Communication method and apparatus

Abstract

Provided in the present application are a communication method and apparatus. The method comprises: a gateway user equipment receiving a first message from a first user equipment, wherein the first message comprises an identifier of a first user associated with the first user equipment, and the first message is used for requesting the authorization of the connection of the first user; and on the basis of the first message, sending a second message to a service device, wherein the service device is used for providing a connection authorization service for the first user, the second message comprises an identifier of the first user, and the second message is used for requesting the authorization of the connection of the first user. By means of carrying the identifier of the first user in a first request message for requesting the authorization of the connection of the first user, both the gateway user equipment and the service device can accurately identify whether a plurality of connection requests come from the same user, and can thus accurately determine whether the same user has had at least one connection, so that the connection of the same user can be effectively controlled, and the authorization of the connection of a single user can be realized.

Description

Communication method and device

[0001] CROSS-REFERENCE TO RELATED APPLICATIONS

[0002] This application claims priority to the Chinese patent application filed with the State Intellectual Property Office of China on September 28, 2023, with application number 202311293920.2 and application name “A Communication Method and Device”, the entire contents of which are incorporated by reference into this application. Technical Field

[0003] The present application relates to the field of communication technology, and in particular to a communication method and device. Background Art

[0004] The 3rd Generation Partnership Project (3GPP) has standardized a set of Mission Critical (MC) services based on the 3GPP Long Term Evolution (LTE) system to support trunked communications in public safety scenarios. For example, MC services include Mission Critical Push To Talk (MCPTT), Mission Critical Data (MCData), and Mission Critical Video (MCVideo).

[0005] Among them, 3GPP SA6 defines the scenario of using Gateway User Equipment (Gateway UE or GW UE) in MC services. When an MC user uses a non-3GPP device (N3GPP device), the non-3GPP device cannot directly connect to the server on the network side, such as the MC server (such as MCPTT server) or the common service core (CSC) server. At this time, the non-3GPP device can connect to the server on the network side through the Gateway UE. For example, an MC client (Client), such as an MCPTT client, a CSC client, etc., can be installed on the non-3GPP device.

[0006] Currently, a non-3GPP device sends a connection authorization request to a Gateway UE. This connection authorization request carries the Gateway MC service ID. The Gateway MC service ID is a temporary, recyclable ID or an authentication ID shared by multiple users. Therefore, the Gateway UE cannot determine whether multiple connection authorization requests correspond to the same user (i.e., MC service user) based on the Gateway MC service ID. Furthermore, the network-side server cannot distinguish whether connection authorization requests from multiple Gateway UEs correspond to the same user based on the Gateway MC service ID. Consequently, the server cannot authorize user connections or determine whether the same user already has a connection for a particular MC service.

[0007] Summary of the Invention

[0008] The present application provides a communication method and apparatus for effectively controlling user connections.

[0009] In a first aspect, the present application provides a communication method, which can be implemented by data interaction between multiple communication devices (such as a first communication device, a second communication device, a third communication device, etc.). Optionally, the first communication device can be a first user device or a component (such as a chip, a chip system, or a circuit, etc.) that can support the first user device to implement the functions required by the method, the second communication device can be a gateway user device or a component (such as a chip, a chip system, or a circuit, etc.) that can support the gateway user device to implement the functions required by the method, and the third communication device can be a service device or a component (such as a chip, a chip system, or a circuit, etc.) that can support the service device to implement the functions required by the method. Exemplarily, taking the data interaction between the first user device, the gateway user device, and the service device to implement the communication method as an example, in this method, after receiving a first message from the first user device, the gateway user device can send a second message to the service device based on the first message, wherein the first message may include an identifier of a first user associated with the first user device, the first message is used to request authorization for the connection of the first user, and the service device is used to provide a connection authorization service to the first user, and the second message may include an identifier of the first user, and the second message is used to request authorization for the connection of the first user.

[0010] In this method, by carrying the user's identifier in the request message for requesting authorization of the user's connection, the gateway user device and the service device can accurately identify whether multiple request messages (or connection requests) are from the same user, and can accurately determine whether the same user already has at least one connection, thereby effectively controlling the connection of the same user, and effectively controlling the connection access of users connecting to the service device through the gateway user device, thereby enabling authorization of a single user for the connection, and effectively avoiding the problem of the same user occupying too many resources due to accessing the service device through multiple gateway user devices, resulting in resource waste. It should be understood that the user identifier carried in the request message can also help the gateway user device accurately identify whether the request message for requesting authorization of the connection from the same user device is from the same user.

[0011] In one possible design, the identifier of the first user may be a permanent identifier of the first user.

[0012] In the above design, by setting the user's identifier as a permanent identifier, it can be ensured that the identifier of each user is unique and unchanged, thereby further ensuring that the gateway user device and the service device can more accurately identify whether multiple request messages for requesting authorized user connections come from the same user through the permanent identifier, which helps to effectively control the number of connections of a single user for a single service (or a single business), and can further effectively realize the authorization of a single user for the connection.

[0013] In one possible design, the method also includes: the gateway user device receives a response message to the second message from the service device, wherein the response message to the second message is used to authorize or reject the connection of the first user, and then the gateway user device can send a response message to the first message to the first user device based on the response message to the second message.

[0014] In the above design, by promptly notifying the first user of the authorization result (e.g., authorization success or authorization failure) of the connection requested by the first user, it is possible to eliminate the need to initiate subsequent business processes after the connection authorized by the first user is rejected, thereby helping to prevent the first user from blindly initiating business request processes. Optionally, by notifying the first user of the result that the first connection authorized was rejected, the first user can also resend the connection request after a period of time, thereby reducing the energy consumption (e.g., resource consumption, power consumption) and network signaling consumption caused by the first user device blindly and continuously initiating connection requests.

[0015] In one possible design, the method also includes: the gateway user equipment can assign a temporary identifier to the first user based on the response message of the second message, wherein the temporary identifier is used to identify the first user on the gateway user equipment, and the response message of the first message includes the temporary identifier of the first user.

[0016] In the above design, by allocating a temporary identifier to each user, the gateway user equipment can accurately identify which user the connection request comes from after receiving a connection request.

[0017] In one possible design, the response message to the first message further includes connection information, and the connection information is used to establish a service connection for the first user.

[0018] In the above design, by carrying the connection information in the response message of the first message, the first user can establish the corresponding service connection in a timely and accurate manner.

[0019] In one possible design, the gateway user equipment sends the second message to the service device based on the first message, including: when the first condition is met, the gateway user equipment may send the second message to the service device based on the first message.

[0020] In the above design, only after judging whether the first condition is met does it decide whether it is necessary to forward the second message for requesting authorization of the first user's connection to the service device. In this way, the connection of the first user can be effectively controlled, and the accuracy of the connection requested for authorization by the first user can be further ensured.

[0021] In one possible design, the first condition includes at least one of the following: the number of connections of the first user is less than or equal to a first number threshold; the association between the device information of the first user device and the identifier of the first user is included in the authorized association relationship; the device information of the first user device is included in the authorized device information; the distance between the first user device and the gateway user device is less than or equal to a distance threshold; there are available resources for the gateway user device; there are no available resources for the gateway user device, and there are connections that can be preempted.

[0022] In the above design, by determining whether one or more of the above conditions are met, a targeted authorization check can be performed on the connection requested by the first user to ensure the rationality and accuracy of the connection authorization.

[0023] In one possible design, the connection that can be preempted includes a second connection, where the second connection is a connection whose user priority is lower than the user priority of the first user, or the second connection is a connection whose service priority is lower than the service priority corresponding to the first service identifier: the method also includes: the gateway user equipment can send a preemption message to the second user equipment corresponding to the second connection, and the preemption message is used to indicate that the resources of the second connection are preempted by a high-priority user or a high-priority service.

[0024] In the above design, when available resources on the gateway user device are insufficient, the connection resources of a particular service or a particular user are selectively preempted based on the service priority or user priority, thereby ensuring that the first user's connection authorization request message can be forwarded to the service device and that the gateway user device has available resources to support the first user's connection. Furthermore, the gateway user device can promptly notify the corresponding user of the specific reason for the preemption by sending a preemption message, and can also inform the corresponding user of the specific service or data flow connection that was preempted.

[0025] In one possible design, the first message also includes at least one of the following: user priority, service priority, location information of the first user device, device information of the first user device, user connection preference, data flow information or first service identifier, the user connection preference is used to indicate priority for preempting or retaining an existing connection, and the data flow information is used to describe the data flow requested to be sent by the first user device.

[0026] In the above design, by carrying one or more of the above contents in the first message, the gateway user equipment can perform a more comprehensive authorization check and a more targeted authorization check on the connection requested by the first user.

[0027] In one possible design, the second message also includes at least one of the following: an identifier of a gateway user device, user priority, service priority, location information of a first user device, device information of a first user device, user connection preference, data flow information, or a first service identifier, where the user connection preference is used to indicate priority for preempting or retaining an existing connection, and the data flow information is used to describe the data flow requested to be sent by the first user device.

[0028] In the above design, by carrying one or more of the above contents in the second message, the service device can perform a more comprehensive authorization check and a more targeted authorization check on the connection of the first request, thereby further deciding whether to authorize the connection requested by the first user or reject the connection requested by the first user.

[0029] In one possible design, the method also includes: the gateway user device receives authorized data flow information from the service device, the authorized data flow information includes information of the authorized data flow associated with the identifier of the first user, and then, after receiving the first data flow from the first user device, the gateway user device sends the first data flow if it determines that the information of the first data flow is included in the authorized data flow information, wherein the first data flow includes the information of the first data flow.

[0030] In the above design, by obtaining the information of the authorized data flow associated with the first user's identifier provided by the service device, it can be accurately determined whether the data flow from the first user device is to be routed or rejected.

[0031] In one possible design, the method also includes: if the information of the first data flow is not included in the authorized data flow information, the gateway user equipment may send a third message to the first user equipment, and the third message is used to indicate that the first data flow is rejected, or to indicate that the first data flow requires additional authorization.

[0032] In the above design, by promptly notifying the first user device of the message that the data flow is rejected (or discarded or not processed), the first user device can take corresponding measures to make adjustments later, such as initiating the corresponding authorization request process for the data flow again.

[0033] In one possible design, the method further includes: after receiving a fourth message from the first user device, the gateway user device can send a corresponding relationship to the service device, wherein the fourth message includes a corresponding relationship between the first user's identifier and at least one service identifier.

[0034] In the above design, by timely sending the correspondence between the first user's identifier and at least one service identifier to the service device, the subsequent service device can accurately obtain the connection status information of the first user from other service devices.

[0035] In one possible design, the method further includes: the gateway user equipment receives a preemption message from the service equipment, where the preemption message is used to indicate that resources of the connection corresponding to the first service identifier are preempted.

[0036] In the above design, the gateway user equipment may also receive a preemption message sent by the service device, for example, the connection resource of a certain service of a certain user connected to the service device through the gateway user equipment is preempted.

[0037] In one possible design, the method also includes: after receiving the fifth message from the first user equipment, the gateway user equipment can send information indicating an established or terminated data flow to the service equipment, wherein the fifth message is used to indicate information of the established or terminated data flow.

[0038] In the above design, by sending information about established or terminated data flows to the service device, the service device can accurately determine the resource usage on the gateway user device.

[0039] On the second aspect, the present application provides a communication method, which can be implemented by data interaction between multiple communication devices (such as a second communication device, a third communication device, etc.). Optionally, the second communication device can be a gateway user device or a component (such as a chip, a chip system or a circuit, etc.) that can support the gateway user device to implement the functions required by the method, and the third communication device can be a service device or a component (such as a chip, a chip system or a circuit, etc.) that can support the service device to implement the functions required by the method. Exemplarily, taking the data interaction between the gateway user device and the service device to implement the communication method as an example, in this method, after the service device receives the second message from the gateway user device, it can send a response message to the second message to the gateway user device based on the second message, wherein the second message may include an identifier of the first user associated with the first user device, the second message is used to request authorization for the connection of the first user, the service device is used to provide a connection authorization service to the first user, and the response message to the second message is used to authorize or reject the connection of the first user.

[0040] In one possible design, when the authorization condition is met, the response message of the second message is used to authorize the connection of the first user; or when the authorization condition is not met, the response message of the second message is used to reject the connection of the first user.

[0041] In one possible design, the second message also includes at least one of the following: an identifier of a gateway user device, user priority, service priority, location information of a first user device, device information of a first user device, user connection preference, data flow information, or a first service identifier, where the user connection preference is used to indicate whether to preempt priority or retain an existing connection, and the data flow information is used to describe the data flow requested to be sent by the first user device.

[0042] In one possible design, the authorization conditions include at least one of the following: the identifier of the first user is included in the authorized user identifier information; the association between the identifier of the first user and the identifier of the gateway user device is included in the authorized association relationship; the association between the identifier of the first user, the device information of the first user device and the identifier of the gateway user device is included in the authorized association relationship; the data flow information verification is passed; the association between the device information of the first user device and the identifier of the gateway user device is included in the authorized association relationship; based on the location information and / or user connection preference of the first user device, there is a connection corresponding to the first service identifier accessed by the first user through other gateway user devices; there are available resources for the gateway user device; there are no available resources for the gateway user device, and there are connections that can be preempted.

[0043] In the above design, by carrying one or more of the above contents in the second message, the service device can perform a more comprehensive authorization check and a more targeted authorization check on the connection of the first request, thereby further deciding whether to authorize the connection requested by the first user or reject the connection requested by the first user.

[0044] In one possible design, the method further includes: the service device may send a preemption message to other gateway user devices, wherein the preemption message is used to indicate that the resources of the connection corresponding to the first service identifier are preempted by the first user.

[0045] In one possible design, the connection that can be preempted includes a third connection, wherein the third connection is a connection whose user priority is lower than the user priority corresponding to the identifier of the first user and whose service identifier is the connection corresponding to the first service identifier, or the second connection is a connection whose service priority is lower than the service priority corresponding to the first service identifier; the method also includes: the service device can send a preemption message to the third user device corresponding to the third connection, wherein the preemption message is used to indicate that the resources of the third connection are preempted by a high-priority user or a high-priority service.

[0046] In one possible design, the method further includes: the service device may send authorized data flow information to the gateway user equipment, wherein the authorized data flow information includes information of the authorized data flow associated with the identifier of the first user.

[0047] In one possible design, the method also includes: the service device receives a fourth message from the gateway user device, and then the service device can obtain the number of connections of the first user based on the first service identifier of the first user, wherein the fourth message includes the correspondence between the identifier of the first user and the first service identifier of the first user.

[0048] In one possible design, the method further includes: the service device receiving a fifth message from the gateway user equipment, wherein the fifth message is used to indicate information about an established or terminated data flow.

[0049] The technical effects that can be achieved in the second aspect can be referred to the technical effects that can be achieved in the first aspect mentioned above, and will not be repeated here.

[0050] In a third aspect, the present application provides a communication method, which can be implemented by data interaction between multiple communication devices (such as a first communication device, a second communication device, a third communication device, etc.). Optionally, the first communication device can be a first user device or a component (such as a chip, a chip system or a circuit, etc.) that can support the first user device to implement the functions required by the method, the second communication device can be a gateway user device or a component (such as a chip, a chip system or a circuit, etc.) that can support the gateway user device to implement the functions required by the method, and the third communication device can be a service device or a component (such as a chip, a chip system or a circuit, etc.) that can support the service device to implement the functions required by the method. Exemplarily, taking the data interaction between the first user device, the gateway user device and the service device to implement the communication method as an example, in this method, after the gateway user device receives the first data packet from the first user device, if the destination address of the first data packet is included in the authorized data flow information, it can forward the first data packet to the service device, and the gateway user device receives the authorized routing address information. Then, the gateway user device can route or reject the data flow from the first user device according to the authorized routing address information.

[0051] Exemplarily, the gateway user equipment may receive authorized routing address information from a service server, an identity authentication management server, or a configuration management server.

[0052] In this method, the gateway user equipment can accurately determine whether to route or reject a data flow from a certain user equipment (e.g., the first user equipment) based on the authorized routing address information, thereby effectively controlling access to user-plane data flows and also effectively controlling access to control-plane data flows. It should be understood that rejection can be understood as discarding or not processing.

[0053] In one possible design, the authorized routing address information includes: the communication address of the service device, or first routing address information and second routing address information, wherein the first routing address information indicates the authorized service communication address of the service device and / or the control plane communication address of the service device, and the second routing address information is used to indicate the user plane communication address of the service device.

[0054] In the above design, the address information included in the authorized routing address information can be used to accurately determine whether a data packet is decided to be routed or rejected.

[0055] In one possible design, the authorized routing address information includes first routing address information and second routing address information, and the gateway user equipment receives the authorized routing address information, including: the gateway user equipment receives the first routing address information, and then the gateway user equipment receives a second data packet from the user equipment. If the destination address of the second data packet is included in the first routing address information, the gateway user equipment can forward the second data packet to the service device corresponding to the destination address, and then the gateway user equipment can receive the second routing address information, and the destination address of the second data packet is the authorized service communication address or the control plane communication address.

[0056] In the above design, the service device provides the gateway user equipment with the authorized first routing address information and the authorized second routing address information, so that the gateway user equipment can accurately determine whether the data packet from the user equipment is to be routed or rejected.

[0057] In one possible design, the method further includes: the gateway user equipment receives third routing address information from the service equipment, and then the gateway user equipment can update the authorized routing address information stored in the gateway user equipment according to the third routing address information.

[0058] In the above design, when the first routing address information and / or the second routing address information is updated, the service device can provide the gateway user device with third routing address information (i.e., the updated first routing address information and / or the second routing address information), so that the gateway user device can promptly update the locally stored first routing address information and / or the second routing address information based on the third routing address information. It will be understood that updating the locally stored first routing address information and / or the second routing address information can mean invalidating, invalidating, or revoking the locally stored first routing address information and / or the second routing address information.

[0059] In one possible design, the method also includes: the gateway user equipment receives a third data packet from the first user equipment, and if the destination address of the third data packet is not included in the authorized routing address information, the gateway user equipment may send a third message to the first user equipment, wherein the third message is used to indicate a refusal to route the third data packet.

[0060] In the above design, when the destination address of a data packet from a user device is not included in the authorized routing address information, the gateway user device can promptly notify the first user device so that the first user device can promptly learn the routing result of the data packet. For example, after learning that the data packet routing result is rejected, the first user device can re-initiate the registration authentication process or service authorization process.

[0061] In one possible design, before the gateway user equipment receives the first message from the first user equipment, the method further includes: the gateway user equipment establishing a non-3GPP transport connection with the first user equipment.

[0062] In the above design, the network access mode of the first user equipment is non-3GPP access. For example, the first user equipment can establish a communication connection with the gateway user equipment through a Bluetooth network or a wireless fidelity network.

[0063] In a fourth aspect, the present application provides a communication method, which can be implemented by data interaction between multiple communication devices (such as a second communication device, a third communication device, etc.). Optionally, the second communication device can be a gateway user device or a component (such as a chip, a chip system or a circuit, etc.) that can support the gateway user device to implement the functions required by the method, and the third communication device can be a service device or a component (such as a chip, a chip system or a circuit, etc.) that can support the service device to implement the functions required by the method. Exemplarily, taking the data interaction between the gateway user device and the service device to implement the communication method as an example, in this method, the service device receives a first message from the first user device. Afterwards, if the first user identity authentication is passed, the service device can send authorized routing address information to the gateway user device, wherein the first message is encapsulated in a first data packet and sent to the service device via the gateway user device. The first message may include the identifier of the first user associated with the first user device, and the first message is used to request identity authentication for the first user.

[0064] The technical effects that can be achieved in the fourth aspect can be referred to the technical effects that can be achieved in the third aspect mentioned above, and will not be repeated here.

[0065] In one possible design, the authorized routing address information includes: the communication address of the service device, or first routing address information and second routing address information, wherein the first routing address information indicates the authorized service communication address of the service device and / or the control plane communication address of the service device, and the second routing address information is used to indicate the user plane communication address of the service device.

[0066] In one possible design, the authorized routing address information includes first routing address information and second routing address information; the service device sends the authorized routing address information to the gateway device, including: if the first user identity authentication is passed, the service device can send the first routing address information to the gateway user device, and then the service device can receive a second message from the gateway user device. If the service authorization or service registration is completed, the service device can send the second routing address information to the gateway user device, wherein the second message is encapsulated in a second data packet and sent to the service device via the gateway user device, and the second message is used to request service authorization or service registration for the first user.

[0067] In the above design, after the service device performs identity authentication on the first user, it can provide the first routing address information to the gateway user device. Thereafter, after completing the service authorization or service registration requested by the first user, it can provide the second routing address information to the gateway user device. In this way, it can effectively determine whether the routing address information authorized by the first user should be provided to the first user.

[0068] In one possible design, the method also includes: if the first user has at least one connection, or the number of connections or the number of users or the number of data streams served by the gateway user device is greater than a second quantity threshold, or the first user's identifier has been de-registered or logged in or logged out from the service device, or the set time period expires, the service device can send third routing address information to the gateway user device.

[0069] In the above design, when any of the above conditions is met, the service device can update the first routing address information and / or the second routing address information to obtain the third routing address information. The service device can then provide the third routing address information to the gateway user device, so that the gateway user device can promptly configure (or update) the locally stored first routing address information and / or the second routing address information. This allows the gateway user device to use the updated first routing address information and / or the second routing address information to determine whether a data stream (or data packet) from the user device should actually be routed.

[0070] In a fifth aspect, the present application provides a possible communication device. Optionally, the communication device may be a communication device (such as a first communication device or a second communication device or a third communication device) or a component (such as a chip, a chip system or a circuit, etc.) that can support the communication device to implement the functions required for the communication method. Exemplarily, the first communication device may be a user equipment (such as a first user equipment or a second user equipment), the second communication device may be a gateway user equipment, and the third communication device may be a service device (such as an MC service server or other business server or a configuration management server or an identity authentication management server). When the communication device is a chip provided in the first communication device (or the second communication device or the third communication device), the communication device includes a transceiver and a processor, but does not include a memory. The transceiver exists in the form of an input and output interface, and the input and output interface is used for the chip to implement the transceiver of the communication device. The input and output interface may include an input interface and / or an output interface, the input interface can implement the reception of the communication device, and the output interface can be used to implement the transmission of the communication device. The processor is used to read and execute corresponding computer programs or instructions so that the corresponding functions of the first communication device (or the second communication device or the third communication device) are implemented. Optionally, when the chip implements the corresponding functions of the first communication device (or the second communication device or the third communication device) in the communication method embodiment provided by the present application, the input and output interface can implement the sending and receiving operations performed by the first communication device (or the second communication device or the third communication device) in the communication method embodiment provided by the present application; the processor can implement other operations other than the sending and receiving operations performed by the first communication device (or the second communication device or the third communication device) in the above-mentioned communication method embodiment provided by the present application.

[0071] In one example, when a communication device is used to implement the functions of a gateway user device in the method embodiments described in the first or second aspects above, the beneficial effects can be found in the description of the gateway user device in the first or second aspects above and are not further described here. The communication device has the function of implementing the behavior of the gateway user device in the method embodiments described in the first or second aspects above. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions. In one possible design, the communication device includes: a communication module (or a communication unit, a transceiver module, or a transceiver unit, configured to send and receive data) and a processing module (or a processing unit). The communication module is configured to receive a first message from a first user device. The first message includes an identifier of a first user associated with the first user device, and the first message is configured to request authorization for the first user's connection. The processing module is configured to send a second message to a service device based on the first message. The service device is configured to provide a connection authorization service to the first user, and the second message includes the identifier of the first user, and the second message is configured to request authorization for the first user's connection. These modules can execute the corresponding functions of the gateway user equipment in the method embodiments shown in the first aspect or the second aspect above. For details, please refer to the detailed description of the corresponding functions of the gateway user equipment in the method examples, which will not be repeated here.

[0072] In another example, when a communication device is used to implement the functions of a service device in the method embodiments described in the first or second aspects above, the beneficial effects can be found in the description of the service device in the first or second aspects above and are not further described here. The communication device has the functions of implementing the behaviors of the service device in the method embodiments described in the first or second aspects above. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions. In one possible design, the communication device includes: a communication module for receiving a second message from a gateway user equipment. The second message includes an identifier of a first user associated with the first user equipment, the second message is used to request authorization for the first user's connection, and the service device is used to provide a connection authorization service to the first user. A processing module is used to send a response message to the second message to the gateway user equipment based on the second message, the response message to the second message being used to authorize or deny the first user's connection. These modules can perform the corresponding functions of the service device in the method embodiments described in the first or second aspects above. For details, refer to the detailed description of the corresponding functions of the service device in the method examples and are not further described here.

[0073] In another example, when a communication device is used to implement the functions of a gateway user equipment in the method embodiments described in the third or fourth aspects above, the beneficial effects can be found in the description of the gateway user equipment in the third or fourth aspects above, and are not further described here. The communication device has the functions of implementing the behaviors of the gateway user equipment in the method embodiments described in the third or fourth aspects above. The functions can be implemented in hardware, or by hardware executing corresponding software implementations. The hardware or software includes one or more modules corresponding to the functions. In one possible design, the communication device includes: a communication module for receiving a first data packet from a first user equipment; a processing module for forwarding the first data packet to a service device if the destination address of the first data packet is included in authorized data flow information; a communication module for further receiving authorized routing address information; and a processing module for routing or rejecting the data flow from the first user equipment based on the authorized routing address information. These modules can perform the corresponding functions of the gateway user equipment in the method embodiments described in the third or fourth aspects above, and for details, refer to the detailed description of the corresponding functions of the gateway user equipment in the method examples, and are not further described here.

[0074] In another example, when a communication device is used to implement the functions of a service device in the method embodiments described in the third or fourth aspects above, the beneficial effects can be found in the description of the service device in the third or fourth aspects above and are not further described here. The communication device has the function of implementing the behavior of the service device in the method embodiments described in the third or fourth aspects above. The functions can be implemented in hardware or by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the functions. In one possible design, the communication device includes: a communication module for receiving a first message from a first user device. The first message includes an identifier of a first user associated with the first user device, the first message is encapsulated in a first data packet and sent to the service device via a gateway user device, and the first message is used to request identity authentication for the first user. A processing module is configured to send authorized routing address information to the gateway user device if the first user identity authentication is successful. These modules can perform the corresponding functions of the service device in the method embodiments described in the third or fourth aspects above. For details, see the detailed description of the corresponding functions of the service device in the method examples and are not further described here.

[0075] In a sixth aspect, the present application provides a possible communication device, which may be a communication device (such as a first communication device or a second communication device or a third communication device) required to execute the communication method provided in the present application, or may be a device that includes the communication device required to execute the communication method provided in the present application, or may be a device having the functions required to implement the communication method. The communication device may include a transceiver and a processor. Optionally, the communication device may also include a memory. The memory is used to store computer programs or instructions, and the processor is coupled to the memory and the transceiver. When the processor executes the computer program or instruction, the communication device executes any possible design method of the first aspect or any possible design method of the second aspect or any possible design method of the third aspect or any possible design method of the fourth aspect.

[0076] In a seventh aspect, the present application provides a possible communication system, which may include the first communication device, the second communication device, and the third communication device mentioned in the first, second, third, or fourth aspects above. The relevant functional implementations of the first, second, or third communication device can be found in the relevant descriptions of the first, second, third, or fourth aspects above, and will not be repeated here.

[0077] Exemplarily, the communication system may include one or more first communication devices, one or more second communication devices, and one or more third communication devices.

[0078] In an eighth aspect, the present application provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run on a computer, the computer executes any possible design method of the first aspect above, or any possible design method of the second aspect above, or any possible design method of the third aspect above, or any possible design method of the fourth aspect above.

[0079] In the ninth aspect, the present application provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed by a computer, the computer executes any possible design method of the first aspect or any possible design method of the second aspect or any possible design method of the third aspect or any possible design method of the fourth aspect.

[0080] In a tenth aspect, the present application further provides a chip, which may include a processor and may also include a memory (or the chip is coupled to the memory), and the chip executes program instructions in the memory to perform the method in any possible design of the first aspect or any possible design of the second aspect or any possible design of the third aspect or any possible design of the fourth aspect. Wherein, "coupling" refers to the direct or indirect combination of two components, such as coupling can refer to an electrical connection between two components.

[0081] In an eleventh aspect, the present application further provides a chip system, which includes a processor for supporting a computer device to implement the method in any possible design of the first aspect, the method in any possible design of the second aspect, the method in any possible design of the third aspect, or the method in any possible design of the fourth aspect. In one possible design, the chip system also includes a memory for storing the necessary programs and data for the computer device. The chip system can be composed of a chip, or it can include a chip and other discrete devices.

[0082] Based on the implementation methods provided in the above aspects, this application can also be further combined to provide more implementation methods. BRIEF DESCRIPTION OF THE DRAWINGS

[0083] FIG1a exemplarily shows a possible communication system architecture diagram provided by an embodiment of the present application;

[0084] FIG1b exemplarily shows a schematic diagram of an MCPTT communication system architecture provided in an embodiment of the present application;

[0085] FIG1c exemplarily shows another possible communication system architecture diagram provided by an embodiment of the present application;

[0086] FIG2 exemplarily shows a flow chart of a communication method provided in an embodiment of the present application;

[0087] FIG3 exemplarily shows a flow chart of another communication method provided in an embodiment of the present application;

[0088] FIG4 exemplarily shows a flow chart of another communication method provided in an embodiment of the present application;

[0089] FIG5 exemplarily shows a flow chart of another communication method provided in an embodiment of the present application;

[0090] FIG6 exemplarily shows a structural diagram of a possible communication device provided in an embodiment of the present application;

[0091] FIG7 exemplarily shows a schematic structural diagram of another possible communication device provided in an embodiment of the present application. DETAILED DESCRIPTION

[0092] The embodiments of the present application will be described in detail below with reference to the accompanying drawings.

[0093] The following describes possible communication system architectures to which the communication method provided in this application is applicable. It should be noted that these descriptions are intended to facilitate understanding by those skilled in the art and do not limit the scope of protection claimed in this application.

[0094] Figure 1a illustrates a possible communication system architecture applicable to embodiments of the present application. As shown in Figure 1a, the communication system architecture includes a Mission Critical Service Server (MC Service Server / MC server), a Common Service Core (CSC), and an MC Service User Equipment (MC Service UE).

[0095] Exemplarily, the emergency mission service server may include but is not limited to an MCPTT server, an MCData server, or an MCVideo server, etc. The universal service core may include a CSC server, for example, the CSC server may include but is not limited to a group management server, a configuration management server, an identity management server, a key management server, or a location management server, etc. The emergency mission service user equipment may be installed with at least one of the following clients: an emergency mission service client (MC Service client) or a universal service core (CSC) client. For example, the universal service core client may include but is not limited to a group management client, a configuration management client, an identity management client, a key management client, or a location management client, etc. For example, the emergency mission service client may include but is not limited to an MCPTT client, an MCData client, or an MCVideo client, etc.

[0096] The following is a brief introduction to the functions of some network elements included in the communication system architecture shown in Figure 1a above:

[0097] The Emergency Mission Service Server is used to provide users with corresponding business services, such as call control, media control, service authorization, or user registration processing. For example, the MCPTT server is used to provide MCPTT services to users; the MCData server is used to provide users with MCData services; and the MCVideo server is used to provide users with MCVideo services. In this application, the Emergency Mission Service Server can also provide connection authorization services for users using non-3GPP devices.

[0098] The general service core is used to provide corresponding data services to the emergency task service server and the emergency task service user equipment.

[0099] In one example, when the general service core includes a group management server, the group management server is used to manage group information (such as the group to which each user belongs). For example, the emergency task service server and / or the emergency task service user device can obtain the groups to which one or more users belong from the group management server. In another example, when the general service core includes a configuration management server, the configuration management server is used to distribute the user's configuration data (such as the group to which the user belongs, user permissions, etc.). For example, the emergency task service server and / or the emergency task service user device can obtain the configuration data of one or more users from the configuration management server. In another example, when the general service core includes an identity authentication management server, the identity authentication management server is used to authenticate the user's identity information and determine whether it is a legitimate user. For example, the emergency task service server and / or the emergency task service user device can verify whether one or several users are legitimate users through the identity authentication management server. In another example, when the general service core includes a key management server, the key management server is used to provide key management services, such as services such as key creation, enabling, disabling, viewing key details, modifying related information, or it can also refer to the corresponding management of key information such as keys, digital certificates, configuration files, etc. (such as authorization or cancellation). In another example, when the universal service core includes a location management server, the location management server is used to manage the user's location information, such as configuring a location reporting trigger, obtaining location information from a user device, and providing location information query functions. In the present application, the service for providing connection authorization for users using non-3GPP devices may also be a server module in the universal service core.

[0100] A client for assisting users in accessing corresponding servers is installed on the emergency task service user device. For example, a user can access the MCPTT server by logging into the MCPTT client installed on the emergency task service user device, or the user can access the MCData server by logging into the MCData client installed on the emergency task service user device, or the user can access the MCVideo server by logging into the MCVideo client installed on the emergency task service user device, or the user can access the group management server by logging into the group management client installed on the emergency task service user device, or the user can access the configuration management server by logging into the configuration management client installed on the emergency task service user device, or the user can access the identity authentication management server by logging into the identity authentication management client installed on the emergency task service user device, or the user can access the key management server by logging into the key management client installed on the emergency task service user device, or the user can access the location management server by logging into the location management client installed on the emergency task service user device.

[0101] For example, as shown in Figure 1a, a group management service client can communicate with a group management server via the CSC-2 interface (CSC-2). A configuration management client can communicate with a configuration management server via the CSC-4 interface (CSC-4). An identity authentication management client can communicate with an identity authentication management server via the CSC-1 interface (CSC-1). A key management client can communicate with a key management server via the CSC-8 interface (CSC-8). A location management client can communicate with a location management server via the CSC-14 interface (CSC-14). The location management server can communicate with the configuration management server via the CSC-24 interface (CSC-24). The key management server can communicate with a group management server via the CSC-10 interface (CSC-10). The location management server can communicate with an emergency task service server via the CSC-15 interface (CSC-15). The key management server can communicate with an emergency task service server via the CSC-9 interface (CSC-9). The configuration management server can communicate with the emergency task service server through the CSC-5 interface (abbreviated as CSC-5). The group management server can communicate with the emergency task service server through the CSC-3 interface (abbreviated as CSC-3).

[0102] It should be noted that the names of the network elements and the interfaces between them in FIG1a are only examples. In the specific implementation process, the names of the network elements and the interfaces between them may be other names, and the present embodiment does not limit this. In the present embodiment, the Evolved Packet System (EPS) can also be replaced by other mobile communication networks (such as the fifth-generation communication system (5GS)).

[0103] For example, the following describes the MCPTT communication system architecture, using MCPTT as an example. As shown in Figure 1b, the MCPTT communication system architecture includes an MCPTT server, an MCPTT UE, an MCPTT user database, an interworking function module with the legacy system, and other MCPTT servers.

[0104] Exemplarily, the functional modules of the MCPTT server may include but are not limited to a media distribution function module or a media control server (Transmission control server / floor control server). The media distribution function module may be a logical entity located inside the service server, responsible for receiving uplink media data and sending downlink media data. The media control server may serve as a media transmission control entity on the media plane, located inside the service server, responsible for uplink and / or downlink transmission control of the media. For example, in the MCPTT system, the media control server may be a floor control server, and in MCVideo, the media control server may be a transmission control server.

[0105] The MCPTT UE is installed with a client for assisting users in accessing the MCPTT server, namely the MCPTT client. For example, the functional modules of the MCPTT client may include but are not limited to a multimedia functional module (Media mixer) or a media control participant (Transmission control participant / Floor participant). Among them, the Media mixer is a peer entity corresponding to the Media distribution function on the user side, and is responsible for the processing of media packets. The media control participant is a peer entity of the media control server on the user side, that is, a media transmission control entity on the media plane, and is responsible for the transmission control of media uplink and / or downlink. Exemplarily, in the MCPTT system, the media control participant may be a Floor control participant.

[0106] The MCPTT user database is used to store configuration data information of users in the system, such as the MCPTT user profile.

[0107] The module for interconnection and interoperability with legacy systems is used for interconnection and service connection with other heterogeneous systems / access systems, such as P25 and TETRA.

[0108] For example, as shown in Figure 1b, the MCPTT server can communicate with other MCPTT servers through the MCPTT-3 interface (MCPTT-3 for short). The MCPTT user database can communicate with the MCPTT server through the MCPTT-2 interface (MCPTT-2 for short). The interoperability function module with the old system can communicate with the MCPTT server through the IWF-1 interface (IWF for short). The media mixer can communicate with the media distribution function module through the MCPTT-7 interface (MCPTT-7 for short) and the MCPTT-8 interface (MCPTT-8 for short). The media control server can communicate with the media control participants through the MCPTT-4 interface (MCPTT-4 for short) and the MCPTT-9 interface (MCPTT-9 for short). The MCPTT UE can communicate with the MCPTT server through the MCPTT-1 interface (MCPTT-1 for short). It should be noted that the names of the modules and the interfaces between the modules in FIG1b are merely examples. In a specific implementation process, the names of the modules and the interfaces between the modules may be other names, which are not limited in the embodiments of the present application.

[0109] Figure 1c illustrates another possible communication system architecture applicable to embodiments of the present application. As shown in Figure 1c, the communication system architecture includes non-3GPP devices, a Gateway User Equipment (or MC Gateway UE), an emergency mission service server, a general service core, a Session Initiation Protocol (SIP) core, and a Hypertext Transfer Protocol (HTTP) proxy module.

[0110] For example, a gateway client (such as an MC gateway client), an emergency task client (MC client), an HTTP client, or a signaling user agent (Signaling User Agent) module may be installed on a non-3GPP device, but is not limited to the following. Exemplarily, the emergency task client may represent an emergency task service client or a CSC client. The functional modules of a gateway user equipment (such as an MC gateway user equipment) may include, but are not limited to, a gateway user equipment server (such as an MC gateway UE server), an emergency task service client, a CSC client, an HTTP client, or a signaling user agent module. The gateway user equipment function (such as an MC gateway UE function) module may be set inside the emergency task service server, or the gateway user equipment function module may also be set in a service device (such as an MC server) independent of the emergency task service server.

[0111] Optionally, the functions of the emergency mission service server and the general service core can be introduced by referring to the relevant description of the communication system architecture shown in FIG1a above, which will not be repeated here.

[0112] The following is a brief introduction to the functions of some network elements included in the communication system architecture shown in Figure 1c above:

[0113] In MC service scenarios, MC users need to use non-3GPP devices to access the corresponding services. For example, non-3GPP devices use non-3GPP access methods, such as Bluetooth or wireless fidelity (Wi-Fi).

[0114] The gateway client is a connection authentication function introduced in the terminal for non-3GPP devices to use the gateway user equipment. When the gateway client does not need to transmit data through the gateway user equipment, the connection with the gateway user equipment is disconnected.

[0115] The gateway user equipment is used to connect non-3GPP devices with the server system on the network side (such as MC gateway UE function), which is equivalent to a user equipment that assumes the gateway function.

[0116] The gateway user equipment server is responsible for interacting with the server system on the network side (such as the MC gateway UE function) to complete the connection authentication for non-3GPP devices.

[0117] The gateway user equipment function module is a function module in the emergency mission service server or in other service devices, and is responsible for interacting with the gateway user equipment server in the gateway user equipment to implement connection authentication for non-3GPP devices using the gateway user equipment.

[0118] The signaling user agent module is used to handle SIP transactions, including SIP session and connection management, SIP message routing, etc.

[0119] The Hypertext Transfer Protocol proxy module is used to handle HTTP transactions, including HTTP session and connection management, HTTP message routing, etc.

[0120] The Session Initiation Protocol core is responsible for SIP processing, service selection, routing SIP messages, etc.

[0121] For example, as shown in Figure 1c, a gateway client can communicate with a gateway user equipment server via the GW-local interface (GW-local). The gateway user equipment server communicates with the gateway user equipment functional module via the GW-Core interface (GW-Core). An emergency task client can communicate with the gateway user equipment via the MCX-n interface (MCX-n), and the gateway user equipment can also communicate with the emergency task service server via the MCX-n interface. The emergency task client can also communicate with the emergency task service server via the MCX-n interface. A CSC client can communicate with the CSC server in the common service core via the CSC-n interface (CSC-n). The emergency task client can communicate with the gateway user equipment via the CSC-n interface, and the gateway user equipment can also communicate with the CSC server in the common service core via the CSC-n interface. The signaling user agent module in a non-3GPP device can communicate with the gateway user equipment via the SIP-1 interface (SIP-1), and the gateway user equipment can also communicate with the Session Initiation Protocol core via the SIP-1 interface. The signaling user agent module in the gateway user equipment can communicate with the session initiation protocol core through the SIP-1 interface. The HTTP client in the non-3GPP device can communicate with the gateway user equipment through the HTTP-1 interface (HTTP-1 for short), and the gateway user equipment also communicates with the hypertext transfer protocol proxy module through the HTTP-1 interface. The HTTP client in the gateway user equipment can communicate with the hypertext transfer protocol proxy module through the HTTP-1 interface. It should be noted that the names of the various modules and the interfaces between the various modules in Figure 1c are only used as an example. During the specific implementation process, the names of the various modules and the interfaces between the various modules may be other names, and the embodiments of the present application do not limit this.

[0122] It is understood that the above-mentioned network element or function can be a network element in a hardware device, a software function running on dedicated hardware, or a virtualized function instantiated on a platform (e.g., a cloud platform). Optionally, the above-mentioned network element or function can be implemented by a single device, or by multiple devices, or can be a functional module within a single device, and this is not specifically limited in the embodiments of the present application.

[0123] Optionally, the communication method provided in the embodiment of the present application can be applied to the architecture of a mission critical service system. For example, the mission critical service system may include but is not limited to systems such as MCPTT, MCVIDEO or MCDATA. It should be noted that the communication system architecture shown in the embodiment of the present application is for the purpose of more clearly illustrating the technical solution of the embodiment of the present application, and does not constitute a limitation on the technical solution provided in the embodiment of the present application. A person of ordinary skill in the art will know that with the evolution of the communication system architecture and the emergence of new business scenarios, the technical solution provided in the embodiment of the present application is also applicable to similar technical problems.

[0124] The following is a detailed introduction to the specific implementation of the communication method in the embodiment of the present application based on the communication system architecture shown in Figure 1a, Figure 1b or Figure 1c.

[0125] Figure 2 exemplarily shows a flow chart of a communication method provided by an embodiment of the present application. The method is applicable to the communication system architecture shown in Figure 1a, Figure 1b or Figure 1c. The method flow can be implemented by data interaction between multiple communication devices (such as a first communication device, a second communication device or a third communication device). Optionally, the first communication device can be a user device (such as a first user device or a second user device) or a component that can support the user device to implement the functions required by the method (such as a chip, a chip system or a circuit, etc.), the second communication device can be a gateway user device or a component that can support the gateway user device to implement the functions required by the method (such as a chip, a chip system or a circuit, etc.), and the third communication device can be a service device or a component that can support the service device to implement the functions required by the method (such as a chip, a chip system or a circuit, etc.). Exemplarily, the user equipment may be an emergency task service user equipment as shown in FIG1a , or may be an MCPTT UE as shown in FIG1b , or may be a non-3GPP device as shown in FIG1c ; the gateway user equipment may be a gateway user equipment as shown in FIG1c ; the service equipment may be an emergency task service server as shown in FIG1a , or may be an MCPTT server as shown in FIG1b , or may be an emergency task service server or a general service core or a session initiation protocol core or a gateway user equipment functional module or a hypertext transfer protocol proxy module as shown in FIG1c . It should be understood that the communication method provided in the embodiment of the present application is also applicable when a gateway user equipment is introduced between the emergency task service user equipment and the emergency task service server as shown in FIG1a , or the communication method provided in the embodiment of the present application is also applicable when a gateway user equipment is introduced between the MCPTT UE and the MCPTT server as shown in FIG1b . To facilitate the introduction of the technical solutions provided by the embodiments of the present application, the following describes a process for implementing a communication method by exchanging data between the first communication device, the second communication device, and the third communication device, taking the first communication device as a first user device, the second communication device as a gateway user device, and the third communication device as a service device as an example. As shown in FIG2 , the method includes:

[0126] Step 201: A first user equipment sends a first message to a gateway user equipment, and the gateway user equipment receives the first message.

[0127] Optionally, before the first user equipment sends the first message to the gateway user equipment, the first user equipment establishes a non-3GPP transmission connection (such as a Bluetooth connection or a WI-FI connection) with the gateway user equipment, which can be understood as the network access method of the first user equipment being non-3GPP access. For example, the first user equipment is a non-3GPP device. For example, the first user equipment can be installed with, but not limited to, a gateway client (such as an MC gateway client), an emergency task client (MC client), an HTTP client, or a signaling user agent module.

[0128] Exemplarily, the first message may include an identifier of the first user associated with the first user device. The first message is used to request authorization for the connection of the first user. It can be understood that the connection of the first user may refer to the connection between the user and the gateway device, and the connection of the first user may also refer to the connection for data transmission between the user and the MC Service Server. The connection of the first user may also refer to the association between the first user and the gateway UE. The connection of the first user may refer to a data plane connection (i.e., a connection channel for transmitting voice, video, and data packets), and / or a signaling plane connection (i.e., a connection channel for transmitting application layer signaling messages such as authentication messages, authorization messages, session messages, etc.).

[0129] For example, the first message may be used to request that an authorized user use a gateway user device (such as gateway UE1). In this case, the connection of the first user may refer to the connection between the first user device and the gateway user device (or may be understood as the authorized user using a non-3GPP connection with the gateway user device to transmit data). At this time, the first user device can communicate with another non-3GPP device or service device through the gateway user device. Optionally, the first message may also be used to request that an authorized user use the data connection between the gateway user device and the service device. The connection of the first user refers to the data connection between the gateway user device and the service device. It should be understood that the connection of the first user may also refer to two connections between the first user device and the gateway user device, and the gateway user device and the service device. Optionally, the first message may also be used to request authorization for a connection between the first user device and a specific gateway user device. For example, the specific gateway user device can only be gateway UE1 and cannot be gateway UE2.

[0130] In an embodiment of the present application, the identifier of the first user may be a permanent identifier of the first user. Exemplarily, the identifier of the first user may be an MC ID, or may also be an MC IP. For example, taking the first user as a certain user (such as user1), the identifier of user1 may be MC ID1, or may also be MC IP1. MC ID uniquely identifies a user. MC ID is the identity presented by a user to the identity authentication server during an authentication transaction. The MC ID can be bound to a single MC service type (such as MCPTT, MCVideo, MCData), and the MC ID can be linked to a set of credentials (such as biometrics, security ID, username / password).

[0131] For example, the first message may also include at least one of the following: user priority, service priority, location information of the first user device, device information of the first user device, user connection preference, data flow information (such as information about the connection or flow received or sent after the MC client installed on the first user device is connected and authorized, such as a Uniform Resource Locator (URL) list, a server IP triplet, or an IP quadruple (terminal IP + server IP triplet)), a first service identifier (such as a GW MC service ID, or an MC service type), or a security credential, etc. Exemplarily, the first service identifier can be used to indicate a service (such as one or more of MCPTT, MCVideo, or MCdata), or can also be used as a temporary identifier for the gateway user device to distinguish different users, such as the gateway user device assigning different temporary identifiers to different users. Among them, the user connection preference is used to indicate priority for preemption or priority for retaining an existing connection, the data flow information is used to describe the data flow requested to be sent or received by the first user device, and the security credential can be used to verify whether the first user is legitimate.

[0132] Step 202: The gateway user equipment sends a second message to the service device according to the first message. The service device receives the second message.

[0133] In the embodiment of the present application, a service device (such as an MC Service Server, an Identity management server, or other service servers (such as a SIP Core)) is used to provide a connection authorization service to the first user.

[0134] Exemplarily, the second message may include an identity management message, which may be a cell or container in the second message. The identity management message is used to authenticate the identity of the first user. In this case, the second message is also used for identity authentication.

[0135] Exemplarily, the second message may also include an identifier of the first user associated with the first user equipment. The second message is used to request authorization for the connection of the first user.

[0136] For example, the second message further includes at least one of the following: an identifier of a gateway user device, a user priority, a service priority, location information of the first user device, device information of the first user device, user connection preferences, data flow information, or a first service identifier. The identifier of the gateway user device may be a device identifier of the gateway user device (e.g., a SN number, a MAC address), or a user identifier of a logged-in user on the gateway device. In this case, the user may be a special user, such as an administrator user.

[0137] In a possible implementation, when the first condition is met, the gateway user equipment may send a second message to the service device according to the first message.

[0138] Exemplarily, the first condition may include at least one of the following: the number of connections of the first user is less than or equal to a first quantity threshold; the association between the device information of the first user device (such as the device number, SN (Serial Number) number, etc.) and the identifier of the first user (such as MC ID or MC IP) is included in the authorized association relationship (or the authorized association relationship list, such as which user devices are pre-configured on the gateway user device to have an association relationship with which users); the device information of the first user device is included in the authorized device information (or the authorized device information list, such as which user devices are pre-configured on the gateway user device to be allowed to access (or allowed to serve)); the distance between the first user device and the gateway user device is less than or equal to the distance threshold; the gateway user device has available resources; or the gateway user device has no available resources and there is a connection that can be preempted (such as a connection of a user whose user priority is lower than the user priority of the first user or a connection of a service whose service priority is lower than the service priority corresponding to the first service identifier).

[0139] It can be understood that the distance between the first user equipment and the gateway user equipment is calculated based on the location information of the first user equipment and the location information of the gateway user equipment.

[0140] For example, after the gateway user equipment determines that there are no available resources for the gateway user equipment and there is a connection that can be preempted, a preemption message can be sent to the user equipment corresponding to the preempted connection. The preemption message is used to indicate that the resources of the preempted connection are preempted by a high-priority user or a high-priority service. For example, taking the preemptible connection as an example, the second connection may refer to a connection whose user priority is lower than the user priority of the first user, or the second connection may refer to a connection whose service priority is lower than the service priority corresponding to the first service identifier. When the second connection refers to a connection whose user priority is lower than the user priority of the first user, the gateway user equipment may send a preemption message to the user equipment corresponding to the second connection (such as the second user equipment). When the second connection refers to a connection whose service priority is lower than the service priority corresponding to the first service identifier, the gateway user equipment may send a preemption message to the user equipment corresponding to the second connection (such as the first user equipment or the second user equipment).

[0141] In another possible implementation, when the first condition is not met, the gateway user equipment may send an authorization rejection message (or an authorization failure or authorization failure message) to the first user equipment. The authorization rejection message (or authorization failure or authorization failure message) is used to indicate that the first user's connection authorization request is rejected (or fails or is not passed).

[0142] Step 203: The service device sends a response message of the second message to the gateway user equipment according to the second message. The gateway user equipment receives the response message of the second message.

[0143] Exemplarily, the response message to the second message is used to indicate authorization of the first user's connection, or to indicate rejection of the first user's connection.

[0144] For example, when the authorization condition is met, the service device may carry information indicating that the authorization of the first user's connection has been passed (or that the authorization has succeeded) in the response message to the second message. When the authorization condition is not met, the service device may carry information indicating that the authorization of the first user's connection has not been passed (or that the authorization has failed or has been rejected) in the response message to the second message.

[0145] Exemplarily, the authorization condition may include at least one of the following:

[0146] The identification of the first user is included in the authorized user identification information (or a list of authorized or allowed user identification information, such as which users are pre-configured on the service device as authorized users of the service device);

[0147] The association between the identifier of the first user (such as the MC ID or the MC IP) and the identifier of the gateway user equipment (such as the gateway UE ID) is included in the authorized association (or the authorized association list, such as the service device pre-configuring which gateway user equipment or gateway user equipments any MC ID (or MC IP) is allowed to access), or it can be understood that the service device has an association between the identifier of the first user and the identifier of the gateway user equipment;

[0148] The association between the identifier of the first user, the device information of the first user equipment, and the identifier of the gateway user equipment is included in the authorized association relationship (or the authorized association relationship list, such as the association relationship between the allowed MC ID (or MC IP) pre-configured on the serving device and the device information of the non-3GPP device and the gateway user equipment);

[0149] Data flow information verification passed;

[0150] The association between the device information of the first user equipment and the identifier of the gateway user equipment is included in the authorized association relationship (or the authorized association relationship list, such as which gateway user equipments are pre-configured on the serving device to allow any user equipment (such as a non-3GPP device) to connect, or which non-3GPP devices are pre-configured on the serving device to allow any gateway user equipment to connect);

[0151] According to the location information and / or user connection preference of the first user equipment, there is a connection corresponding to the first service identifier (such as GW MC service ID) accessed by the first user through other gateway user equipment; the gateway user equipment has available resources;

[0152] Or there are no available resources in the gateway user equipment, and there is a connection that can be preempted (for example, a connection with a user priority lower than the user priority of the first user and a service identifier corresponding to the first service identifier, or a connection with a service with a service priority lower than the service priority corresponding to the first service identifier).

[0153] In one possible implementation, after the service device determines that a connection corresponding to a first service identifier accessed by a first user through another gateway user device exists, the service device may send a preemption message to the other gateway user device or gateway device (i.e., the gateway device that sent the second message). The preemption message indicates that the connection corresponding to the first service identifier has been preempted by the first user. Optionally, the other gateway user device or gateway device may also send the preemption message to the user device corresponding to the connection corresponding to the preempted first service identifier. In an embodiment of the present application, the service device may also negotiate with the user device whether to preempt the previous connection corresponding to the first service identifier by sending the preemption message to the user device corresponding to the connection corresponding to the preempted first service identifier. If the user device agrees to preempt the previous connection, it may send a corresponding preemption response message to the service device. The preemption response message may carry information indicating agreement to preempt the previous connection. If the user device refuses to preempt the previous connection, it may send a corresponding preemption response message to the service device. The preemption response message may carry information indicating refusal to preempt the previous connection. The preemption at this time can also be understood as replacement / substitution, that is, interrupting the previous connection and retaining the current connection initiated by the gateway device.

[0154] For example, when a first user sends a message requesting authorization for a connection of a second user through a certain gateway user device (such as a first gateway user device), when the service device determines that there is a connection corresponding to the first service identifier accessed by the second user through another gateway user device (such as a second gateway device), the service device can send a preemption message to the first gateway user device or the second gateway device. The preemption message is used to indicate that the connection corresponding to the first service identifier is preempted. Optionally, the above-mentioned gateway user device can also send the preemption message to the first user device corresponding to the connection corresponding to the preempted first service identifier.

[0155] In another possible implementation, when the service device determines that there are no available resources for the gateway user equipment and that a connection that can be preempted exists, the service device may send a preemption message to the user equipment corresponding to the preempted connection. The preemption message is used to indicate that the resources of the preempted connection have been preempted by a high-priority user or a high-priority service. For example, taking the example of the preemptible connection including the third connection, the third connection may refer to a connection whose user priority is lower than the user priority corresponding to the first user identifier and whose service identifier is the first service identifier, or may refer to a connection whose service priority is lower than the service priority corresponding to the first service identifier.

[0156] When the third connection refers to a connection in which the user priority is lower than the user priority corresponding to the identifier of the first user and the service identifier is the connection corresponding to the first service identifier, the service device may send a preemption message to the user device corresponding to the third connection (e.g., the third user device). For example, when the service device sends the preemption message to the third user device, the preemption message first passes through the gateway user device to which the third user device is connected, and then the gateway user device to which the third user device is connected sends the preemption message to the third user device.

[0157] When the third connection refers to a connection whose service priority is lower than the service priority corresponding to the first service identifier, the service device may send a preemption message to the user device corresponding to the third connection (e.g., the first user device or the third user device). For example, when the service device sends a preemption message to the first user device, during the process of the service device sending the preemption message to the first user device, the preemption message first passes through the gateway user device connected to the first user device, and then the gateway user device connected to the first user device sends the preemption message to the first user device.

[0158] In addition, when the response message of the second message is used to indicate the authorization of the connection of the first user, the service device can carry the authorized (or allowed to be routed or allowed) data flow information (such as server IP triplet, IP quadruple (MC IP (used to indicate the permanent IP used by the MC user or the IP used by the non-3GPP device) + server triplet) or IP quintuple) in the second response message. Data flow can also be understood as packet, flow, traffic, data. The authorized data flow information can also be called an authorized flow filter, an authorized data filter, an authorized packet filter, an authorized traffic filter or a routing rule. The authorized data flow information may include information about one or more authorized data flows associated with the identifier of the first user. Optionally, the service device may also carry the authorized data flow information in other independent messages and send them to the gateway user device. After receiving the authorized data flow information, the gateway user device saves the authorized data flow information. Thereafter, the gateway user device can determine whether to route or reject the data flow from the first user device based on the authorized data flow information (or the authorized data flow information list). It is understandable that rejecting the data flow from the first user equipment may also mean discarding or not processing the data flow, or may also mean sending a routing rejection message (e.g., carrying information indicating routing rejection) to the first user equipment. After receiving the routing rejection message, the first user equipment may re-initiate a connection authorization process to request authorization for the rejected data flow information.

[0159] For example, taking the data stream sent by the first user device to the gateway user device as the first data stream, when the information contained in the first data stream (such as the destination IP address, URL, server IP triplet or IP quadruple, etc.) is included in the authorized data stream information, the gateway user device can route or forward the first data stream, for example, the first data stream can be routed or forwarded to the service device corresponding to the destination address of the first data stream. When the information contained in the first data stream is not included in the authorized data stream information, the gateway user device can send a third message to the user device. The third message is used to indicate that the first data stream is rejected, or it can also be used to indicate that the first data stream requires additional authorization.

[0160] Optionally, after the first user device subsequently exchanges data streams with the service device (including data streams for identity authentication, data streams for service authorization, data streams for call control, and data streams for the media plane), the above-mentioned data stream connection of the first user device may also be preempted by other high-priority users or high-priority services. At this time, the gateway user device of the first user device receives a preemption message sent by the service device, instructing to preempt the connection resources of the first user. The gateway user device of the first user device then stops routing the data stream of the first user device. It can be understood that the gateway device of the first user device can also perform similar actions of the gateway user device accessed by the third user device.

[0161] Optionally, after the service device completes step 203, the gateway user device may further execute step 204. By executing step 204, the first user device may be promptly notified of whether the service device has authorized the first user's connection. This facilitates the first user device to subsequently initiate corresponding business processes (such as user identity authentication, service authorization, and subsequent group calls, private calls, and other business processes) in a timely and accurate manner, and may reduce energy consumption caused by the first user device still sending corresponding business processes to the gateway user device when the first user's connection is not authorized, thereby making the business processes subsequently initiated by the first user device more accurate and effective. Optionally, executing step 204 may also avoid the problem of the service device not receiving the corresponding business request due to the corresponding business process initiated by the first user device when the first user's connection is not authorized.

[0162] Step 204: The gateway user equipment sends a response message of the first message to the first user equipment according to the response message of the second message. The first user equipment receives the response message of the first message.

[0163] In one possible implementation, when the response message of the second message is used to indicate authorization of the first user's connection, the gateway user equipment may carry information indicating that the authorization of the first user's connection has passed (or authorization is successful or authorization is allowed) in the response message of the first message. At this time, the response message of the first message may be used to indicate authorization (or permission) of the first user's connection.

[0164] In another possible implementation, when the response message of the second message is used to indicate the rejection of the first user's connection, the gateway user equipment may carry information in the response message of the first message to indicate that the authorization of the first user's connection has not passed (or authorization failed or authorization was rejected). At this time, the response message of the first message can be used to indicate that the first user's connection is not authorized (or not allowed or rejected).

[0165] Optionally, the gateway user equipment may also allocate a temporary identifier (such as a GM MC service ID) to the first user based on the response message of the second message. The temporary identifier may be used to assist the gateway user equipment in identifying the first user. The temporary identifier uniquely identifies a user on a gateway user equipment. Different gateway user equipment may be allocated the same temporary identifier. The temporary identifier is an application layer identifier on the GW-local reference point. Optionally, the response message of the first message may also carry the temporary identifier of the first user. In subsequent signaling interaction messages between the first user equipment and the gateway user equipment on the GW-local reference point, the first user equipment may use the temporary identifier to identify the first user.

[0166] In the embodiment of the present application, the response message to the first message may further include corresponding connection information, where the connection information is used to establish a service connection for the first user.

[0167] Exemplarily, the corresponding operations performed by the first user equipment after receiving the response message to the first message are introduced below through the following possible implementation methods.

[0168] Method 1: When the response message to the first message is used to indicate authorization of the connection of the first user, the first user device may initiate user identity authentication, service authorization, and subsequent group call, private call and other service processes to the service device.

[0169] Optionally, during the process in which the first user device can initiate user identity authentication, service authorization, and subsequent group calls, private calls, and other business processes to the service device, if the gateway user device receives a data stream (such as the first data stream) from the first user device, the gateway user device can determine whether the first data stream can be routed to the corresponding target service device based on the saved authorized data stream information. When the information of the first data stream is included in the authorized data stream information, the gateway user device can route or forward the first data stream to the corresponding target service device. When the information of the first data stream is not included in the authorized data stream information, the gateway user device can discard the first data stream or not process the first data stream. Optionally, the gateway user device can also send a third message to the first user device. The third message can be used to indicate that the first data stream is rejected, or it can also be used to indicate that the first data stream requires additional authorization. Thereafter, the first user device can initiate the authorization connection request process again for a specific data stream.

[0170] Method 2: When the response message to the first message indicates rejection of the first user's connection, the first user device does not need to initiate a corresponding service process, or may initiate a process for requesting authorization of the first user's connection again after a period of time.

[0171] Optionally, after the first user completes identity authentication, the first user can obtain one or more service identifiers (MC service ID(s)). Afterwards, the first user device can send the correspondence between the first user (such as the first user's MC ID or MC IP) and the one or more service identifiers to the service device. It should be understood that the first user device can send the correspondence between the first user and the one or more service identifiers to the gateway user device. Then, the service device can request the data flow information of the first user (such as the connection status of the first user) from other business service devices based on the second message. For example, taking the first service identifier as an example, the service device can obtain the number of connections of the first user from other business service devices based on the correspondence between the first user (or the first user's identifier) ​​and the first service identifier.

[0172] Optionally, after the first user uses the first user device to establish a connection to the corresponding service device, the first user device (such as the gateway client (MC gateway client) in the first user device) may send a fifth message to the service device (or, such as a gateway UE function module installed in the service device). The fifth message is used to indicate information about an established or terminated data flow (for example, it may include data flow information, GW MC service ID, MC ID (or MC IP), MC service ID list). At this time, the data flow information may include at least one of IP five-tuple information and the amount of data. For example, the information about the established or terminated data flow can be used by the service device (or, such as a gateway UE function module installed in the service device) to determine the resource usage on the gateway user device.

[0173] As can be seen from steps 201 to 204 above, by carrying the user identifier in the request message for requesting authorization of a user's connection, the gateway user device and the service device can accurately identify whether multiple request messages (or connection requests) are from the same user, and can also accurately determine whether the same user already has at least one connection. This allows for effective control of the connections of the same user and effective control of connection access for users connecting to the service device through the gateway user device, thereby enabling authorization of connections for individual users and effectively avoiding the problem of the same user occupying excessive resources and causing resource waste due to access to the service device through multiple gateway user devices. It should be understood that the user identifier carried in the request message can also help the gateway user device accurately identify whether the request message for requesting authorization of a connection from the same user device is from the same user. In addition, when available resources on the gateway user device are insufficient, the gateway user device can selectively preempt the connection resources of a certain service or a certain user based on the service priority or the user priority, thereby ensuring that the connection authorization request message of the first user can be forwarded to the service device and ensuring that the gateway user device has available resources to support the connection of the first user.

[0174] Based on the implementation scheme of the communication method illustrated in FIG2 above, the following takes the identification of the first user as MC ID or MC IP, the first user equipment as non-3GPP equipment 1, the second user equipment as non-3GPP equipment 2, the gateway user equipment as gateway UE1, the other gateway user equipment as gateway UE2, and the service device as MC Service Server as an example, and describes the communication method illustrated in FIG2 in detail through the specific example shown in FIG3. It can be understood that in the embodiment of the present application, the action performed by a certain network element can also be replaced by being performed by a functional component in the network element. In the embodiment of the present application, the functional component may, for example, include at least one of a chip, a chip system, a processor, and a processing unit.

[0175] FIG3 is a flow chart of another communication method provided in an embodiment of the present application. The communication method shown in FIG3 is applicable to an emergency mission service communication system architecture. As shown in FIG3, the specific process of the method may include:

[0176] Step 301: Non-3GPP device 1 sends a first connection authorization request message to gateway UE1. Gateway UE1 receives the authorization request message.

[0177] In one example, when the identifier of the first user is an MC ID, the first connection authorization request message carries the MC ID of the first user (e.g., user1) associated with the non-3GPP device 1. Exemplarily, the MC ID is used to identify the MC service user, such as the MC ID may refer to the account information of the first user. For example, the account information of the first user may refer to the account ID of the first user for logging into the client, or may refer to the identity account of the first user, or may refer to other information that can be used to distinguish different users.

[0178] In another example, when the first user's identifier is an MC IP, the first connection authorization request message carries the MC IP of the first user (e.g., user1) associated with non-3GPP device 1. A particular user can be identified by the MC IP. In this case, the communication method illustrated in FIG3 is applicable to scenarios where a non-3GPP device uses a permanent IP or an MC service user (or MC user) uses a permanent IP. For non-3GPP devices or MC service users, the permanent IP can be allocated by the gateway UE or pre-configured by the system.

[0179] For example, in addition to carrying the MC ID or MC IP, the first connection authorization request message may also carry at least one of the following: priority (such as service priority or user priority), data flow description information for which authorization is requested, user connection preferences (such as preemption priority or retention of existing connections priority or device priority list), location information of non-3GPP device 1, device information of non-3GPP device 1 (such as device number or SN number, etc.), security credentials, or GW MC service ID list or MC service list. The data flow description information is used to describe information about subsequent connections / flows on the MC client installed on the non-3GPP device 1, such as a URL list, a server IP triplet, or an IP quadruple (terminal IP + server IP triplet).

[0180] For the GW MC service ID, the GW MC service ID can be an identifier configured on the gateway UE1 and the MC gateway UE function module, used to indicate a service (for example, one or more of MCPTT, MCVideo, or MCdata). The GW MC service ID list can correspond to multiple services respectively, that is, to authorize the connections of multiple services. When the first connection authorization request message contains the GW MC service ID list, the connection / flow information mentioned above can be a sub-item of each GW MC service ID, that is, it represents multiple flows under one service. In addition, the first connection authorization request message can also be used to indicate the information of the gateway UE (such as gateway UE1), for example, it is allocated or managed by the gateway UE (such as gateway UE1). It can be understood that gateway UE1 is responsible for managing which non-3GPP devices use this group of IDs and how to use them. The GW MC service ID can be used to indicate the information of the MC gateway, and it can also be understood that when the MC gateway UE function receives the GW MC service ID, it can find one or more gateway UEs (or MC gateway UEs) corresponding to the GW MC service ID.

[0181] For MC service, it indicates the MC service type applicable (associated) to the first connection, for example, one or more of MCPTT, MCVideo, and MCData.

[0182] Optionally, the first connection authorization request message is used to request authorization for the connection of the first user.

[0183] For example, the first connection authorization request message may be sent by a gateway client (such as an MC gateway client) installed on the non-3GPP device 1. Optionally, the non-3GPP device 1 may further be installed with an MC client.

[0184] Step 302: Gateway UE1 sends a second connection authorization request message to the MC Service Server according to the first connection authorization request message. The MC Service Server receives the second connection authorization request message.

[0185] The second connection authorization request message may also be used to request authorization for the connection of the first user.

[0186] Optionally, when the MC Service Server includes an MC gateway UE function module, gateway UE1 (or the MC gateway UE server in gateway UE1) sends a second connection authorization request message to the MC gateway UE function module according to the first connection authorization request message when the first condition is met.

[0187] In an embodiment of the present application, in addition to carrying the information carried by the first connection authorization request message, the second connection authorization request message may also carry the identifier of gateway UE1, such as gateway UE ID, gateway user ID, gateway UE's MC service ID, GW MC service ID or gateway ID list.

[0188] For example, whether the first condition is met can be understood as gateway UE1 (or the MC gateway UE server in gateway UE1) performing at least one of the following authorization checks on the connection of the first user requested by the first connection authorization request message to determine whether the connection of the first user requested by the first connection authorization request message is authorized.

[0189] (1) Gateway UE1 (or the MC gateway UE server in Gateway UE1) checks the device information of the non-3GPP device 1 to determine whether the non-3GPP device 1 is a device that is allowed to serve / connect, thereby determining whether the first user's connection is authorized. For example, the device information of the devices allowed to serve is configured in the MC gateway UE server on Gateway UE1. When the device information of the non-3GPP device 1 carried in the first connection authorization request message is included in the device information of the devices allowed to serve, Gateway UE1 (or the MC gateway UE server in Gateway UE1) determines that the first user's connection can be authorized.

[0190] (2) gateway UE1 (or the MC gateway UE server in gateway UE1) determines whether the connection of the first user is authorized based on the location information of the non-3GPP device 1. In one example, when the device is located in a specific area, gateway UE1 (or the MC gateway UE server in gateway UE1) determines that the authorization is passed. In another example, gateway UE1 (or the MC gateway UE server in gateway UE1) calculates the distance between gateway UE1 and the non-3GPP device 1, and determines whether the authorization is allowed based on the distance. For example, when the distance between gateway UE1 and the non-3GPP device 1 is less than a distance threshold, gateway UE1 (or the MC gateway UE server in gateway UE1) determines that the connection of the first user can be authorized.

[0191] (3) Gateway UE1 (or the MC gateway UE server in Gateway UE1) determines whether the association between the device information of the non-3GPP device 1 and the MC ID is included in the associations that allow authorization (such as a list of associations that allow authorization), thereby determining whether the connection of the first user is authorized. For example, when the association is included in the associations that allow authorization, Gateway UE1 (or the MC gateway UE server in Gateway UE1) determines that the connection of the first user can be authorized. In this way, the method can avoid situations where the device is stolen or the user uses the wrong device.

[0192] (4) Gateway UE1 (or the MC gateway UE server in Gateway UE1) determines whether the first user's connection is authorized by determining whether the first user already has a connection for the same service or whether the number of connections exceeds the upper limit for a single user per service (e.g., the upper limit is 1 or a value greater than 1). If the upper limit is 1, the situation is the same as if the current user already has a connection for the same service.

[0193] For example, if the first user already has a connection for the same service or the number of connections for the first user exceeds the upper limit for a single user per service, gateway UE1 (or the MC gateway UE server in gateway UE1) may send a response message to the first connection authorization request message to the non-3GPP device 1. The response message to the first connection authorization request message is used to indicate the rejection of the first user's connection authorization request (and indicate the specific reason for the rejection, such as the existence of a connection for the same service or the number of connections exceeding the upper limit). Afterwards, the first user may disconnect some flows and then initiate connection authorization again with gateway UE1.

[0194] For another example, when the first user has no connection for the same service or the number of connections of the first user does not exceed the upper limit of the number of connections for a single service of a single user, gateway UE1 (or the MC gateway UE server in gateway UE1) determines that the connection of the first user can be authorized.

[0195] (5) Gateway UE1 (or the MC gateway UE server in Gateway UE1) determines whether the connection of the first user is authorized by determining whether there are available resources on Gateway UE1.

[0196] For example, a simple resource management method is to configure a fixed number of connections / users to be served. For example, when the number of connections / users being served on gateway UE1 exceeds the limit, gateway UE1 can preempt the connection resources of a certain service (which can be one or more) of other users based on the higher priority of the currently requested service (for example, the service priority (such as the priority of MCPTT is higher than the priority of MCvideo), the priority of the user (the priority of the dispatcher / commander is higher than the priority of ordinary users). At this time, gateway UE1 sends a connection preemption request to the user on the selected preempted non-3GPP device (such as non-3GPP device 2), and can indicate the preemption reason in the connection preemption request, such as the preemption reason can be that the connection resources of a certain service are preempted by a high-level user or a high-level service, or the connection preemption request can carry information about the preempted service or preempted data flow. Optionally, the preempted non-3GPP device can also reply with an Acknowledgement (ACK) message. Thereafter, the gateway UE1 may refuse to route the preempted data flow of the preempted user. A dispatcher generally refers to a user with special permissions, and may be a member of one or several groups, or a super user.

[0197] Step 303: The MC Service Server performs an authorization check on the connection of the first user requested in the second connection authorization request message according to the second connection authorization request message.

[0198] Optionally, the MC Service Server determines whether the connection requested by the first user in the second connection authorization request message is authorized by performing at least one of the following authorization checks on the connection requested by the first user in the second connection authorization request message. When the MC Service Server includes an MC gateway UE function module, step 303 may be performed by the MC gateway UE function module.

[0199] (1) When the identifier of the first user carried in the second connection authorization request message is an MC ID, the MC Service Server may determine whether the first user is an authorized user by checking the MC ID + (optionally, security credentials) carried in the second connection authorization request message, thereby determining whether the first user's connection is authorized. For example, after the MC ID + (optionally, security credentials) carried in the second connection authorization request message are successfully verified, the MC Service Server determines that the first user is an authorized user and thus determines that the first user's connection is authorized.

[0200] When the identifier of the first user carried in the second connection authorization request message is an MC IP, the MC Service Server can determine whether the first user is an authorized user by checking the MC IP + (optionally, security credentials) carried in the second connection authorization request message, thereby determining whether the first user's connection is authorized. For example, after the MC IP + (optionally, security credentials) carried in the second connection authorization request message are successfully verified, the MC Service Server determines that the first user is an authorized user and that the first user's connection is authorized.

[0201] (2) When the identifier of the first user carried in the second connection authorization request message is an MC ID, the MC Service Server can determine whether the MC ID is allowed to access through gateway UE1 to determine whether the connection of the first user is authorized.

[0202] For example, the MC Service Server may determine whether to allow the MC ID to access through gateway UE1 based on the identifier of gateway UE1 carried in the second connection authorization request message. For example, when determining that the MC ID is allowed to access through gateway UE1, the MC Service Server determines that the first user's connection can be authorized.

[0203] When the identifier of the first user carried in the second connection authorization request message is the MC IP, the MC Service Server may determine whether the MC IP is allowed to access through the gateway UE1, thereby determining whether the connection of the first user is authorized.

[0204] For example, the MC Service Server can determine whether to allow the MC IP to access through gateway UE1 based on the identifier of gateway UE1 carried in the second connection authorization request message. For example, when determining that the MC IP is allowed to access through gateway UE1, the MC Service Server determines that the first user's connection can be authorized.

[0205] (3) The MC Service Server determines whether the connection of the first user is authorized by determining whether the association between the device information of the non-3GPP device 1 and the identifier of the gateway UE1 is allowed.

[0206] For example, the MC Service Server configures information (such as identifiers or device information) of the gateway UE to which non-3GPP devices are allowed to connect, or configures information (such as identifiers or device information) of non-3GPP devices allowed to connect on the gateway UE. For example, when the association between the device information of non-3GPP device 1 and the identifier of gateway UE 1 is included in a configured association (such as a configured association list), the MC Service Server determines that the connection of the first user can be authorized.

[0207] (4) When the identifier of the first user carried in the second connection authorization request message is the MC ID, the MC Service Server determines whether the connection of the first user is authorized by determining whether the association between the MC ID, the device information of the non-3GPP device 1, and the identifier of the gateway UE1 is allowed.

[0208] For example, the MC Service Server may determine whether the association between the MC ID, the device information of non-3GPP device 1, and the identifier of gateway UE 1 is permitted based on the association configured on the MC Service Server among the permitted MC IDs, the device information of non-3GPP devices, and the identifier of gateway UE 1. For example, when the association between the MC ID, the device information of non-3GPP device 1, and the identifier of gateway UE 1 is included in the configured association, the MC Service Server determines that the connection of the first user can be authorized.

[0209] When the identifier of the first user carried in the second connection authorization request message is MC IP, the MC Service Server determines whether the connection of the first user is authorized by determining whether the association between the MC IP, the device information of the non-3GPP device 1, and the identifier of the gateway UE1 is allowed.

[0210] For example, the MC Service Server may determine whether the association between the MC IP, the device information of non-3GPP device 1, and the identifier of gateway UE 1 is permitted based on the association configured on the MC Service Server among the permitted MC IP, the device information of non-3GPP device 1, and the identifier of gateway UE 1. For example, when the association between the MC IP, the device information of non-3GPP device 1, and the identifier of gateway UE 1 is included in the configured association, the MC Service Server determines that the connection of the first user can be authorized.

[0211] (5) When the second connection authorization request message carries the data flow description information requesting authorization, the MC Service Server determines whether the first user's connection is authorized by checking the data flow description information. For example, if the data flow description information includes a URL, the MC Service Server resolves the URL to a corresponding server IP address. If the server IP address is determined to be the MC Service Server's IP address, the first user's connection is authorized.

[0212] (6) When a connection for the first user to access the same service (e.g., MCPTT) through another gateway UE already exists, the MC Service Server can take the following possible actions. Optionally, the MC Service Server can determine whether a connection for the first user to access the same service already exists by checking whether there is another GW MC service ID for the same service.

[0213] Operation a: The MC Service Server may send a response message to the second connection authorization request message to gateway UE1. The response message to the second connection authorization request message indicates the rejection of the first user's connection authorization request (and indicates the specific reason for the rejection, such as the existence of a connection for the same service). Subsequently, gateway UE1 may also send a response message to the first connection authorization request message to the non-3GPP device 1 based on the response message to the second connection authorization request message. The response message to the first connection authorization request message indicates the rejection of the first user's connection authorization request (and indicates the specific reason for the rejection, such as the existence of a connection for the same service).

[0214] For example, the MC Service Server may reject the first user's connection authorization request based on the first user's ongoing data flow (such as ongoing traffic) on another gateway UE (such as gateway UE2), or based on system preferences (such as settings to retain the original connection, give priority to specific devices, etc.) or user connection preferences (reported or pre-configured user connection preferences indicate retaining the most recently existing connection), or based on location / distance, etc. Specifically, the MC Service Server may also reject a specific service connection authorization, and more specifically, may also reject a specific data flow under the service that is indicated as rejected in the response message to the first connection authorization request message, so that the first user can, after removing the rejected data flow / service, reinitiate the authorization connection process with the non-rejected data flow / service information.

[0215] Operation b: The MC Service Server authorizes the current connection of the first user to preempt (or disconnect, replace, or substitute) a connection accessed through another gateway UE (such as gateway UE2).

[0216] In one possible implementation, the MC Service Server may send a connection preemption request (or a connection disconnection request or a notification message) to the gateway UE2 based on the user's connection preference, the location information of the non-3GPP device 1, or one or more of the data flows that the gateway UE2 has no ongoing, and indicate the preemption reason or the disconnection reason, such as shown in FIG3 (a, sending a connection preemption request). For example, the MC Service Server may also carry information about the preempted service or preempted data flow in the connection preemption request (or connection disconnection request or notification message). If the preempted service or preempted data flow is not specified, all services or all data flows are preempted by default. Optionally, the gateway UE2 may further send a connection preemption request (or a connection disconnection request or a notification message) to the non-3GPP device 2 (or the MC gateway client of the non-3GPP device 2). After receiving the connection seizure request (or connection disconnection request or notification message), the non-3GPP device 2 (or the MC gateway client of the non-3GPP device 2) may also send a connection seizure response / indication message (eg, indicating to retain the original connection) to the MC Service Server.

[0217] In another possible implementation, the MC Service Server may, based on one or more of the user's connection preference, the location information of the non-3GPP device 1, or the fact that gateway UE 2 has no ongoing data flows, send a connection preemption request (or a connection disconnection request or notification message) to the non-3GPP device 2 (or the MC gateway client of the non-3GPP device 2) via gateway UE 1, in order to negotiate with the non-3GPP device 2 (or the MC gateway client of the non-3GPP device 2) whether to preempt the original connection, as illustrated in FIG3 (b, sending a connection preemption request). After negotiating to preempt the original connection, the MC Service Server still sends a connection preemption request (or a connection disconnection request or notification message) to gateway UE 2 and indicates the preemption reason or disconnection reason. In this case, gateway UE 2 does not need to send a connection preemption request (or a connection disconnection request or notification message) to the non-3GPP device 2 (or the MC gateway client of the non-3GPP device 2).

[0218] Operation c: When the number of connections / service users / data flows (IP flows) on gateway UE1 reaches the upper limit, the following operations are possible.

[0219] c1. Same-Service Preemption: The MC Service Server preempts the connection of a user with the same service and a lower priority than the first user, based on the user priority of the first user. If the user has an ongoing data flow, the MC Service Server can specify the specific data flow (such as the IP 5-tuple) to be preempted.

[0220] c2. Cross-service preemption: The MC Service Server preempts the connection corresponding to the service whose service priority is lower than the service priority corresponding to the MC service ID based on the service priority corresponding to the MC service ID carried in the second connection authorization request message. For example, if the service corresponding to the MC service ID is MCPTT and the other service is MCData, where the service priority of MCPTT is higher than the service priority of MCData, the MC Service Server can preempt the connection corresponding to MCData of other non-3GPP devices. If other non-3GPP devices have ongoing data flows, the MC Service Server can indicate which specific data flow (such as IP five-tuple) to preempt.

[0221] The following describes the process of determining ongoing traffic:

[0222] The MC Service Server obtains ongoing traffic information (such as the MC ID, IP address of the non-3GPP device, or the MC IP address and IP address of the non-3GPP device) from other service servers (other MC servers). This allows it to accurately preempt connections of non-3GPP devices that have no ongoing traffic. For example, the MC Service Server sends a query message to another MC server. The query message may carry (the IP address of the non-3GPP device, or the IP address of the non-3GPP device + the MC ID, or the IP address of the non-3GPP device + the MC IP address) to query the other MC server for the connection status information (or connection status) of the user corresponding to the MC ID or MC IP address. After receiving the query message, the other MC server queries the connection status information of the user corresponding to the MC ID or MC IP address and feedbacks the connection status information (such as whether a connection exists and the number of connections) to the MC Service Server. Optionally, the MC Service Server may also determine whether a non-3GPP device has ongoing traffic based on the correspondence reported in step 306 and the information about established or terminated data flows reported in step 307.

[0223] c3. Consider if the user has multiple devices logged in, such as UE, non-3GPP device 1 (requesting MCPTT through gateway UE1), and non-3GPP device 2 (requesting MCData through gateway UE2). The MC Service Server can determine whether to preempt other connections of the user by considering whether the user has directly used the MC service UE to access the server. If so, it will choose to preempt. At this time, if it is not with the MC service server, it is also necessary to introduce interaction between servers to obtain the MC ID from other MC service servers. The service authorization of this user has a scenario where the user directly uses the MC UE to access the server. It should be noted that if the identifier of the first user carried in the second connection authorization request message is MC IP, the above operation c3 does not apply.

[0224] Optionally, the MC Service Server may select one or more preempted non-3GPP devices (such as non-3GPP device 2) according to the above operation c, and may send a connection preemption request to the selected non-3GPP device (such as non-3GPP device 2) through gateway UE1 (or the MC gateway UE server in gateway UE1), such as (b, sending a connection preemption request) as shown in Figure 3. In one example, the connection preemption request may carry at least one of the MC ID, MC service ID, or GW MC service ID. In another example, when the identifier of the first user carried by the second connection authorization request message is the MC IP, the above operation c3 is not applicable. In this case, the connection preemption request may carry at least one of the MC IP, MC service ID, or GW MC service ID. Optionally, the connection preemption request may also carry information about the preempted service or preempted data flow. If the preempted service or preempted data flow is not specified, all services or all data flows are preempted by default. Optionally, the preempted non-3GPP device (or the MC gateway client in the preempted non-3GPP device) may send an ACK message to the MC Service Server.

[0225] Step 304: The MC Service Server sends a response message to the second connection authorization request message to the gateway UE1. The gateway UE1 receives the response message to the second connection authorization request message.

[0226] In one possible implementation, when the authorization check of the connection of the first user requested by the second connection authorization request message passes, the MC Service Server may carry information indicating that the authorization has passed (or the authorization is successful) in the response message of the second connection authorization request message. In one example, the MC Service Server may also carry the authorized data flow information associated with the first user (such as a server IP triplet, an IP quadruple (MC IP (used to indicate a permanent IP used by the MC user or an IP used by a non-3GPP device) + a server triplet) or an IP quintuple) in the response message of the second connection authorization request message. In another example, the MC Service Server may also carry the authorized data flow information associated with the first user in a separate message and send it to gateway UE1 (or the MC gateway UE server in gateway UE1).

[0227] In another possible implementation, when the authorization check for the first user's connection requested in the second connection authorization request message fails, the MC Service Server may include information indicating the authorization failure (or authorization failure or authorization rejection) in a response message to the second connection authorization request message. Optionally, the MC Service Server may also include information about the rejected service or rejected data flow in the response message to the second connection authorization request message.

[0228] Step 305: Gateway UE1 sends a response message to the first connection authorization request message to the non-3GPP device 1 according to the response message to the second connection authorization request message. The non-3GPP device 1 receives the response message to the first connection authorization request message.

[0229] In one possible implementation, when the response message to the second connection authorization request message indicates authorization is passed, gateway UE1 (or the MC gateway UE server in gateway UE1) may carry information indicating authorization is passed (or authorization is successful) in the response message to the first connection authorization request message.

[0230] In one example, when the response message to the second connection authorization request message carries the authorized data flow information associated with the first user, gateway UE1 (or the MC gateway UE server in gateway UE1) can obtain the authorized data flow information associated with the first user from the response message to the second connection authorization request message and save the authorized data flow information associated with the first user. The authorized data flow information associated with the first user can be used to subsequently perform corresponding routing operations for data flows from non-3GPP devices.

[0231] In another example, when the response message of the second connection authorization request message does not carry the authorized data flow information associated with the first user, gateway UE1 (or the MC gateway UE server in gateway UE1) can obtain the authorized data flow information associated with the first user from other messages from the MC Service Server and save the authorized data flow information associated with the first user.

[0232] In another possible implementation, when the response message to the second connection authorization request message indicates that the authorization failed, gateway UE1 (or the MC gateway UE server in gateway UE1) may carry information indicating the authorization failure (or authorization rejection) in the response message to the first connection authorization request message.

[0233] Step 306: When the response message to the first connection authorization request message indicates that the authorization is passed, the non-3GPP device 1 initiates a service process to the MC Service Server.

[0234] Optionally, when the response message to the first connection authorization request message indicates that the authorization is passed, the non-3GPP device 1 may initiate user identity authentication, service authorization, and subsequent group call, private call and other service processes to the MC Service Server.

[0235] For example, when the non-3GPP device 1 (or the MC client in the non-3GPP device 1) initiates a service process to the MC Service Server, when one or more service data packets sent by the non-3GPP device 1 to the MC Service Server pass through the gateway UE1 (or the MC gateway UE server in the gateway UE1), the gateway UE1 (or the MC gateway UE server in the gateway UE1) can determine, based on the stored authorized data flow information, for each of the one or more service data packets (or simply referred to as data packets), whether the information included in the data packet (such as an IP triplet, an IP quadruple, or an IP quintuple) is included in the authorized data flow information.

[0236] When the information included in the data packet is included in the authorized data flow information, gateway UE1 (or the MC gateway UE server in gateway UE1) can route the data packet to the corresponding MC Service Server (such as the MC Service Server corresponding to the destination address). When the information included in the data packet is not included in the authorized data flow information, gateway UE1 (or the MC gateway UE server in gateway UE1) can discard the data packet or not process the data packet. Optionally, gateway UE1 (or the MC gateway UE server in gateway UE1) can also send a notification message to the non-3GPP device 1. Exemplarily, the notification message can carry an indication that the data packet is rejected or that the data packet requires additional authorization. Thereafter, the non-3GPP device 1 (or the MC gateway client in the non-3GPP device 1) can re-initiate the authorization connection process for the specific data packet.

[0237] Step 307: The non-3GPP device 1 sends the correspondence between the first user's identifier and the service identifier (MC service ID) to the MC Service Server.

[0238] For example, the non-3GPP device 1 may carry the correspondence between the first user's identifier and one or more MC service IDs in a message and send it to the MC Service Server. The MC service ID may also be used as an identifier to distinguish different users.

[0239] Optionally, after the identity authentication of the first user is completed, the first user can obtain the MC service ID(s). Afterwards, the non-3GPP device 1 (or the MC gateway client in the non-3GPP device 1) can send the correspondence between the first user's identifier (such as MC ID or MC IP) and the MC service ID(s) to the MC Service Server. The correspondence can be used by the MC Service Server to request the connection status information (such as the number of connections) of the first user from other MC servers. Optionally, the non-3GPP device 1 (or the MC gateway client in the non-3GPP device 1) can also send the correspondence between the first user's identifier (such as MC ID or MC IP) and the MC service ID(s) to the gateway UE1 (or the MC gateway UE server in the gateway UE1).

[0240] Step 308: The non-3GPP device 1 sends information about the established or terminated data flow to the MC Service Server.

[0241] Exemplarily, the non-3GPP device 1 may carry information of established or terminated data flows (such as data flow information, MC ID (or MC IP), and MC service ID list) in a message and send it to the corresponding MC Service Server.

[0242] After non-3GPP device 1 (or the MC client in non-3GPP device 1) establishes a connection to the corresponding MC Service Server, non-3GPP device 1 (or the MC client in non-3GPP device 1) may send information about established or terminated data flows to the corresponding MC Service Server. This information about established or terminated data flows is used by the MC Service Server to determine resource usage on gateway UE 1. Optionally, non-3GPP device 1 (or the MC client in non-3GPP device 1) may also send information about established or terminated data flows to gateway UE 1 (or the MC gateway UE server in gateway UE 1).

[0243] It can be seen from the above steps 301 to 308 that by carrying the identifier of the first user in the connection authorization request message initiated by a certain user (such as the first user), the gateway user device or service device (such as a service server) can promptly and accurately connect to the user from which the connection requested for authorization by the authorization request message comes. In this way, effective access control can be achieved for users who access the connection using the gateway user device and the data streams initiated by the user, thereby preventing a user from connecting to the service device through multiple gateway user devices, that is, preventing a user from occupying too many resources. By determining whether there are available resources on the gateway user device (such as determining whether the number of connections, users, or data streams served by the gateway user device exceeds the upper limit), it is also possible to further control the resource usage on the gateway user device to be maintained within a reasonable range. In addition, when the number of connections for a single user and a single service exceeds the upper limit, the gateway user device can initiate a selection of which connection to use for the user among multiple connections.

[0244] Figure 4 exemplarily shows a flow chart of another communication method provided by an embodiment of the present application. The method is applicable to the communication system architecture shown in Figure 1a, Figure 1b or Figure 1c. The method flow can be implemented by data interaction between multiple communication devices (such as a first communication device, a second communication device or a third communication device). Optionally, the first communication device can be a user device (such as a first user device or a second user device) or a component that can support the user device to implement the functions required for the method (such as a chip, a chip system or a circuit, etc.), the second communication device can be a gateway user device or a component that can support the gateway user device to implement the functions required for the method (such as a chip, a chip system or a circuit, etc.), and the third communication device can be a service device or a component that can support the service device to implement the functions required for the method (such as a chip, a chip system or a circuit, etc.). Exemplarily, the user equipment may be an emergency task service user equipment as shown in FIG1a , or may be an MCPTT UE as shown in FIG1b , or may be a non-3GPP device as shown in FIG1c ; the gateway user equipment may be a gateway user equipment as shown in FIG1c ; the service equipment may be an emergency task service server as shown in FIG1a , or may be an MCPTT server as shown in FIG1b , or may be an emergency task service server or a general service core or a session initiation protocol core or a gateway user equipment functional module or a hypertext transfer protocol proxy module as shown in FIG1c . It should be understood that the communication method provided in the embodiment of the present application is also applicable when a gateway user equipment is introduced between the emergency task service user equipment and the emergency task service server as shown in FIG1a , or the communication method provided in the embodiment of the present application is also applicable when a gateway user equipment is introduced between the MCPTT UE and the MCPTT server as shown in FIG1b . Optionally, in the implementation scheme of the communication method illustrated in FIG4 , the gateway user equipment (such as gateway UE) may not need to control the control plane connection of a certain user equipment (such as the first user equipment), but may perform access control on the data flow of the user plane. That is, the implementation scheme of the communication method illustrated in FIG4 can be understood as a user plane control scheme. In order to facilitate the introduction of the technical solution provided in the embodiment of the present application, the following takes the first communication device as the first user equipment, the second communication device as the gateway user equipment, and the third communication device as the service device as an example to introduce the process of implementing the communication method by data interaction between the first communication device, the second communication device, and the third communication device. As shown in FIG4 , the method includes:

[0245] Step 401: A first user equipment sends a first data packet to a gateway user equipment, and the gateway user equipment receives the first data packet.

[0246] Optionally, before the first user equipment sends the first data packet to the gateway user equipment, the first user equipment establishes a non-3GPP transmission connection (such as a Bluetooth connection or a WI-FI connection) with the gateway user equipment, which can be understood as the network access method of the first user equipment is non-3GPP access. For example, the first user equipment is a non-3GPP device. For example, the first user equipment can be installed with, but not limited to, a gateway client (such as an MC gateway client), an emergency task client (MC client), an HTTP client, or a signaling user agent module.

[0247] Exemplarily, the first data packet may include a first message (such as an authentication request message), and the first message may include an identifier of a first user associated with the first user device (such as an MC ID or an MC IP). For example, taking the first user as a certain user (such as user1), the identifier of user1 may be MC ID1 or MC IP1.

[0248] Optionally, the first message is used to request an authentication device (such as an identity authentication management server) to perform identity authentication on the first user.

[0249] In an embodiment of the present application, before the first user device sends the first data packet to the gateway user device, the identity authentication management server (or configuration management server) can provide the gateway user device with data flow information that is allowed to be routed (for example, it can be the address information of the identity authentication management server (such as the IP address and port number of the identity authentication management server, or the URL), or it can also be the characteristic information of the user authentication message (such as the message header name, the message header information, such as the header information carried in the HTTP message, can indicate that the message is used for identity authentication)), so that the gateway user device can also identify whether the user authentication message is used for identity authentication based on the characteristic information of a certain user authentication message, thereby determining whether the user authentication message needs to be routed to the identity authentication management server. The gateway user device receives and saves the address information of the identity authentication management server that is allowed to be routed or the characteristic information of the user authentication message. The data flow information that is allowed to be routed can also be referred to as an allowed flow filter, an allowed data filter, an allowed packet filter, an allowed traffic filter, or a routing rule.

[0250] Optionally, after the gateway user device completes identity authentication with the identity authentication management server, the address information of the identity authentication management server that is allowed to be routed or the characteristic information of the user authentication message may be sent to the gateway user device by the configuration management server on the network side. The gateway user device receives and stores the address information of the identity authentication management server that is allowed to be routed or the characteristic information of the user authentication message.

[0251] Step 402: If the destination address of the first data packet is included in the authorized data flow information, the gateway user equipment forwards the first data packet to the service device. The service device receives the first message in the first data packet.

[0252] Optionally, the gateway user equipment may forward a first message encapsulated in a first data packet to a service device (e.g., an authentication device). For example, the first message may include an identifier of a first user associated with the first user equipment. The first message is used to request identity authentication for the first user, and the authentication device (e.g., an identity authentication server) is used to provide identity authentication services to the first user.

[0253] In one possible implementation, when the gateway user device stores data flow information that is allowed to be routed, if the gateway user device determines that the destination address of the first data packet is included in the data flow information that is allowed to be routed, the first message in the first data packet can be forwarded to a service device (such as an authentication device).

[0254] In another possible implementation, when the gateway user device stores characteristic information of a user authentication message, if the gateway user device determines that the characteristic information of the first message included in the first data packet matches the characteristic information of the user authentication message, the first data packet can be forwarded to the identity authentication management server.

[0255] Furthermore, the gateway user equipment may further parse the application layer message in the first data packet, and when determining that it is an identity authentication message or an allowed URL, it may forward the first message in the first data packet to a service device (such as an authentication device).

[0256] Step 403: If the first user identity authentication is successful, the service device sends the authorized routing address information to the gateway user device. The gateway user device receives the authorized routing address information. The authorized routing address information may also be referred to as an authorized flow filter, an authorized data filter, an authorized packet filter, an authorized traffic filter, or a routing rule.

[0257] Step 404: The gateway user equipment routes or rejects the data flow from the first user equipment according to the authorized routing address information.

[0258] In the embodiment of the present application, the service device is used to provide corresponding business services to the first user. Exemplarily, the service device may include but is not limited to an identity authentication management server, a configuration management server, or a business server (such as an MC Service Server or other business servers (such as a SIP Core)).

[0259] Exemplarily, the authorized (or allowed) routing address information (or routing address information list) may include the communication address of an authorized service device (such as a service server), or may include first routing address information (such as the IP address and port number / URL of the service server (particularly, the IP address and port number for a SIP connection), or the address and port number / URL of a SIP core) and second routing address information (such as the IP address and port number of a service flow (for example, the IP address and port number of a SIP session, or the IP address and port number of a media plane)). The first routing address information may indicate the authorized service communication address of the service device (such as a service server) and / or the control plane communication address of the authorized service device (such as a service server); the second routing address information may be used to indicate the user plane communication address of the authorized service device (such as a service server).

[0260] It can be understood that the gateway user equipment rejecting the data flow from the first user equipment may mean that the gateway user equipment discards the data flow, or may also mean that the gateway user equipment does not process the data flow.

[0261] In an embodiment of the present application, after the service device (such as an identity authentication management server) authenticates the first user and passes the identity authentication, the first routing address information may be provided by the identity authentication management server to the gateway user device, or may be provided by the configuration management server to the gateway user device, or may be provided by the service server to the gateway user device. The second routing address information may be provided by the identity authentication management server to the gateway user device, or may be provided by the configuration management server to the gateway user device, or may be provided by the service server to the gateway user device.

[0262] Optionally, after the service device authenticates the first user, it may also send an authentication response message to the first user device. The authentication response message may be used to indicate that the first user's identity authentication has passed (or succeeded), or it may also be used to indicate that the first user's identity authentication has failed (or failed). In the process of the identity authentication management server sending the authentication response message to the first user device, the authentication response message first passes through the gateway user device, and the gateway user device forwards the authentication response message to the first user device.

[0263] As an example, the first routing address information and the second routing address information may be carried in one message and provided to the gateway user equipment, or may be carried in two messages and provided to the gateway user equipment respectively.

[0264] Exemplarily, the following takes the example of providing the first routing address information and the second routing address information to the gateway user equipment in two messages as an example to introduce the implementation process of the service device providing the first routing address information and the second routing address information to the gateway user equipment.

[0265] After the service device authenticates the first user, it can send the first routing address information to the gateway user device. Optionally, the first routing address information can be encapsulated in a message and sent. For example, taking the first routing address information encapsulated in a message (such as message 1), message 1 can include the first routing address information (or a list of authorized service devices). After receiving the third message, the gateway user device obtains the first routing address information from message 1 and saves the first routing address information. Thereafter, upon receiving the second data packet from the first user device, the gateway user device can determine whether to route or reject the second data packet based on the first routing address information. Optionally, the second data packet can be triggered by the first user device receiving an authentication response message, or it can be triggered by the first user device actively after a period of time after sending the first data packet. The second data packet (or the service authorization request message included in the second data packet) can be used to request service authorization for the first user, or the second data packet (or the service registration request message included in the second data packet) can be used to request service registration (such as SIP registration) for the first user. When the destination address of the second data packet is included in the first routing address information, the gateway user equipment may route or forward the second data packet to the service device (such as a service server (such as an MCPTT server)) corresponding to the destination address of the second data packet. When the destination address of the second data packet is not included in the first routing address information, the gateway user equipment may discard or not process the second data packet. Optionally, the gateway user equipment may also send a response message to the first user equipment refusing to route the second data packet, the response message being used to indicate that the second data packet is rejected or discarded, or the response message may also carry a specific reason for indicating that the second data packet is rejected or discarded.

[0266] After receiving the second data packet, if the service device completes service authorization (or service registration) for the first user, it may send a service authorization response message (or service registration response message) to the first user device. The service authorization response message is used to indicate that service authorization is complete, and the service registration response message is used to indicate that service registration is complete. In the process of the service device sending the service authorization response message (or service registration response message) to the first user device, the service authorization response message (or service registration response message) first passes through the gateway user device, and the gateway user device forwards the service authorization response message (or service registration response message) to the first user device.

[0267] Optionally, after the service device completes service authorization (or service registration) for the first user, the service device (such as a business server or configuration management server) may provide the gateway user device with second routing address information. Optionally, the second routing address information may be encapsulated in a message and sent. For example, assuming the second routing address information is encapsulated in a message (such as message 2), after receiving message 2, the gateway user device may obtain the second routing address information from message 2 and store the second routing address information. Subsequently, when the gateway user device receives a data packet (or data stream, such as data packet 1, e.g., data packet 1 is a group call request) from the first user device, it may determine whether to route or reject data packet 1 based on the locally stored second routing address information. When the destination address of data packet 1 is included in the second routing address information, the gateway user device may route data packet 1 to the service device corresponding to the destination address of data packet 1. After receiving data packet 1, the service device may perform corresponding processing on data packet 1 and then send a response message to the first user device regarding data packet 1. When the destination address of data packet 1 is not included in the second routing address information, the gateway user device may discard or not process data packet 1.

[0268] In addition, in an embodiment of the present application, when any of the following situations occurs, the service device (such as a service server) can update the first routing address information and / or the second routing address information to obtain the third routing address information: the first user has at least one connection (which can be understood as the number of connections of the first user exceeds the upper limit) (for example, the first user corresponds to multiple IP addresses / SIP addresses); or the number of connections or the number of users or the number of data streams served by the gateway user equipment is greater than the second quantity threshold; or the identifier of the first user has been deregistered, logged in, or logged out from the service device; or the set time period expires (for example, the time interval from the last time the allowed (or authorized) routing address information was provided to the gateway UE1 is greater than or equal to the time threshold, or the time period from the last time the allowed routing address information was provided meets the time threshold); or the connection of the first user is preempted by its connection.

[0269] Afterwards, the service device can send the third routing address information to the gateway user device. Since the service device provides updated routing address information, this will cause the user to re-initiate the authentication and authorization process the next time they send a specific service. After receiving the third routing address information, the gateway user device can update the first routing address information and / or second routing address information stored in the gateway user device according to the third routing address information. Thereafter, when the gateway user device receives a data packet (such as the third data packet) from the first user device, it can determine whether to route or reject the third data packet based on the updated first routing address information and / or second routing address information. When the destination address of the third data packet is not included in the updated first routing address information and / or second routing address information (i.e., the third routing address information), the gateway user device can send a third message to the first user device. The third message is used to indicate the refusal to route the third data packet. Furthermore, the third message can also be used to instruct the first user device to re-initiate identity authentication or re-initiate service authorization.

[0270] It can be understood that the service device provides the updated data flow address allowed for routing to the gateway user equipment, which can also be understood as revoking / disabling / invalidating the data flow address allowed for routing before.

[0271] It can be seen from the above steps 401 to 404 that the gateway user device can accurately determine whether to route or reject the data flow from a certain user device (such as the first user device) based on the authorized routing address information provided by the service device (such as the identity authentication management server or the configuration management server or the business server), thereby effectively controlling the access of the data flow on the user plane and effectively controlling the access of the data flow on the control plane.

[0272] Based on the implementation scheme of the communication method illustrated in FIG4 above, the following takes the case where the identifier of the first user is MC ID or MC IP, the first user device is non-3GPP device 1, the gateway user device is gateway UE1, the service device is an identity authentication management server and an MC Service Server, the first routing address information is the service device address allowed for routing, and the second routing address information is the data stream address allowed for routing as an example, and the communication method illustrated in FIG4 above is described in detail through the specific example shown in FIG5. It can be understood that in the embodiment of the present application, the action performed by a network element can also be replaced by being performed by a functional component in the network element. In the embodiment of the present application, the functional component may, for example, include at least one of a chip, a chip system, a processor, and a processing unit.

[0273] FIG5 is a flow chart of another communication method provided in an embodiment of the present application. The communication method shown in FIG5 is applicable to the emergency mission service communication system architecture. As shown in FIG5, the specific process of the method may include:

[0274] Step 501: The identity authentication management server provides the gateway UE1 with the data flow information that is allowed to be routed. The gateway UE1 receives and stores the data flow information that is allowed to be routed.

[0275] In a possible implementation, the identity authentication management server may provide gateway UE1 with data flow information that is allowed to be routed (for example, the address information of the identity authentication management server (such as the IP address and port number, or URL, of the identity authentication management server), or characteristic information of the user authentication message (such as the message header name, the message header information, such as the header information carried in the HTTP message, may indicate that the message is used for identity authentication)), so that gateway UE1 may also identify whether the user authentication message is used for identity authentication based on the characteristic information of a certain user authentication message, thereby determining whether the user authentication message needs to be routed to the identity authentication management server. Optionally, the above step 501 may also be that after gateway UE1 completes identity authentication with the identity authentication management server, the identity authentication management server sends the address information of the identity authentication management server that is allowed to be routed or the characteristic information of the user authentication message to gateway UE1. Gateway UE1 receives and saves the address information of the identity authentication management server that is allowed to be routed or the characteristic information of the user authentication message.

[0276] In another possible implementation, after gateway UE1 completes identity authentication with the identity authentication management server, the address information of the identity authentication management server or the characteristic information of the user authentication message that is allowed to be routed may also be sent to gateway UE1 by the configuration management server on the network side. Gateway UE1 receives and stores the address information of the identity authentication management server or the characteristic information of the user authentication message that is allowed to be routed.

[0277] Step 502: Non-3GPP device 1 sends a first IP data packet to gateway UE 1. Gateway UE 1 receives the first IP data packet.

[0278] Before sending the first IP data packet to gateway UE 1, non-3GPP device 1 establishes a non-3GPP transmission connection (such as a Bluetooth connection or a WI-FI connection) with gateway UE 1. The first IP data packet is carried on the non-3GPP transmission connection.

[0279] Exemplarily, the first IP data packet encapsulates an identity authentication request message (or authentication request message). The identity authentication request message is used to request identity authentication of the first user. For example, the identity authentication request message may carry the MC ID or MC IP of the first user.

[0280] Step 503: When the destination address of the first IP data packet is included in the data flow information allowed to be routed, gateway UE1 forwards the first IP data packet to the identity authentication management server. The identity authentication management server receives the first IP data packet.

[0281] In a possible implementation, when gateway UE1 stores routing-allowed data flow information, if gateway UE1 determines that the destination address of the first IP data packet is included in the routing-allowed data flow information, it may forward the first IP data packet to the identity authentication management server.

[0282] In another possible implementation, when gateway UE1 stores characteristic information of a user authentication message, if gateway UE1 determines that the characteristic information of the first IP data packet matches the characteristic information of the user authentication message, it may forward the first IP data packet to the identity authentication management server.

[0283] Furthermore, the gateway UE1 may further parse the application layer message in the first IP data packet, and when it is determined that the message is an identity authentication message or an allowed URL, it may forward the first IP data packet to the identity authentication management server.

[0284] Step 504: The identity authentication management server performs identity authentication on the first user and sends an authentication response message to the non-3GPP device 1. The non-3GPP device 1 receives the authentication response message.

[0285] Exemplarily, the authentication response message may be used to indicate that the first user identity authentication has passed (or succeeded), or may also be used to indicate that the first user identity authentication has not passed (or failed).

[0286] When the identity authentication management server sends the authentication response message to the non-3GPP device 1 , the authentication response message first passes through the gateway UE1 and is forwarded to the non-3GPP device 1 by the gateway UE1 .

[0287] Step 505: After the first user identity authentication is passed, the identity authentication management server sends the service device address that is allowed to be routed to gateway UE1. Gateway UE1 receives the service device address that is allowed to be routed.

[0288] Illustratively, the address of a routable service device (such as the IP address and port number / URL of a service server (particularly, the IP address and port number for a SIP connection), or the address and port number / URL of a SIP core) may be provided to gateway UE1 by an identity authentication management server, or may be provided to gateway UE1 by a configuration management server, or may be provided to gateway UE1 by an MC Service Server (a type of service server). Illustratively, the service server may include, but is not limited to, an MC Service Server or a SIP Core.

[0289] Among them, the information or event of the success of the identity authentication of a specific user can be synchronized between the identity authentication management server and the configuration management server or MC Service Server, that is, the configuration management server or MC Service Server obtains from the identity authentication management server whether the identity authentication of the specific user is completed.

[0290] Optionally, the above step 505 may also be understood as updating the address of the service device allowed to route stored in the gateway UE1.

[0291] Step 506: Non-3GPP device 1 sends a second IP data packet to gateway UE 1. Gateway UE 1 receives the second IP data packet.

[0292] Exemplarily, the second IP data packet encapsulates a service authorization message or a SIP registration message. The service authorization message is used to request service authorization, and the SIP registration message is used to request SIP registration. The second IP data packet is carried on a non-3GPP transport connection.

[0293] Step 507: When the destination address of the second IP data packet is included in the address of the service device allowed to be routed, the gateway UE1 forwards the second IP data packet to the MC Service Server. The MC Service Server receives the second IP data packet.

[0294] In a possible implementation, when the second IP data packet encapsulates a service authorization message, if gateway UE1 determines that the destination address of the second IP data packet is included in the service device address allowed for routing (or a list of service device addresses allowed for routing), the second IP data packet can be forwarded to the MC Service Server.

[0295] Furthermore, the gateway UE1 may further parse the application layer message in the second IP data packet, and when determining that the URL is an allowed URL, may forward the second IP data packet to the MC Service Server.

[0296] When the second IP data packet encapsulates a SIP registration message, if the gateway UE1 determines that the destination address of the second IP data packet is included in the address of the service device allowed to be routed, the second IP data packet may be forwarded to the SIP core.

[0297] Furthermore, the gateway UE1 may further parse the application layer message in the second IP data packet, and when determining that it is an allowed URL, may forward the second IP data packet to the SIP core.

[0298] In another possible implementation, when gateway UE 1 determines that the destination address of the second IP packet is not included in the address of the service device allowed for routing, the second IP packet may be discarded or not processed. Optionally, gateway UE 1 may also send a notification message to non-3GPP device 1. This notification message is used to notify re-authentication or re-authorization.

[0299] Step 508: When the second IP data packet encapsulates a service authorization message, after completing the service authorization, the MC Service Server sends a service authorization response message to the non-3GPP device 1. The non-3GPP device 1 receives the service authorization response message.

[0300] For example, the service authorization response message may carry information indicating that the service authorization has been approved. When the MC Service Server sends the service authorization response message to non-3GPP device 1, the service authorization response message first passes through gateway UE1, which then forwards it to non-3GPP device 1. Alternatively, the service authorization response message may be encapsulated in a data packet for routing.

[0301] Optionally, when the second IP data packet encapsulates a SIP registration message, the SIP core may send a SIP registration response message to non-3GPP device 1 after completing the SIP registration. For example, the SIP registration response message may carry information indicating a successful SIP registration. When the SIP core sends the SIP registration response message to non-3GPP device 1, the SIP registration response message first passes through gateway UE1 and is then forwarded by gateway UE1 to non-3GPP device 1.

[0302] Step 509: The MC Service Server provides the data flow address allowed for routing to the gateway UE1. The gateway UE1 receives the updated data flow address allowed for routing.

[0303] Exemplarily, the data flow address allowed for routing (such as the IP address and port number of the service flow (for example, the IP address and port number of the SIP session, or the IP address and port number of the media plane)) can be provided to the gateway UE1 by the configuration management server, or can also be provided to the gateway UE1 by the MC Service Server (a type of service server, or other service server).

[0304] Optionally, the above step 509 may also be understood as updating the data flow address (or the data flow address list) allowed to be routed stored by the gateway UE1.

[0305] Step 510: Non-3GPP device 1 sends a third IP data packet to gateway UE 1. Gateway UE 1 receives the third IP data packet.

[0306] Exemplarily, the third IP data packet encapsulates a service request (such as a group call request) message, wherein the service request message is used to request a corresponding service or business. The third IP data packet may also be carried on a non-3GPP transport connection.

[0307] Step 511: When the destination address of the third IP data packet is included in the data flow addresses allowed for routing, the gateway UE1 forwards the third IP data packet to the MC Service Server. The MC Service Server receives the third IP data packet.

[0308] Optionally, when gateway UE1 determines that the destination address of the third IP packet is not included in the address of the service device allowed to be routed, the third IP packet may be discarded or not processed. Optionally, gateway UE1 may also send a notification message to non-3GPP device 1. The notification message is used to notify re-authentication or re-authorization.

[0309] Step 512: The MC Service Server sends a service request response message to the non-3GPP device 1. The non-3GPP device 1 receives the service request response message.

[0310] For example, the service request response message may carry the corresponding result for the service request. In the process of the MC Service Server sending the service request response message to the non-3GPP device 1, the service request response message first passes through the gateway UE1 and is forwarded to the non-3GPP device 1 by the gateway UE1.

[0311] Optionally, the service request response message can also be encapsulated in a data packet for routing.

[0312] Step 513: The MC Service Server sends the updated data flow address or service device address allowed for routing to the gateway UE1.

[0313] Optionally, when the second condition is met, the MC Service Server may send the updated data flow address and / or service device address allowed for routing to the gateway UE1.

[0314] Exemplarily, the second condition may be one of the following: the first user has already connected through another gateway UE (for example, if the first user has multiple IP addresses / SIP addresses, it is considered a duplicate connection); the number of connections / data streams / users connected to gateway UE1 exceeds the limit; the first user's identifier has been registered, logged in, or logged off from the MC service server (or other service server); or after a period of time has passed (for example, the time interval from the last data stream address provided to gateway UE1 for routing permission is greater than or equal to a time threshold). Optionally, when the number of connections / data streams / users connected to gateway UE1 exceeds the limit, the first user's request may be rejected or the connection of another user may be preempted.

[0315] For example, when the first user's identifier has been deregistered from the MC service server (or other service server), the first user can send a service de-registration / authorization message to the MC service server (or other service server) through the MC client in the non-3GPP device 1. Optionally, the service de-registration / authorization message can be encapsulated in a data packet for routing.

[0316] It can be understood that the MC service server (or other service server) provides the updated data flow address and / or service device address allowed for routing to the gateway UE1, which can also be understood as revoking / disabling / invalidating the data flow address and / or service device address allowed for routing before.

[0317] In this embodiment of the present application, after the MC service server (or other service server) provides gateway UE1 with the updated permitted data flow address and / or service device address, the user will need to re-initiate the authentication and authorization process the next time they send a specific service. For example, after gateway UE1 refuses to route an IP data packet sent by the MC client in non-3GPP device 1, it can send a re-authentication message or a re-authorization message to the MC client in non-3GPP device 1. The re-authentication message is used to notify the first user that the authentication process needs to be re-initiated, and the re-authorization message is used to notify the first user that the authorization process needs to be re-initiated.

[0318] It can be seen from the above steps 501 to 513 that after the identity authentication management server authenticates a certain user (such as the first user), the identity authentication management server (or the configuration management server) can provide the gateway user device with the service device address that is allowed to be routed, so that the gateway user device can accurately determine whether to route or reject data packets from non-3GPP devices (such as data packets encapsulating service authorization messages or SIP registration messages). In addition, after the service server completes the service authorization or SIP registration for the first user, the data flow address that is allowed to be routed can be provided to the gateway user device, so that the gateway user device can accurately determine whether to route or reject data packets from non-3GPP devices (such as data packets encapsulating service request (e.g., group call request) messages). In this way, the method can achieve effective control of access to data packets from user devices.

[0319] It should be noted that in the description of this application, "at least one" refers to one or more, and "plurality" refers to two or more. "And / or" describes the association relationship of associated objects, indicating that three relationships can exist. For example, A and / or B can represent: the existence of A alone, the existence of A and B at the same time, and the existence of B alone, where A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are in an "or" relationship. "At least one of the following" or similar expressions refers to any combination of these items, including any combination of single or plural items. For example, "at least one of A, B and C" includes A, B, C, AB, AC, BC or ABC. And, unless otherwise specified, the ordinal numbers such as "first", "second", and "third" mentioned in the embodiments of this application are used to distinguish multiple objects and are not used to limit the order, timing, priority or importance of multiple objects. In addition, the terms "including", "comprising", "having" and their variations appearing in this application all mean "including but not limited to" unless otherwise specifically emphasized.

[0320] In addition, it should be noted that each step involved in the above embodiments can be performed by a corresponding device, or by a component such as a chip, processor, or chip system within the device, and the embodiments of the present application do not limit this. The above embodiments are described only as examples of execution by corresponding devices.

[0321] It should be noted that in each of the above embodiments, some steps may be selected for implementation, and the order of the steps in the diagrams may be adjusted for implementation, and this application does not limit this. It should be understood that executing some of the steps in the diagrams, adjusting the order of the steps, or combining them for specific implementation all fall within the scope of protection of this application.

[0322] It is understandable that in order to implement the functions in the above embodiments, the various devices involved in the above embodiments include hardware structures and / or software modules corresponding to the execution of each function. It should be readily apparent to those skilled in the art that, in combination with the units and method steps of the various examples described in the embodiments disclosed in this application, the present application can be implemented in the form of hardware or a combination of hardware and computer software. Whether a function is executed in the form of hardware or computer software driving hardware depends on the specific application scenario and design constraints of the technical solution.

[0323] It should be noted that the "steps" in the embodiments of this application are merely illustrative and serve as a method of expression for a better understanding of the embodiments. They do not constitute a substantive limitation on the implementation of the solutions of this application. For example, the "steps" can also be understood as "features." Furthermore, the steps do not constitute any limitation on the execution order of the solutions of this application. Any changes to the order of steps, or any operations such as step merging or step splitting that do not affect the implementation of the overall solution, resulting in new technical solutions, are also within the scope of this application.

[0324] Based on the same concept, an embodiment of the present application also provides a possible communication device, which is applicable to the communication system architecture shown in Figure 1a or Figure 1b or Figure 1c. Optionally, the communication device can be a communication device (for example, a user device (such as a first user device or a second user device or a third user device, etc.), a gateway user device (such as gateway UE1 or gateway UE2, etc.) or a service device (such as an MC service server or other business server or a configuration management server or an identity authentication management server)) or a device that can support the communication device to implement the functions required by the communication method. In an example, when the communication device is a first user device (or a second user device or a third user device) (such as a UE), the communication device is used to implement the technical solution involved in the first user device (or the second user device or the third user device) in the above embodiment, or the module (such as a chip) of the communication device is used to implement the technical solution involved in the first user device (or the second user device or the third user device) in the above embodiment, and thus the beneficial effects of the first user device (or the second user device or the third user device) in the above embodiment can also be achieved. Exemplarily, when the communication device is a chip provided in a first user device (or a second user device or a third user device), the communication device includes a transceiver and a processor, but does not include a memory. The transceiver exists as an input / output interface, and the input / output interface is used by the chip to implement transceiver functions of the first user device (or the second user device or the third user device). The input / output interface may include an input interface and / or an output interface, the input interface may implement reception by the first user device (or the second user device or the third user device), and the output interface may be used to implement transmission by the first user device (or the second user device or the third user device). The processor is used to read and execute corresponding computer programs or instructions so that the corresponding functions of the first user device (or the second user device or the third user device) are implemented. Optionally, when the chip implements the corresponding functions of the first user device (or the second user device or the third user device) in the above embodiment, the input / output interface may implement the transceiver operations performed by the first user device (or the second user device or the third user device) in the above embodiment; the processor may implement other operations other than the transceiver operations performed by the first user device (or the second user device or the third user device) in the above embodiment. For specific related descriptions, please refer to the related descriptions of the first user equipment (or the second user equipment or the third user equipment) in the above embodiment, which will not be described in detail here.

[0325] In another example, when the communication device is a gateway user equipment (such as gateway UE1 or gateway UE2), the communication device is used to implement the technical solutions involved in the gateway user equipment in the above embodiments, or the module of the communication device (such as a chip) is used to implement the technical solutions involved in the gateway user equipment in the above embodiments, thereby also achieving the beneficial effects of the gateway user equipment in the above embodiments. Exemplarily, when the communication device is a chip set in the gateway user equipment, the communication device includes a transceiver and a processor, but does not include a memory. The transceiver exists as an input and output interface, and the input and output interfaces are used by the chip to implement the transmission and reception of the communication device. The input and output interfaces may include an input interface and / or an output interface. The input interface can implement the reception of the gateway user equipment, and the output interface can be used to implement the transmission of the gateway user equipment. The processor is used to read and execute the corresponding computer program or instructions so that the corresponding functions of the gateway user equipment are implemented. Optionally, when the chip implements the corresponding functions of the gateway user equipment in the above embodiments, the input and output interfaces can implement the transmission and reception operations performed by the gateway user equipment in the above embodiments; and the processor can implement other operations performed by the gateway user equipment in the above embodiments in addition to the transmission and reception operations. For specific related descriptions, please refer to the related descriptions of the gateway user equipment in the above embodiments, which will not be described in detail here.

[0326] In another example, when the communication device is a service device (such as an MC service server or other business server, configuration management server, or identity authentication management server), the communication device is used to implement the technical solutions involved in the service device in the above embodiments, or a module of the communication device (such as a chip) is used to implement the technical solutions involved in the service device in the above embodiments, thereby also achieving the beneficial effects of the service device in the above embodiments. For example, when the communication device is a chip provided in the service device, the communication device includes a transceiver and a processor, but does not include a memory. The transceiver is present as an input / output interface, and the input / output interface is used by the chip to implement transceiver communication of the communication device. The input / output interface may include an input interface and / or an output interface, the input interface can implement reception of the service device, and the output interface can implement transmission of the service device. The processor is used to read and execute the corresponding computer program or instructions to implement the corresponding functions of the service device. Optionally, when the chip implements the corresponding functions of the service device in the above embodiments, the input / output interface can implement the transceiver operations performed by the service device in the above embodiments; the processor can implement other operations performed by the service device in the above embodiments in addition to the transceiver operations. For specific related descriptions, please refer to the relevant description of the service device in the above embodiments and will not be described in detail here.

[0327] 6 , a communication device 600 includes a communication module 601 (or a transceiver module, for sending and receiving data) and a processing module 602. The communication device 600 is used to implement the functions of the first communication device (e.g., user equipment (e.g., first user equipment, second user equipment, or third user equipment)), the second communication device (e.g., gateway user equipment), or the third communication device (e.g., service device) in the method embodiments shown in FIG. 2 to FIG. 3 .

[0328] Optionally, the communication module 601 may include a receiving module and / or a transmitting module. The receiving module may be used by the communication device 600 to receive signals (information or data, etc.); the transmitting module may be used by the communication device 600 to transmit signals (information or data, etc.). The transmitting module may transmit signals (information or data, etc.) under the control of the processing module 602, and the receiving module may receive signals (information or data, etc.) under the control of the processing module 602.

[0329] When the communication device 600 is used to implement the functions of the gateway user equipment in the method embodiments shown in Figures 2 and 3 above: the communication module 601 is configured to receive a first message from a first user equipment. The first message includes the identifier of a first user associated with the first user equipment and is used to request authorization for the first user's connection. The processing module 602 is configured to send a second message to a service device based on the first message. The service device is configured to provide a connection authorization service to the first user, and the second message includes the identifier of the first user and is used to request authorization for the first user's connection.

[0330] When the communication device 600 is used to implement the functions of the service device in the method embodiments shown in Figures 2 and 3 above, the communication module 601 is configured to receive a second message from a gateway user equipment. The second message includes the identifier of a first user associated with the first user equipment and is used to request connection authorization for the first user. The service device is configured to provide a connection authorization service to the first user. The processing module 602 is configured to send a response message to the second message to the gateway user equipment based on the second message. The response message to the second message is used to authorize or deny the connection of the first user.

[0331] When the communication device 600 is used to implement the functions of the first user equipment in the method embodiments shown in Figures 2 and 3 above: the communication module 601 is used to send a first message to the gateway user equipment, or to receive a message from the gateway user equipment. Optionally, the processing module 602 is used to establish a non-3GPP transport connection with the gateway user equipment, or to process other data.

[0332] When the communication device 600 is used to implement the functions of the gateway user equipment in the method embodiments shown in Figures 4 and 5 above: the communication module 601 is configured to receive a first data packet from a first user equipment. The processing module 602 is configured to forward the first data packet to a service device if the destination address of the first data packet is included in the authorized data flow information. The communication module 601 is further configured to receive authorized routing address information. The processing module 602 is further configured to route or reject the data flow from the first user equipment based on the authorized routing address information.

[0333] When the communication device 600 is used to implement the functions of the service device in the method embodiments shown in Figures 4 and 5 above: the communication module 601 is configured to receive a first message from a first user device. The first message includes the identifier of a first user associated with the first user device. The first message is encapsulated in a first data packet and sent to the service device via a gateway user device. The first message is used to request identity authentication of the first user. The processing module 602 is configured to send authorized routing address information to the gateway user device if the first user identity authentication is successful.

[0334] When the communication device 600 is used to implement the functions of the first user equipment in the method embodiments shown in Figures 4 and 5 above: the communication module 601 is used to send a data packet (such as the first data packet, the second data packet, or the third data packet) to the gateway user equipment, or to receive data (such as authorized routing address information) from the gateway user equipment. Optionally, the processing module 602 is used to establish a non-3GPP transport connection with the gateway user equipment, or to process other data.

[0335] Among them, when the communication device 600 is used to implement the functions of the first communication device or the second communication device or the third communication device in the method embodiments shown in Figures 2 to 5, for a more detailed description of the communication module 601 and the processing module 602, please refer to the relevant description of the first communication device or the second communication device or the third communication device in the method embodiments shown in Figures 2 to 5 above, and will not be repeated here.

[0336] It should be understood that the communication module 601 in the embodiment of the present application can be implemented by a transceiver or a transceiver-related circuit component, and the processing module 602 can be implemented by a processor or a processor-related circuit component.

[0337] It should be noted that the division of modules in the embodiments of the present application is illustrative and is merely a logical functional division. In actual implementation, other division methods may be used. Furthermore, the functional units in the various embodiments of the present application may be integrated into a single processing unit, or may exist physically separately, or two or more units may be integrated into a single unit. The aforementioned integrated units may be implemented in the form of hardware or software functional units.

[0338] If the integrated unit is 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 present application is essentially or the part that contributes to the prior art or all or 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 for enabling a computer device (which can be a personal computer, or a server, etc.) or a processor to execute all or part of the steps of the various embodiments 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 (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0339] Based on the same concept, the embodiment of the present application also provides a possible communication device, which is applicable to the communication system architecture shown in Figure 1a or Figure 1b or Figure 1c. Exemplarily, the communication device can be a device (such as a first communication device or a second communication device or a third communication device) required for executing the communication method provided in the embodiment of the present application, or can be a device including a device required for executing the communication method provided in the embodiment of the present application. Optionally, the communication device can also be arranged in a chip in the first communication device (or the second communication device or the third communication device). When the communication device is a chip arranged in the first communication device (or the second communication device or the third communication device), the communication device includes a transceiver and a processor, but does not include a memory. Wherein, the transceiver exists as an input and output interface, and the input and output interface is used for the chip to realize the transceiver of the communication device. The input and output interface may include an input interface and / or an output interface, and the input interface can realize the reception of the communication device, and the output interface can be used to realize the transmission of the communication device. The processor is used to read and execute corresponding computer programs or instructions so that the corresponding functions of the first communication device (or the second communication device or the third communication device) are realized. Optionally, when the chip implements the corresponding functions of the first communication device (or second communication device or third communication device) in the above embodiment, the input and output interface can implement the transceiver operations performed by the first communication device (or second communication device or third communication device) in the above embodiment; the processor can implement other operations other than the transceiver operations performed by the first communication device (or second communication device or third communication device) in the above embodiment. Specific relevant descriptions can be found in the relevant descriptions in the above embodiment and will not be described in detail here. For example, the communication device is a first communication device (such as a user device (e.g., a first user device)) or a second communication device (such as a gateway user device) or a third communication device (such as a service device). When the communication device is used to implement the technical solutions involved in the first communication device in the above embodiment, the beneficial effects of the first communication device in the above method embodiment can also be achieved. When the communication device is used to implement the technical solutions involved in the second communication device in the above embodiment, the beneficial effects of the second communication device in the above method embodiment can also be achieved. When the communication device is used to implement the technical solutions involved in the third communication device in the above embodiment, the beneficial effects of the third communication device in the above method embodiment can also be achieved.

[0340] 7 , the communication device 700 includes: a transceiver 701 and a processor 702. Optionally, the communication device 700 further includes a memory 703. The transceiver 701, the processor 702, and the memory 703 are interconnected. When the communication device 700 is used to implement the technical solution involved in the first communication device provided in the above embodiment, the transceiver 701 can be used to implement the functions of the above communication module 601 when executing the technical solution involved in the first communication device, and the processor 702 is used to implement the functions of the above processing module 602 when executing the technical solution involved in the first communication device. When the communication device 700 is used to implement the technical solution involved in the second communication device provided in the above embodiment, the transceiver 701 can be used to implement the functions of the above communication module 601 when executing the technical solution involved in the second communication device, and the processor 702 is used to implement the functions of the above processing module 602 when executing the technical solution involved in the second communication device. When the communication device 700 is used to implement the technical solution involved in the third communication device provided in the above embodiment, the transceiver 701 can be used to implement the function of the above communication module 601 when executing the technical solution involved in the third communication device, and the processor 702 is used to implement the function of the above processing module 602 when executing the technical solution involved in the third communication device.

[0341] Optionally, transceiver 701, processor 702, and memory 703 are interconnected via bus 704. Bus 704 may be a Peripheral Component Interconnect (PCI) bus or an Extended Industry Standard Architecture (EISA) bus. Buses can be classified as address buses, data buses, control buses, and the like. For ease of illustration, FIG7 shows only one thick line, but this does not imply that there is only one bus or only one type of bus.

[0342] The transceiver 701 is used to receive and send data. For example, when the communication device 700 is an emergency mission service user equipment (or emergency mission service server) as shown in Figure 1a, an MCPTT UE (or MCPTT server) as shown in Figure 1b, or a non-3GPP device (or gateway user equipment) as shown in Figure 1c, the transceiver 701 implements communication with the RAN device as shown in Figure 1a, Figure 1b or Figure 1c, or can also implement communication with other devices (such as servers) outside the communication system architecture shown in Figure 1a, Figure 1b or Figure 1c. In one example, the transceiver can be a transceiver device with integrated data transceiver functions. In another example, the transceiver can also be composed of a transmitter and a receiver, wherein the transmitter is used to send data and the receiver is used to receive data.

[0343] Optionally, the transceiver 701 may include a transmitter and / or a receiver. The transmitter is used to transmit signals, messages, information, or data. The receiver is used to receive signals, messages, information, or data. For example, the transmitter transmits signals, messages, information, or data under the control of the processor 702. The receiver receives signals, messages, information, or data under the control of the processor 702.

[0344] The functions of processor 702 can refer to the description of the corresponding functions involved in the first communication device, the second communication device, or the third communication device in the above embodiments, and will not be repeated here. Processor 702 can be a central processing unit (CPU), a network processor (NP), or a combination of a CPU and an NP, etc. Processor 702 can further include a hardware chip. The hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD), or a combination thereof. The PLD can be a complex programmable logic device (CPLD), a field-programmable gate array (FPGA), a generic array logic (GAL), or any combination thereof. When implementing the above functions, processor 702 can be implemented through hardware, or it can also execute corresponding software implementations through hardware.

[0345] Memory 703 is used to store program instructions, etc. Specifically, program instructions may include program code, which includes computer operating instructions. Memory 703 may include random access memory (RAM) or non-volatile memory (non-volatile memory), such as at least one disk drive. Processor 702 executes the program instructions stored in memory 703 to implement the above functions, thereby implementing the method steps required to be executed by the first communication device, the second communication device, or the third communication device in the above embodiments.

[0346] Based on the same concept, an embodiment of the present application further provides a possible communication system, which includes a first communication device (such as a user equipment (e.g., a first user equipment)), a second communication device (such as a gateway user equipment), and a third communication device (such as a service device). The first communication device can be used to implement the technical solution involved in the first communication device in the above embodiment, the second communication device can be used to implement the technical solution involved in the second communication device in the above embodiment, and the third communication device can be used to implement the technical solution involved in the third communication device in the above embodiment.

[0347] Based on the same concept, an embodiment of the present application further provides a computer program product, which includes a computer program or instructions. When the computer program or instructions are run on a computer, the computer executes the method provided in the above embodiment.

[0348] Based on the same concept, an embodiment of the present application also provides a computer-readable storage medium, which stores a computer program or instruction. When the computer program or instruction is executed by a computer, the computer executes the method provided in the above embodiment.

[0349] The storage medium may be any available medium that can be accessed by a computer. By way of example and not limitation, computer-readable media may include RAM, ROM, EEPROM, CD-ROM or other optical disk storage, magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store desired program code in the form of instructions or data structures and can be accessed by a computer.

[0350] Based on the same concept, an embodiment of the present application further provides a chip, which is coupled to a memory and is used to read a computer program stored in the memory to implement the method provided in the above embodiment.

[0351] Based on the same concept, an embodiment of the present application also provides a chip system, which includes a processor for supporting a computer device to implement the functions involved in the first communication device (such as user equipment (such as first user equipment)), the second communication device (such as gateway user equipment) or the third communication device (such as service equipment) in the above embodiments. In one possible design, the chip system also includes a memory, which is used to store the necessary programs and data for the computer device. The chip system can be composed of chips, or it can include chips and other discrete devices.

[0352] The methods provided in the embodiments of the present application can be implemented in whole or in part by software, hardware, firmware, or any combination thereof. When implemented using software, they can be implemented in whole or in part in the form of a computer program product. The computer program product includes one or more computer instructions. When the computer instructions are loaded and executed on a computer, the process or function described in the embodiments of the present application is generated in whole or in part. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via a wired (e.g., coaxial cable, optical fiber, digital subscriber line (DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) method. The computer-readable storage medium can be any available medium that can be accessed by a computer or a data storage device such as a server or data center that includes one or more available media integrated therein. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a high-density digital video disc (DVD)), or a semiconductor medium (eg, a solid state drive (SSD)).

[0353] The steps of the methods described in the embodiments of the present application can be directly embedded in hardware, software units executed by a processor, or a combination of the two. The software units can be stored in RAM, ROM, EEPROM, registers, hard disks, removable disks, CD-ROMs, or other storage media in any form known in the art. Exemplarily, the storage medium can be connected to the processor so that the processor can read information from the storage medium and write information to the storage medium. Alternatively, the storage medium can also be integrated into the processor. The processor and storage medium can be arranged in an ASIC.

[0354] The present application is described with reference to the flowcharts and / or block diagrams of the methods, devices (systems), and computer program products according to the present application. It should be understood that each flow and / or box in the flow chart and / or block diagram, as well as the combination of the flow chart and / or box in the flow chart and / or block diagram, can be implemented by computer program instructions. These computer program instructions can be provided to a processor of a general-purpose computer, a special-purpose computer, an embedded processor, or other programmable data processing device to produce a machine, so that the instructions executed by the processor of the computer or other programmable data processing device produce a device for implementing the functions specified in one or more flow charts and / or one or more boxes in the block diagram.

[0355] These computer program instructions can also be loaded onto a computer or other programmable data processing device so that a series of operating steps are executed on the computer or other programmable device to produce a computer-implemented process, so that the instructions executed on the computer or other programmable device provide steps for implementing the functions specified in one or more processes in the flowchart and / or one or more boxes in the block diagram.

[0356] Obviously, those skilled in the art may make various changes and modifications to this application without departing from the spirit and scope of this application. Thus, if these modifications and variations of this application fall within the scope of the claims of this application and their equivalents, this application is intended to include these modifications and variations.

Claims

1. A communication method, characterized in that: Applied to a gateway user equipment, the method comprises: receiving a first message from a first user equipment, the first message including an identifier of a first user associated with the first user equipment, the first message being used to request authorization for connection of the first user; According to the first message, a second message is sent to a service device, the service device is used to provide a connection authorization service to the first user, the second message includes an identifier of the first user, and the second message is used to request authorization for connection of the first user.

2. The method according to claim 1, characterized in that The identifier of the first user is a permanent identifier of the first user.

3. The method according to claim 1 or 2, characterized in that The method further comprises: receiving a response message to the second message from the service device, wherein the response message to the second message is used to authorize or deny the connection of the first user; According to the response message to the second message, a response message to the first message is sent to the first user equipment.

4. The method according to claim 3, characterized in that The method further comprises: According to a response message to the second message, a temporary identifier is allocated to the first user, where the temporary identifier is used to identify the first user on the gateway user equipment, and the response message to the first message includes the temporary identifier of the first user.

5. The method according to claim 3, characterized in that The response message to the first message further includes connection information, where the connection information is used to establish a service connection for the first user.

6. The method according to any one of claims 1 to 5, characterized in that: Sending a second message to a service device according to the first message includes: When the first condition is met, the second message is sent to the service device according to the first message.

7. The method according to claim 6, characterized in that The first condition includes at least one of the following: The number of connections of the first user is less than or equal to a first number threshold; The association relationship between the device information of the first user device and the identifier of the first user is included in the authorized association relationship; The device information of the first user device is included in the authorized device information; The distance between the first user equipment and the gateway user equipment is less than or equal to a distance threshold; The gateway user equipment has available resources; The gateway user equipment has no available resources and has a connection that can be preempted.

8. The method according to claim 7, characterized in that The preemptible connection includes a second connection, where the second connection is a connection whose user priority is lower than the user priority of the first user, or the second connection is a connection whose service priority is lower than the service priority corresponding to the first service identifier: The method further comprises: A preemption message is sent to a second user equipment corresponding to the second connection, where the preemption message is used to indicate that resources of the second connection are preempted by a high-priority user or a high-priority service.

9. The method according to any one of claims 1 to 8, characterized in that The first message also includes at least one of the following: user priority, service priority, location information of the first user device, device information of the first user device, user connection preference, data flow information or a first service identifier, wherein the user connection preference is used to indicate priority for preempting or retaining an existing connection, and the data flow information is used to describe the data flow requested to be sent by the first user device.

10. The method according to any one of claims 1 to 8, characterized in that The second message also includes at least one of the following: the identification of the gateway user equipment, user priority, service priority, location information of the first user equipment, equipment information of the first user equipment, user connection preference, data flow information or first service identification, the user connection preference is used to indicate priority to preempt or retain an existing connection, and the data flow information is used to describe the data flow requested to be sent by the first user equipment.

11. The method according to any one of claims 1 to 10, characterized in that: The method further comprises: receiving authorized data flow information from the service device, the authorized data flow information including information of an authorized data flow associated with the identifier of the first user; receiving a first data stream from the first user equipment, where the first data stream includes information of the first data stream; If the information of the first data flow is included in the authorized data flow information, the first data flow is sent.

12. The method according to claim 11, characterized in that The method further comprises: If the information of the first data flow is not included in the authorized data flow information, sending a third message to the first user equipment, The third message is used to indicate that the first data flow is rejected, or is used to indicate that the first data flow requires additional authorization.

13. The method according to any one of claims 1 to 12, characterized in that: The method further comprises: receiving a fourth message from the first user equipment, where the fourth message includes a correspondence between an identifier of the first user and at least one service identifier; The corresponding relationship is sent to the service device.

14. The method according to any one of claims 1 to 13, characterized in that: The method further comprises: A preemption message is received from the service device, where the preemption message is used to indicate that resources of the connection corresponding to the first service identifier are preempted.

15. The method according to any one of claims 1 to 14, characterized in that: The method further comprises: receiving a fifth message from the first user equipment, where the fifth message is used to indicate information about an established or terminated data flow; The information indicating the established or terminated data flow is sent to the service device.

16. A communication method, characterized in that: Applied to a service device, the method comprises: receiving a second message from a gateway user equipment, the second message including an identifier of a first user associated with the first user equipment, the second message being used to request authorization for connection of the first user, the service device being used to provide a connection authorization service to the first user; According to the second message, a response message of the second message is sent to the gateway user equipment, where the response message of the second message is used to authorize or reject the connection of the first user.

17. The method according to claim 16, characterized in that When the authorization condition is met, the response message of the second message is used to authorize the connection of the first user; or When the authorization condition is not met, the response message of the second message is used to reject the connection of the first user.

18. The method according to claim 17, characterized in that The second message also includes at least one of the following: the identification of the gateway user equipment, user priority, service priority, location information of the first user equipment, equipment information of the first user equipment, the user connection preference, data flow information or the first service identification, the user connection preference is used to indicate preemption priority or retention of an existing connection, and the data flow information is used to describe the data flow requested to be sent by the first user equipment.

19. The method according to claim 18, characterized in that The authorization condition includes at least one of the following: The identification of the first user is included in the authorized user identification information; The association relationship between the identifier of the first user and the identifier of the gateway user equipment is included in the authorized association relationship; The association relationship between the identifier of the first user, the device information of the first user equipment and the identifier of the gateway user equipment is included in the authorized association relationship; The data flow information verification is passed; The association relationship between the device information of the first user equipment and the identifier of the gateway user equipment is included in the authorized association relationship; According to the location information and / or user connection preference of the first user equipment, there exists a connection corresponding to the first service identifier accessed by the first user through other gateway user equipment; The gateway user equipment has available resources; The gateway user equipment has no available resources and has a connection that can be preempted.

20. The method of claim 19, wherein: The method further comprises: A preemption message is sent to the other gateway user equipment, where the preemption message is used to indicate that resources of the connection corresponding to the first service identifier are preempted by the first user.

21. The method of claim 20, wherein: The preemptible connection includes a third connection, the third connection is a connection whose user priority is lower than the user priority corresponding to the identifier of the first user and whose service identifier is the connection corresponding to the first service identifier, or the second connection is a connection whose service priority is lower than the service priority corresponding to the first service identifier; The method further comprises: A preemption message is sent to a third user equipment corresponding to the third connection, where the preemption message is used to indicate that resources of the third connection are preempted by a high-priority user or a high-priority service.

22. The method according to any one of claims 16 to 21, characterized in that: The method further comprises: Sending authorized data flow information to the gateway user equipment, the authorized data flow information including information of the authorized data flow associated with the identifier of the first user.

23. The method according to any one of claims 16 to 22, characterized in that: The method further comprises: receiving the fourth message from the gateway user equipment, where the fourth message includes a correspondence between the identifier of the first user and the first service identifier of the first user; The number of connections of the first user is acquired according to the first service identifier of the first user.

24. The method according to any one of claims 16 to 23, characterized in that: The method further comprises: A fifth message is received from the gateway user equipment, where the fifth message is used to indicate information of an established or terminated data flow.

25. A communication method, characterized in that: Applied to a gateway user equipment, the method comprises: receiving a first data packet from a first user equipment; If the destination address of the first data packet is included in the authorized data flow information, forwarding the first data packet to the service device; Get the authorized routing address information; The data flow from the first user equipment is routed or rejected according to the authorized routing address information.

26. The method of claim 25, wherein: The authorized routing address information includes: The communication address of the service device, or First routing address information and second routing address information; the first routing address information indicates the authorized service communication address of the service device and / or the control plane communication address of the service device; the second routing address information is used to indicate the user plane communication address of the service device.

27. The method according to claim 25 or 26, characterized in that The authorized routing address information includes the first routing address information and the second routing address information; Obtain authorized routing address information, including: receiving the first routing address information; receiving a second data packet from the user equipment, where the destination address of the second data packet is the authorization service communication address or the control plane communication address; If the destination address of the second data packet is included in the first routing address information, forwarding the second data packet to a service device corresponding to the destination address; The second routing address information is received.

28. The method of claim 27, wherein: The method further comprises: receiving third routing address information from the service device; The authorized routing address information stored in the gateway user equipment is updated according to the third routing address information.

29. The method according to any one of claims 25 to 28, characterized in that The method further comprises: receiving a third data packet from the first user equipment; If the destination address of the third data packet is not included in the authorized routing address information, a third message is sent to the first user equipment, where the third message is used to indicate that routing of the third data packet is rejected.

30. The method according to any one of claims 25 to 29, characterized in that Before receiving the first message from the first user equipment, the method further includes: The gateway user equipment establishes a non-3GPP transmission connection with the first user equipment.

31. A communication method, characterized in that: Applied to a service device, the method comprises: receiving a first message from a first user equipment, the first message including an identifier of a first user associated with the first user equipment, the first message being encapsulated in a first data packet and sent to the service device via a gateway user equipment, the first message being used to request identity authentication for the first user; If the first user identity authentication is passed, the authorized routing address information is sent to the gateway user equipment.

32. The method of claim 31, wherein: The authorized routing address information includes: The communication address of the service device, or First routing address information and second routing address information; the first routing address information indicates the authorized service communication address of the service device and / or the control plane communication address of the service device; the second routing address information is used to indicate the user plane communication address of the service device.

33. The method according to claim 31 or 32, characterized in that The authorized routing address information includes first routing address information and second routing address information; Sending the authorized routing address information to the gateway device includes: If the first user identity authentication is passed, sending the first routing address information to the gateway user equipment; Receive a second message from the gateway user equipment, the second message being encapsulated in a second data packet and sent via the gateway user equipment The second message is sent to the service device, where the second message is used to request service authorization or service registration for the first user; If the service authorization or the service registration is completed, the second routing address information is sent to the gateway user equipment.

34. The method of claim 33, wherein: The method further comprises: If the first user has at least one connection, or the number of connections, the number of users, or the number of data streams served by the gateway user equipment is greater than the second quantity threshold, or the identifier of the first user has been de-registered, logged in, or logged out from the service device, or the set time period has expired, then the third routing address information is sent to the gateway user equipment.

35. A communication device, characterized in that: Comprising a module or unit for executing the method as described in any one of claims 1 to 15, or comprising a module or unit for executing the method as described in any one of claims 16 to 24, or comprising a module or unit for executing the method as described in any one of claims 25 to 30, or comprising a module or unit for executing the method as described in any one of claims 31 to 34.

36. A communication device, characterized in that: include: transceiver, used to receive and send data; Memory for storing computer program instructions and data; A processor, configured to execute and call computer program instructions and data in the memory so that the communication device performs the method as described in any one of claims 1-15, or the method as described in any one of claims 16-24, or the method as described in any one of claims 25-30, or the method as described in any one of claims 31-34.

37. A communication system, characterized in that: The method comprises a gateway user equipment for executing the method as described in any one of claims 1-15 or any one of claims 25-30, a service equipment for executing the method as described in any one of claims 16-24 or any one of claims 31-34, and a first user equipment, a second user equipment or a third user equipment.

38. A computer-readable storage medium, characterized in that: The computer-readable storage medium stores a computer program or instructions, which, when executed by a computer, causes the computer to execute the method as described in any one of claims 1 to 15, or the method as described in any one of claims 16 to 24, or the method as described in any one of claims 25 to 30, or the method as described in any one of claims 31 to 34.

39. A computer program product, characterized in that The computer program product comprises a computer program or instructions, which, when executed on a computer, causes the computer to execute the method according to any one of claims 1 to 15, or the method according to any one of claims 16 to 24, or the method according to any one of claims 25 to 30, or the method according to any one of claims 31 to 34.

40. A chip, characterized in that: The chip includes a processor, which is used to execute program instructions in the memory to perform the method as described in any one of claims 1-15, or the method as described in any one of claims 16-24, or the method as described in any one of claims 25-30, or the method as described in any one of claims 31-34.

Images