Communication method and device

Abstract

The invention provides a communication method and device. The method comprises the steps that gateway user equipment receives a first message from first user equipment, the first message comprises an identifier of a first user associated with the first user equipment, the first message is used for requesting to authorize connection of the first user, and according to the first message, a second message is sent to service equipment, the service equipment is used for providing a connection authorization service for the first user, the second message comprises the identifier of the first user, and the second message is used for requesting to authorize the connection of the first user. The identifier of the first user is carried in the first request message used for requesting to authorize the connection of the first user, so that gateway user equipment and service equipment can accurately identify whether a plurality of connection requests are from the same user or not, and whether the same user has at least one connection or not can be accurately judged; therefore, the connection of the same user can be effectively controlled, and authorization of a single user can be carried out on the connection.

Description

Technical Field

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

[0002] 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 cluster communications in public safety scenarios. Exemplarily, MC services may include Mission Critical Push To Talk (MCPTT), Mission Critical Data (MCData), and Mission Critical Video (MCVideo).

[0003] Among them, 3GPP SA6 defines the scenario of using Gateway User Equipment (Gateway UE or GW UE) in MC services. When MC users use non-3GPP devices (Non-3GPP devices, N3GPP devices), the non-3GPP devices 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 be connected to the server on the network side through the Gateway UE. Exemplarily, an MC client (Client), such as MCPTT client, CSC client, etc., can be installed on the non-3GPP device.

[0004] At present, non-3GPP devices send connection authorization requests to Gateway UEs, and the connection authorization requests carry Gateway MC service IDs. Gateway MC service IDs are temporary recyclable IDs or authentication IDs that can be shared by multiple users. Therefore, Gateway UEs cannot determine whether multiple connection authorization requests correspond to the same user (i.e., MC service user) based on Gateway MC service IDs. At the same time, the server on the network side cannot distinguish whether connection authorization requests from multiple Gateway UEs correspond to the same user based on Gateway MC service IDs, and thus cannot authorize the user's connection, and cannot determine whether the same user already has a connection for a certain MC service. Summary of the invention

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

[0006] In the 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 the method, after receiving the first message from the first user device, the gateway user device can send a second message to the service device according to the first message, wherein the first message may include the 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, the service device is used to provide the first user with a connection authorization service, and the second message may include the identifier of the first user, and the second message is used to request authorization for the connection of the first user.

[0007] In this method, by carrying the identifier of the user in the request message for requesting the authorized 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, so that the connection of the same user can be effectively controlled, and the connection access of the user connecting to the service device through the gateway user device can be effectively controlled, so that the connection can be authorized for a single user, and the problem of the same user occupying too many resources and causing resource waste due to accessing the service device through multiple gateway user devices can be effectively avoided. It should be understood that the identifier of the user carried in the request message can also help the gateway user device accurately identify whether the request message for requesting authorized connection from the same user device is from the same user.

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

[0009] 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 are 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.

[0010] In one possible design, the method also includes: the gateway user equipment receives a response message to the second message from the service equipment, 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 equipment can send a response message to the first message to the first user equipment based on the response message to the second message.

[0011] In the above design, by notifying the first user of the authorization result (such as authorization success or authorization failure) of the connection requested by the first user in a timely manner, it is possible to avoid the first user from blindly initiating a service request process by notifying the first user of the result that the connection requested for authorization is rejected, so that the first user can send a connection request again after a period of time, thereby reducing the energy consumption (such as resource consumption, power consumption) and network signaling consumption caused by the first user device blindly and continuously initiating connection requests.

[0012] In one possible design, the method also includes: the gateway user equipment can assign a temporary identifier to the first user based on a response message to the second message, wherein 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.

[0013] 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.

[0014] In one possible design, 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.

[0015] 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.

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

[0017] In the above design, by judging whether the first condition is met, it is decided 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 by the first user for authorization can be further ensured.

[0018] 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.

[0019] In the above design, by judging 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.

[0020] In one possible design, the connection that can be preempted includes a second connection, 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, 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.

[0021] In the above design, when the available resources on the gateway user device are insufficient, by selectively preempting the connection resources of a certain service or a certain user according to the service priority or the user priority, it is ensured that the connection authorization request message of the first user can be forwarded to the service device, and it can be ensured that the gateway user device has available resources for supporting the connection of the first user. In addition, the gateway user device can send a preemption message to the corresponding user to promptly inform the user of the specific reason for the preemption, and can inform the corresponding user of which service or data flow connection is preempted.

[0022] 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 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.

[0023] 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.

[0024] In one possible design, the second message also includes at least one of the following: an identifier of a gateway user device, a user priority, a service priority, location information of a first user device, device information of the first user device, a 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.

[0025] 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.

[0026] In one possible design, the method also includes: the gateway user equipment receives authorized data flow information from the service equipment, 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 equipment, if it is determined that the information of the first data flow is included in the authorized data flow information, the gateway user equipment sends the first data flow, wherein the first data flow includes the information of the first data flow.

[0027] In the above design, by acquiring the information of the authorized data flow associated with the identification of the first user 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.

[0028] 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.

[0029] 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.

[0030] In one possible design, the method also 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.

[0031] 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.

[0032] 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.

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

[0034] 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.

[0035] 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.

[0036] In 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 of the second message to the gateway user device according to the second message, wherein the second message may include an identifier of a 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 of the second message is used to authorize or reject the connection of the first user.

[0037] 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.

[0038] In one possible design, the second message also includes at least one of the following: an identifier of a gateway user device, a user priority, a service priority, location information of a first user device, device information of the first user device, a user connection preference, data flow information, or a first service identifier, wherein the user connection preference is used to indicate whether to preempt an existing connection 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.

[0039] 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; according to the location information of the first user device and / or the user connection preference, 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.

[0040] 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.

[0041] 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 resources of the connection corresponding to the first service identifier are preempted by the first user.

[0042] In one possible design, the connection that can be preempted 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 a 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 a 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.

[0043] 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.

[0044] In one possible design, the method also includes: the service device receives a fourth message from the gateway user device, after which 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.

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

[0046] For the technical effects that can be achieved in the second aspect, please refer to the technical effects that can be achieved in the first aspect mentioned above, and no further details will be given here.

[0047] 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, the first data packet can be forwarded 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.

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

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

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

[0051] In the above design, through the above address information included in the above authorized routing address information, it can be accurately determined whether a data packet is decided to be routed or rejected.

[0052] 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.

[0053] 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 decided to be routed or rejected.

[0054] 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.

[0055] 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 the 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 timely update the locally stored first routing address information and / or the second routing address information according to the third routing address information. It can be understood that updating the locally stored first routing address information and / or the second routing address information can refer to invalidating or invalidating or revoking the locally stored first routing address information and / or the second routing address information.

[0056] 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.

[0057] In the above design, when the destination address of the data packet from the 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 is rejected for routing, the first user device can re-initiate the registration authentication process or service authorization process.

[0058] 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 transmission connection with the first user equipment.

[0059] In the above design, the network access method 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.

[0060] 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 may 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 may 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 a first user device, and then, 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.

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

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

[0063] 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 passes, 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.

[0064] 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.

[0065] 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 has expired, the service device can send third routing address information to the gateway user device.

[0066] 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. Afterwards, the service device can provide the third routing address information to the gateway user device so that the gateway user device can timely configure (or update) the first routing address information and / or the second routing address information stored locally, so that the gateway user device can use the updated first routing address information and / or the second routing address information to determine whether a certain data stream (or data packet) from the user device should actually be routed.

[0067] 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 by the communication method. Exemplarily, the first communication device may be a user device (such as a first user device or a second user device), the second communication device may be a gateway user device, 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 set 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. Among them, the transceiver exists as 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 sending 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.

[0068] In one example, when the communication device is used to implement the function of the gateway user equipment in the method embodiment shown in the first aspect or the second aspect above, the beneficial effects can be referred to the description of the gateway user equipment in the first aspect or the second aspect, which will not be repeated here. The communication device has the function of implementing the behavior of the gateway user equipment in the method embodiment shown in the first aspect or the second aspect above. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a communication module (or a communication unit, a transceiver module or a transceiver unit, used to send and receive data) and a processing module (or a processing unit). The communication module is used 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 used to request authorization for the connection of the first user. The processing module is used to send a second message to a service device according to the first message. The service device is used to provide a connection authorization service to the first user, and the second message includes an identifier of the first user, and the second message is used to request authorization for the connection of the first user. 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.

[0069] In another example, when the communication device is used to implement the function of the service device in the method embodiment shown in the first aspect or the second aspect, the beneficial effects can refer to the description of the service device in the first aspect or the second aspect, which will not be repeated here. The communication device has the function of implementing the behavior of the service device in the method embodiment shown in the first aspect or the second aspect. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a communication module, which is used to receive a second message from a gateway user device. Among them, the second message includes an identifier of a first user associated with the first user device, the second 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. A processing module is used to send a response message of the second message to the gateway user device according to the second message, and the response message of the second message is used to authorize or reject the connection of the first user. These modules can perform the corresponding functions of the service device in the method embodiment shown in the first aspect or the second aspect, specifically refer to the detailed description of the corresponding functions of the service device in the method example, which will not be repeated here.

[0070] In another example, when the communication device is used to implement the function of the gateway user equipment in the method embodiment shown in the third aspect or the fourth aspect above, the beneficial effects can refer to the description of the gateway user equipment in the third aspect or the fourth aspect, which will not be repeated here. The communication device has the function of implementing the behavior of the gateway user equipment in the method embodiment shown in the third aspect or the fourth aspect above. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a communication module for receiving a first data packet from a first user device. 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 the authorized data flow information. The communication module is also used to receive the authorized routing address information. The processing module is also used to route or reject the data flow from the first user device according to the authorized routing address information. These modules can perform the corresponding functions of the gateway user equipment in the method embodiment shown in the third aspect or the fourth aspect above, and specifically refer to the detailed description of the corresponding functions of the gateway user equipment in the method example, which will not be repeated here.

[0071] In another example, when the communication device is used to implement the function of the service device in the method embodiment shown in the third aspect or the fourth aspect, the beneficial effect can refer to the description of the service device in the third aspect or the fourth aspect, which will not be repeated here. The communication device has the function of implementing the behavior of the service device in the method embodiment shown in the third aspect or the fourth aspect. The function can be implemented by hardware, or it can be implemented by hardware executing corresponding software. The hardware or software includes one or more modules corresponding to the above functions. In one possible design, the communication device includes: a communication module, which is used to receive a first message from a first user device. Among them, 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 used to send authorized routing address information to the gateway user device if the first user identity authentication passes. These modules can perform the corresponding functions of the service device in the method embodiment shown in the third aspect or the fourth aspect, specifically refer to the detailed description of the corresponding functions of the service device in the method example, which will not be repeated here.

[0072] 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 for executing the communication method provided in the present application, or may be a device including a communication device required for executing the communication method provided in the present application, or may be a device having the functions required to implement the communication method. Among them, the communication device may include a transceiver and a processor. Optionally, the communication device may also include a memory. Among them, 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 above, any possible design method of the second aspect above, any possible design method of the third aspect above, or any possible design method of the fourth aspect above.

[0073] 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 aspect, the second aspect, the third aspect, or the fourth aspect. The relevant functional implementation of the first communication device, the second communication device, or the third communication device can refer to the relevant description mentioned in the first aspect, the second aspect, the third aspect, or the fourth aspect, which will not be repeated here.

[0074] 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.

[0075] 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 a 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.

[0076] 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 method in the design of the first aspect or any possible method in the design of the second aspect or any possible method in the design of the third aspect or any possible method in the design of the fourth aspect.

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

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

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

[0080] Figure 1a A possible communication system architecture diagram provided by an embodiment of the present application is exemplarily shown;

[0081] Figure 1b A schematic diagram of a communication system architecture of MCPTT provided in an embodiment of the present application is exemplarily shown;

[0082] Figure 1c Another possible communication system architecture diagram provided by an embodiment of the present application is exemplarily shown;

[0083] Figure 2 A schematic diagram exemplarily illustrates a flow chart of a communication method provided in an embodiment of the present application;

[0084] Figure 3 A schematic diagram exemplarily illustrates a flow chart of another communication method provided in an embodiment of the present application;

[0085] Figure 4 A flowchart showing another communication method provided by an embodiment of the present application is exemplified;

[0086] Figure 5 A schematic diagram exemplarily illustrates a flow chart of another communication method provided in an embodiment of the present application;

[0087] Figure 6 A schematic diagram showing a possible structure of a communication device provided in an embodiment of the present application is exemplified;

[0088] Figure 7 A schematic diagram of the structure of another possible communication device provided in an embodiment of the present application is exemplified. DETAILED DESCRIPTION

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

[0090] The following is an introduction to possible communication system architectures applicable to the communication method provided in this application. It should be noted that these introductions are intended to facilitate understanding by those skilled in the art and do not constitute a limitation on the scope of protection claimed by this application.

[0091] Figure 1a The following is a schematic diagram of a possible communication system architecture applicable to the embodiments of the present application. Figure 1a As shown, the communication system architecture includes a Mission Critical Service Server (MCService Server / MC server), a Common Service Core (CSC) and a MC Service User Equipment (MC Service UE).

[0092] Exemplarily, the emergency mission service server may include but is not limited to a MCPTT server (server), a MCData server or a MCVideo server, etc. The general service core may include a CSC server (server), for example, the CSC server may include but is not limited to a group management server (Group management server), a configuration management server (Configuration management server), an identity management server (identity management server), a key management server (Key management server) or a location management server (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 (Mission Critical Service client, MC Service client) or a general service core (CSC) client (client). For example, the general service core client may include but is not limited to a group management client (Group management client), a configuration management client (Configuration management client), an identity management client (identity management client), a key management client (Key management client) or a location management client (Location management client), etc. For example, the emergency mission service client may include but is not limited to a MCPTT client, a MCData client or a MCVideo client, etc.

[0093] The following is the above Figure 1a The functions of some network elements included in the communication system architecture shown are briefly introduced:

[0094] The emergency mission service server is used to provide corresponding business services to users, such as call control, media control, business 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 MCData services to users; and the MCVideo server is used to provide MCVideo services to users. In this application, the emergency mission service server can also provide services for connection authorization for users using non-3GPP devices.

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

[0096] 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 group 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, and configuration files (such as authorization or cancellation). In another example, when the general 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 of providing connection authorization for users using non-3GPP devices can also be a server module in the general service core.

[0097] 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.

[0098] For example, if Figure 1a As shown, the group management service client can communicate with the group management server through the CSC-2 interface (referred to as CSC-2). The configuration management client can communicate with the configuration management server through the CSC-4 interface (referred to as CSC-4). The identity authentication management client can communicate with the identity authentication management server through the CSC-1 interface (referred to as CSC-1). The key management client can communicate with the key management server through the CSC-8 interface (referred to as CSC-8). The location management client can communicate with the location management server through the CSC-14 interface (referred to as CSC-14). The location management server can communicate with the configuration management server through the CSC-24 interface (referred to as CSC-24). The key management server can communicate with the group management server through the CSC-10 interface (referred to as CSC-10). The location management server can communicate with the emergency task service server through the CSC-15 interface (referred to as CSC-15). The key management server can communicate with the emergency task service server through the CSC-9 interface (referred to as CSC-9). The configuration management server can communicate with the emergency task service server through the CSC-5 interface (referred to as CSC-5). The group management server can communicate with the emergency task service server through the CSC-3 interface (referred to as CSC-3).

[0099] It should be noted that Figure 1aThe names of the network elements and the interfaces between the network elements are only used as an example. In the specific implementation process, the names of the network elements and the interfaces between the network elements may be other names, and the embodiments of the present application do not limit this. In the embodiments of the present application, the Evolved Packet System (EPS) can also be replaced by other mobile communication networks (such as the fifth-generation communication system (5GS)).

[0100] For example, the following takes the MC service as MCPTT as an example to introduce the communication system architecture of MCPTT. Figure 1b As shown, the communication system architecture of MCPTT includes an MCPTT server, an MCPTT UE, an MCPTT user database, an interworking function to legacy system module and other MCPTT servers.

[0101] 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.

[0102] The MCPTT UE is installed with a client for assisting users to access the MCPTT server, namely the MCPTT client. For example, the functional modules of the MCPTT client may include but are not limited to multimedia functional modules (Mediamixer) or media control participants (Transmission control participant / Floor participant). Among them, the Media mixer is a peer entity corresponding to the Media distribution function on the user side, which 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, namely the media transmission control entity on the media plane, which is responsible for the transmission control of media uplink and / or downlink. Exemplarily, in the MCPTT system, the media control participant can be a Floor control participant.

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

[0104] The function module for interconnection and interworking with the old system is used for interconnection and service connection with other heterogeneous systems / access systems, such as P25 and Terrestrial Trunked Radio TETRA.

[0105] For example, if Figure 1b As shown, 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 old system interconnection function module 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, Figure 1b The names of the modules and the interfaces between the modules are only used as examples. In the 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.

[0106] Figure 1c Another possible communication system architecture diagram applicable to the embodiment of the present application is exemplarily shown. Figure 1c As shown, the communication system architecture includes non-3GPP equipment, gateway user equipment (Gateway UE, or can be called MC GatewayUE), emergency mission service server, general service core, session initiation protocol core (Session initiation protocol, SIP Core) and hypertext transfer protocol (HTTP, HyperText Transfer Protocol) proxy module.

[0107] For example, a gateway client (such as MC gateway client), an emergency task client (MC client), an HTTP client or a signaling user agent (Signalling useragent) module, etc. may be installed on a non-3GPP device but is not limited thereto. Exemplarily, the emergency task client may represent an emergency task service client or a CSC client, etc. 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, etc. The gateway user equipment function (such as an MC gateway UE function) module may be arranged inside the emergency task service server, or the gateway user equipment function module may also be arranged in a service device (such as a certain MC server) independent of the emergency task service server.

[0108] Optional, the functions of the emergency task service server and the general service core can be found in the above Figure 1a The description of the communication system architecture shown is not repeated here.

[0109] The following is the above Figure 1c The functions of some network elements included in the communication system architecture shown are briefly introduced:

[0110] In the MC service scenario, MC users need to use non-3GPP devices to implement the corresponding service. For example, the network access method of non-3GPP devices is non-3GPP access, such as access through Bluetooth or wireless fidelity (Wi-Fi) and other networks.

[0111] The gateway client is introduced in the terminal for connection authentication of non-3GPP devices using 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.

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

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

[0114] The gateway user equipment function module is a function module in the emergency mission service server or in other service equipment, 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.

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

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

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

[0118] For example, if Figure 1cAs shown, the gateway client can communicate with the gateway user equipment server through the GW-local interface (GW-local for short). The gateway user equipment server communicates with the gateway user equipment functional module through the GW-Core interface (GW-Core for short). The emergency task client can communicate with the gateway user equipment through the MCX-n interface (MCX-n for short), and the gateway user equipment also communicates with the emergency task service server through the MCX-n interface. The emergency task client can also communicate with the emergency task service server through the MCX-n interface. The CSC client can communicate with the CSC server in the general service core through the CSC-n interface (CSC-n for short). The emergency task client can communicate with the gateway user equipment through the CSC-n interface, and the gateway user equipment also communicates with the CSC server in the general service core through the CSC-n interface. The signaling user agent module in the non-3GPP device can communicate with the gateway user equipment through the SIP-1 interface (SIP-1 for short), and the gateway user equipment also communicates with the session initiation protocol core through 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 can also communicate with the hypertext transfer protocol agent module through the HTTP-1 interface. The HTTP client in the gateway user equipment can communicate with the hypertext transfer protocol agent module through the HTTP-1 interface. It should be noted that Figure 1c The names of the modules and the interfaces between the modules are only used as examples. In the 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.

[0119] It is understandable that the above 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 network element or function can be implemented by one device, or by multiple devices, or a functional module in one device, which is not specifically limited in the embodiments of the present application.

[0120] Optionally, the communication method provided in the embodiment of the present application can be applied to the architecture of the 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 to more clearly illustrate 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.

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

[0122] Figure 2 The following is a flow chart showing a communication method provided by an embodiment of the present application. Figure 1a , Figure 1b or Figure 1c The communication system architecture shown in the figure. The method process 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 device can be as follows Figure 1a The emergency task service user equipment shown, or it may also be as shown Figure 1b The MCPTT UE shown in FIG. Figure 1c The non-3GPP device shown; the gateway user equipment may be such as Figure 1c The gateway user equipment shown; the service equipment can be such as Figure 1a The emergency task service server shown, or it can also be Figure 1b The MCPTT server shown in FIG. Figure 1c The emergency task service server or the general service core or the session initiation protocol core or the gateway user equipment function module or the hypertext transfer protocol proxy module shown. It should be understood that in the example Figure 1aThe communication method provided in the embodiment of the present application is also applicable when a gateway user device is introduced between the emergency task service user device and the emergency task service server, or in the case of Figure 1b The communication method provided in the embodiment of the present application is also applicable when a gateway user device is introduced between the MCPTT UE and the MCPTT server. 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 device, the second communication device as the gateway user device, 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. Figure 2 As shown, the method includes:

[0123] Step 201: A first user equipment sends a first message to a gateway user equipment. The gateway user equipment receives the first message.

[0124] 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 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.

[0125] Exemplarily, 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. It is understandable that the connection of the first user may refer to a connection between the user and a gateway device, and the connection of the first user may also refer to a connection for data transmission between the user and the MC Service Server. The connection of the first user may also refer to an association between the first user and a 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.).

[0126] For example, the first message may be used to request that an authorized user can 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 an authorized user using a non-3GPP connection with the gateway user device to transmit data). At this time, the first user device may 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 can 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 between 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.

[0127] 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 an identity presented by a user to an 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).

[0128] 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 links and is 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 MC service type) or a security credential, etc. Exemplarily, the first service identifier may be used to indicate a service (such as one or more of MCPTT, MCVideo or MCdata), or may also be used as a temporary identifier for a gateway user device to distinguish different users, such as a gateway user device assigning different temporary identifiers to different users. Among them, the user connection preference is used to indicate priority to preempt or to retain 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 may be used to verify whether the first user is legitimate.

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

[0130] 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.

[0131] Exemplarily, the second message may include an identity management message, and the identity management message may be used as 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.

[0132] 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.

[0133] For example, the second message also 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 preference, 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., SN number, MAC address), or a user identifier of a logged-in user on the gateway device. At this time, the user may be a special user, such as an administrator user.

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

[0135] 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 number 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 are connections that can be preempted (such as connections of users whose user priority is lower than the user priority of the first user or connections of services whose service priority is lower than the service priority corresponding to the first service identifier).

[0136] 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.

[0137] 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).

[0138] 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 connection authorization request of the first user is rejected (or failed or failed).

[0139] 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.

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

[0141] For example, when the authorization condition is met, the service device may carry information indicating that the authorization of the connection of the first user is passed (or the authorization is successful) in the response message of the second message. When the authorization condition is not met, the service device may carry information indicating that the authorization of the connection of the first user is not passed (or the authorization fails or the authorization is rejected) in the response message of the second message.

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

[0143] 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);

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

[0145] 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 (or the authorized association relationship list, such as the association relationship between the allowed MCID (or MC IP) pre-configured on the service device, the device information of the non-3GPP device and the gateway user equipment);

[0146] The data flow information verification passed;

[0147] 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 (or the authorized association relationship list, such as which gateway user equipments are pre-configured on the service device to allow any user equipment (such as non-3GPP equipment) to connect, or which non-3GPP equipments are pre-configured to allow any gateway user equipment to connect);

[0148] 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;

[0149] Or there are no available resources in the gateway user equipment, and there are connections that can be preempted (such as 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).

[0150] In a possible implementation, when the service device determines that there is a connection corresponding to the first service identifier accessed by the first user through other gateway user devices, the service device may send a preemption message to other gateway user devices or gateway devices (i.e., the gateway device that sends the second message). The preemption message is used to indicate that the connection corresponding to the first service identifier is preempted by the first user. Optionally, other gateway user devices or gateway devices 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 prior 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 prior connection, a corresponding preemption response message may be sent to the service device. The preemption response message may carry information indicating consent to preempt the prior connection. If the user device refuses to preempt the prior connection, a corresponding preemption response message may be sent to the service device. The preemption response message may carry information indicating refusal to preempt the prior 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.

[0151] For example, when the first user sends a message for requesting authorization of the second user's connection through a certain gateway user device (such as the 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 the 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.

[0152] In another possible implementation, when the service device determines that there are no available resources for the gateway user equipment and there is a connection that can be preempted, the service device can 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 are preempted by a high-priority user or a high-priority service. For example, taking the preemptible connection including the third connection as an example, the third connection can refer to 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 can also refer to a connection whose service priority is lower than the service priority corresponding to the first service identifier.

[0153] When the third connection refers to 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, 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 a 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.

[0154] 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 (such as the first user device or the third user device). For example, when the service device sends a preemption message to the first user device, in 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.

[0155] 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 route or allowed) data flow information (such as server IP triplet, IP quadruple (MC IP (used to indicate the permanent IP used by MC user or the IP used by 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. Among them, the authorized data flow information can include information of one or more authorized data flows associated with the identifier of the first user. Optionally, the service device can 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 rejection routing message (such as carrying information for indicating rejection routing) to the first user equipment. After receiving the rejection routing message, the first user equipment may initiate the connection authorization process again to request authorization for the rejected data flow information.

[0156] 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.

[0157] Optionally, after the first user device subsequently interacts with the service device with data streams (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, indicating the preemption of the connection resources of the first user. The gateway user device of the first user device 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.

[0158] Optionally, after the service device executes step 203, the gateway user device may also execute step 204. By executing step 204, the first user device may be notified in a timely manner of whether the service device has authorized the connection of the first user. This may facilitate 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 the 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, by executing step 204, 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 may be avoided.

[0159] 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.

[0160] 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 can be used to indicate authorization (or permission) of the first user's connection.

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

[0162] Optionally, the gateway user equipment may also allocate a temporary identifier (such as GM MC service ID) to the first user based on the response message of the second message, and 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.

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

[0164] 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.

[0165] Mode 1: When the response message of 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 business processes to the service device.

[0166] Optionally, in the process where 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.

[0167] Mode 2: When the response message to the first message is used to indicate rejection of the connection of the first user, the first user equipment does not need to initiate a corresponding service process, or may initiate a process for requesting authorization of the connection of the first user again after a period of time.

[0168] 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 MC ID or MCIP of the first user) 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 identifier of the first user) and the first service identifier.

[0169] 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 an established or terminated data flow can be used by a service device (or, such as a gateway UE function module installed in a service device) to determine resource usage on the gateway user device.

[0170] It can be seen from the above steps 201 to 204 that by carrying the identifier of the user in the request message for requesting the 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, so that the connection of the same user can be effectively controlled, and the connection access of the user who connects to the service device through the gateway user device can be effectively controlled, so that the connection can be authorized for a single user, and the problem of the same user occupying too many resources and causing resource waste due to access to the service device through multiple gateway user devices can be effectively avoided. It should be understood that the identifier of the user 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. In addition, when the available resources on the gateway user device are insufficient, the gateway user device selectively seizes the connection resources of a certain service or the connection resources of a certain user according to the service priority or the user priority, so as to ensure that the connection authorization request message of the first user can be forwarded to the service device, and it can ensure that the gateway user device has available resources for supporting the connection of the first user.

[0171] Based on the above Figure 2 In the implementation scheme of the communication method shown in the figure, the first user's identifier is MC ID or MCIP, the first user equipment is non-3GPP equipment 1, the second user equipment is non-3GPP equipment 2, the gateway user equipment is gatewayUE1, the other gateway user equipment is gatewayUE2, and the service device is MC Service Server as an example. Figure 3 The specific example shown above Figure 2 It is understood that in the embodiment of the present application, the action performed by a network element can also be replaced by the action performed by the functional component in the network element. In the embodiment of the present application, the functional component may include at least one of a chip, a chip system, a processor, and a processing unit.

[0172] Figure 3 A flow chart of another communication method provided in an embodiment of the present application. Figure 3 The communication method shown is suitable for emergency mission service communication system architecture. Figure 3 As shown, the specific process of the method may include:

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

[0174] In one example, when the first user's identifier is an MC ID, the first connection authorization request message carries the MC ID of the first user (such as user1) associated with the non-3GPP device 1. Exemplarily, the MC ID is used to identify the MC serviceuser, 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 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.

[0175] In another example, when the first user's identifier is MC IP, the first connection authorization request message carries the MC IP of the first user (such as user1) associated with non-3GPP device 1. A user can be identified by MC IP. In this case, Figure 3 The communication method shown is applicable to the scenario where a non-3GPP device uses a permanent IP or a MC service user (or MC user) uses a permanent IP. For a non-3GPP device or MC service user, the permanent IP may be allocated by a gateway UE or pre-configured by the system.

[0176] Exemplarily, in addition to carrying 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 requesting authorization, user connection preference (such as preemption priority or retention of existing connection 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. Among them, the data flow description information is used to describe the information of 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).

[0177] For the GW MC service ID, the GW MC service ID can be an identifier on the configured gateway UE1 and MCgateway 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.

[0178] For MC service, the MC service type to which the first connection is applicable (associated) is indicated, for example, one or more of MCPTT, MCVideo, and MCData.

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

[0180] 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 also be installed with an MC client.

[0181] 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.

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

[0183] Optionally, when the MC Service Server includes an MC gateway UE function module, gatewayUE1 (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.

[0184] In an embodiment of the present application, in addition to the information carried by the first connection authorization request message, the second connection authorization request message may also carry an 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.

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

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

[0187] (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 passed 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.

[0188] (3) gateway UE1 (or MC gateway UE server in gateway UE1) determines whether the association relationship between the device information of non-3GPP device 1 and the MC ID is included in the association relationship that allows authorization (such as the list of association relationships that allow authorization), so as to determine whether the connection of the first user is authorized. For example, when the association relationship is included in the association relationship that allows authorization, gateway UE1 (or 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 the situation where the device is stolen or the user uses the wrong device.

[0189] (4) gateway UE1 (or MC gateway UE server in gateway UE1) determines whether the connection of the first user is authorized by determining whether the first user already has a connection for the same service or whether the connection number exceeds the upper limit of the number of connections per service of a single user (for example, the upper limit of the number of connections is 1 or other values ​​greater than 1). When the upper limit of the number of connections is 1, the situation is the same as that of the current user already having a connection for the same service.

[0190] For example, when the first user already has a connection for the same service or the number of connections for the first user exceeds the upper limit of the number of connections for a single user per service, gateway UE1 (or 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 connection authorization request of the first user (and to 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). Thereafter, the first user may disconnect part of the flow and then initiate a connection authorization to gateway UE1 again.

[0191] For another example, when the first user does not have a 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.

[0192] (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.

[0193] For example, a simple resource management method is to configure a fixed number of connections / users served. For example, when the number of connections / users 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) and the user priority (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. For example, 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 the 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 authority, and may be a group member of one or several groups, or may also be a super user.

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

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

[0196] (1) 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 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 connection of the first user is authorized. For example, after the MC ID+(optionally, security credentials) carried in the second connection authorization request message is successfully verified, the MC Service Server determines that the first user is an authorized user, thereby determining that the connection of the first user can be authorized.

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

[0198] (2) When the identifier of the first user carried in the second connection authorization request message is the 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.

[0199] For example, the MC Service Server may determine whether to allow the MC ID to access through gateway UE1 according to 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 connection of the first user can be authorized.

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

[0201] For example, the MC Service Server may determine whether to allow the MC IP to access through gateway UE1 according to 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 connection of the first user can be authorized.

[0202] (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.

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

[0204] (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 MCID, the device information of the non-3GPP device 1, and the identifier of the gateway UE1 is allowed.

[0205] For example, the MC Service Server may determine whether the association between the MC ID, the device information of the non-3GPP device 1, and the identification of the gateway UE1 is permitted according to the association between the permitted MC ID, the device information of the non-3GPP device, and the identification of the gateway UE configured on the MC Service Server. For example, when the association between the MC ID, the device information of the non-3GPP device 1, and the identification of the gateway UE1 is included in the configured association, the MC Service Server determines that the connection of the first user can be authorized.

[0206] 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 among MC IP, device information of non-3GPP device 1 and identifier of gateway UE1 is allowed.

[0207] For example, the MC Service Server can determine 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 according to the association between the allowed MC IP, the device information of the non-3GPP device, and the identifier of the gateway UE configured on the MC Service Server. For example, when the association between the MC IP, the device information of the non-3GPP device 1, and the identifier of the gateway UE1 is included in the configured association, the MC Service Server determines that the connection of the first user can be authorized.

[0208] (5) When the second connection authorization request message carries the data flow description information for requesting authorization, the MC Service Server determines whether the connection of the first user is authorized by checking the data flow description information. For example, taking the data flow description information including a URL as an example, the MC Service Server resolves the URL to a corresponding server IP address, and when determining that the server IP address is the IP address of the MC Service Server, it is determined that the connection of the first user can be authorized.

[0209] (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.

[0210] Operation a: MC Service Server may send a response message of the second connection authorization request message to gateway UE1. The response message of the second connection authorization request message is used to indicate the rejection of the connection authorization request of the first user (and indicates the specific rejection reason, such as the existence of the same service connection). Afterwards, gateway UE1 may also send a response message of the first connection authorization request message to the non-3GPP device 1 according to the response message of the second connection authorization request message. The response message of the first connection authorization request message is used to indicate the rejection of the connection authorization request of the first user (and indicates the specific rejection reason, such as the existence of the same service connection).

[0211] For example, the MC Service Server may reject the connection authorization request of the first user based on the data flow (such as ongoing traffic) being carried out by the first user on another gateway UE (such as gateway UE2), or based on system preference settings (such as setting to retain the original connection, giving priority to specific devices, etc.) or user connection preferences (the reported or pre-configured user connection preferences indicate retaining the oldest connection), or based on location / distance, etc. Specifically, the MC Service Server may also reject the connection authorization of a specific service, and more specifically, may also reject the data flow under the service that is indicated to be rejected in the response message of the above-mentioned 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.

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

[0213] In a 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 according to one or more of the user connection preference, the location information of the non-3GPP device 1, or the fact that the gateway UE2 has no ongoing data flow, and indicate the preemption reason or the disconnection reason, such as Figure 3As shown in (a, sending a connection preemption request). For example, the MC Service Server may also carry information about the preempted service or preempted data stream in the connection preemption request (or connection disconnection request or notification message). If the preempted service or preempted data stream is not specified, all services or all data streams are preempted by default. Optionally, gateway UE2 may further send a connection preemption request (or connection disconnection request or notification message) to the non-3GPP device 2 (or the MC gateway client of the non-3GPP device 2). After receiving the connection preemption 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 preemption response / indication information (such as an indication to retain the original connection) to the MC Service Server.

[0214] In another possible implementation, the MC Service Server may 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) through the gateway UE1 according to one or more of the user connection preference, the location information of the non-3GPP device 1, or the fact that the gateway UE2 has no ongoing data flow, so as 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, for example Figure 3 As shown in (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 a notification message) to the gateway UE2, and indicates the preemption reason or disconnection reason. At this time, the gateway UE2 does not need to 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).

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

[0216] c1. Preemption of the same service: The MC Service Server preempts the connection of a user with the same service and a lower user priority than the first user according to the user priority of the first user. If the user has an ongoing data stream, the MC Service Server can indicate which specific data stream (such as IP quintuple) to preempt.

[0217] c2. Inter-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 according to the service priority corresponding to the MCservice ID carried in the second connection authorization request message. For example, taking the service corresponding to the MC service ID as MCPTT and the other service as 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 streams, the MC Service Server can indicate which specific data stream (such as IP quintuple) to preempt.

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

[0219] The MC Service Server obtains the ongoing traffic information (such as MC ID, IP address of non-3GPP device, or MC IP, IP address of non-3GPP device) on one or several non-3GPP devices from other service servers (other MC servers), so that the connection of non-3GPP devices with no ongoing traffic on other connections can be accurately seized. For example, the MC Service Server sends a query message to other MC servers. The query message may carry (IP address of non-3GPP device or IP address of non-3GPP device + MC ID or IP address of non-3GPP device + MC IP), which is used to query the connection status information (or can be understood as the connection status) of the user corresponding to the MC ID or MC IP on other MC servers. After receiving the query message, other MC servers query the connection status information of the user corresponding to the MC ID or MC IP, and feedback the connection status information (such as whether there is a connection and the number of connections) to the MC Service Server. Optionally, the MC Service Server may also determine whether there is ongoing traffic on a non-3GPP device based on the corresponding relationship reported in step 306 and the information of the established or terminated data flow reported in step 307.

[0220] 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 determines whether to preempt other connections of the user by considering whether the user directly uses MC service UE to access the server. If so, 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 service authorization of the user with MC ID from other MC service sever. There is a scenario in which the user directly uses 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.

[0221] Optionally, the MC Service Server may send a connection preemption request to the selected non-3GPP device (such as non-3GPP device 2) through gateway UE1 (or MC gatewayUE server in gateway UE1) according to one or more selected preempted non-3GPP devices (such as non-3GPP device 2) in the above operation c, such as Figure 3 As shown in (b, sending a connection preemption request). In one example, the connection preemption request may carry at least one of the MC ID or the MC service ID or the 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. At this time, the connection preemption request may carry at least one of the MC IP or the MCservice ID or the GW MC service ID. Optionally, the connection preemption request may also carry information about the preempted service or the preempted data stream. If the preempted service or the preempted data stream is not specified, all services or all data streams 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.

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

[0223] In a 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 has succeeded) 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 an independent message and send it to the gateway UE1 (or the MC gatewayUE server in the gateway UE1).

[0224] In another possible implementation, when the authorization check of the connection of the first user requested by the second connection authorization request message fails, the MC Service Server may carry information indicating that the authorization fails (or the authorization fails or the authorization is rejected) in the response message of the second connection authorization request message. Optionally, the MC Service Server may also carry information about the rejected service or the rejected data flow in the response message of the second connection authorization request message.

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

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

[0227] In one example, when the response message of 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 of 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 for subsequent corresponding routing operations for data flows from non-3GPP devices.

[0228] 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.

[0229] 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.

[0230] 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.

[0231] 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.

[0232] For example, in the process of non-3GPP device 1 (or MC client in non-3GPP device 1) initiating a service process to MC Service Server, when one or more service data packets sent by non-3GPP device 1 to MC Service Server pass through gateway UE1 (or MC gateway UE server in gateway UE1), gateway UE1 (or MC gateway UE server in 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 IP triplet, IP quadruple or IP quintuple) is included in the authorized data flow information.

[0233] 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 a message indicating 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 initiate the authorization connection process again for a specific data packet.

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

[0235] Exemplarily, 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.

[0236] 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. Among them, 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).

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

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

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

[0240] 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 business server) can timely and accurately connect to the user from which the connection requested for authorization by the authorization request message comes, so that effective access control can be achieved for the user who accesses the connection by using the gateway user device and the data stream initiated by the user, thereby avoiding a user from connecting to the service device through multiple gateway user devices, that is, avoiding a user from occupying too many resources, and by judging whether there are available resources on the gateway user device (such as judging whether the number of connections, the number of users, or the number of data streams served by the gateway user device exceeds the upper limit), it can also be further achieved to 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 which connection to let the user use among multiple connections.

[0241] Figure 4 The following is a flow chart showing another communication method provided by an embodiment of the present application. Figure 1a , Figure 1b or Figure 1c The communication system architecture shown in the figure. The method process 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 device can be as follows Figure 1a The emergency task service user equipment shown, or it may also be as shown Figure 1b The MCPTT UE shown in FIG. Figure 1c The non-3GPP device shown; the gateway user equipment may be such as Figure 1c The gateway user equipment shown; the service equipment can be such as Figure 1a The emergency task service server shown, or it can also be Figure 1b The MCPTT server shown in FIG. Figure 1c The emergency task service server or the general service core or the session initiation protocol core or the gateway user equipment function module or the hypertext transfer protocol proxy module shown. It should be understood that in the example Figure 1aThe communication method provided in the embodiment of the present application is also applicable when a gateway user device is introduced between the emergency task service user device and the emergency task service server, or in the case of Figure 1b 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. Figure 4 In the implementation scheme of the communication method shown, 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, Figure 4 The implementation scheme of the communication method shown is understood as a user plane control scheme. In order to facilitate the introduction of the technical solution provided by the embodiment of the present application, the following takes the first communication device as a first user equipment, the second communication device as a gateway user equipment, and the third communication device as a 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. Figure 4 As shown, the method includes:

[0242] Step 401: A first user equipment sends a first data packet to a gateway user equipment. The gateway user equipment receives the first data packet.

[0243] 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.

[0244] 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) as an example, the identifier of user1 may be MC ID1, or may also be MC IP1.

[0245] 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.

[0246] In an embodiment of the present application, before the first user device sends a first data packet to the gateway user device, the identity authentication management server (or configuration management server) may provide the gateway user device with data flow information that is allowed to be routed (for example, it may 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 may also be characteristic information of the user authentication message (such as the message header name, the information of the message header, such as the header information carried in the HTTP message, which may 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 may 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.

[0247] Optionally, after the gateway user equipment completes identity authentication with the identity authentication management server, the address information of the identity authentication management server that allows routing or the characteristic information of the user authentication message may also be sent to the gateway user equipment by the configuration management server on the network side. The gateway user equipment receives and saves the address information of the identity authentication management server that allows routing or the characteristic information of the user authentication message.

[0248] 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.

[0249] Optionally, the gateway user equipment may forward to the service device (such as an authentication device) a first message encapsulated in a first data packet. Exemplarily, 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 (such as an identity authentication server) is used to provide identity authentication services to the first user.

[0250] In one possible implementation, when the gateway user equipment stores data flow information that is allowed to be routed, if the gateway user equipment 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).

[0251] In another possible implementation, when the gateway user equipment stores characteristic information of a user authentication message, if the gateway user equipment 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 may be forwarded to the identity authentication management server.

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

[0253] Step 403: If the first user identity authentication is passed, 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.

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

[0255] 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 MCService Server or other business servers (such as a SIP Core)).

[0256] Exemplarily, the authorized (or allowed) routing address information (or routing address information list) may include the communication address of the authorized service device (such as a service server), or may include the first routing address information (such as the IP address and port number / URL of the service server (especially, the IP address and port number for the SIP connection), or the address and port number / URL of the SIP core) and the second routing address information (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)). The first routing address information may indicate the authorized service communication address of the service device (such as the service server) and / or the control plane communication address of the authorized service device (such as the service server); the second routing address information may be used to indicate the user plane communication address of the authorized service device (such as the service server).

[0257] 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.

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

[0259] 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 authentication has passed (or succeeded), or it may also be used to indicate that the first user authentication has not passed (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.

[0260] 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 respectively and provided to the gateway user equipment.

[0261] Exemplarily, the following takes the example of carrying the first routing address information and the second routing address information in two messages respectively provided to the gateway user equipment 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 respectively.

[0262] 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. Exemplarily, taking the first routing address information encapsulated in a message (such as message 1) as an example, 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. Afterwards, when 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 according to 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 actively triggered by the first user device 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) is 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 business 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 is 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.

[0263] After receiving the second data packet, if the service authorization (or service registration) for the first user is completed, the service device 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 the service authorization is completed, and the service registration response message is used to indicate that the service registration is completed. 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.

[0264] Optionally, after the service device completes the service authorization (or service registration) for the first user, the service device (such as a business server or a configuration management server) may provide the gateway user device with the second routing address information. Optionally, the second routing address information may be encapsulated in a message and sent. Exemplarily, taking the second routing address information encapsulated in a message (such as message 2) as an example, after receiving message 2, the gateway user device may obtain the second routing address information from message 2 and may save the second routing address information. Then, when the gateway user device receives a data packet (or may be understood as a data stream, such as data packet 1, for example, data packet 1 is a group call request) from the first user device, it may determine whether to route or reject data packet 1 according to the second routing address information stored locally. 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 process data packet 1 accordingly, and then send a response message to data packet 1 to the first user device. 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.

[0265] 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 number threshold; or the identification of the first user has been de-registered or 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 routing address information allowed (or authorized) was provided to gateway UE1 is greater than or equal to the time threshold, or for example, the time 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.

[0266] Afterwards, the service device may 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 the user sends a specific service. After receiving the third routing address information, the gateway user device may update the first routing address information and / or the 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 may determine whether to route or reject the third data packet according to the updated first routing address information and / or the 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 the second routing address information (i.e., the third routing address information), the gateway user device may 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 may also be used to instruct the first user device to re-initiate identity authentication or re-initiate service authorization.

[0267] 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.

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

[0269] Based on the above Figure 4 In the implementation scheme of the communication method shown in the figure, the following takes the first user's identifier as MC ID or MCIP, the first user equipment as non-3GPP equipment 1, the gateway user equipment as gateway UE1, the service equipment as identity authentication management server and MC Service Server, the first routing address information as the service equipment address allowed for routing, and the second routing address information as the data flow address allowed for routing as an example, through Figure 5 The specific example shown above Figure 4 It is understood that in the embodiment of the present application, the action performed by a network element can also be replaced by the action performed by the functional component in the network element. In the embodiment of the present application, the functional component may include at least one of a chip, a chip system, a processor, and a processing unit.

[0270] Figure 5 A flow chart of another communication method provided in an embodiment of the present application. Figure 5 The communication method shown is suitable for emergency mission service communication system architecture. Figure 5 As shown, the specific process of the method may include:

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

[0272] 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, it may be 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 it may be characteristic information of the user authentication message (such as the message header name, the information of the message header, 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.

[0273] 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 saves the address information of the identity authentication management server or the characteristic information of the user authentication message that is allowed to be routed.

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

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

[0276] 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 for the first user. For example, the identity authentication request message may carry the MC ID or MC IP of the first user.

[0277] 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.

[0278] In a possible implementation, when gateway UE1 stores data flow information that is allowed to be routed, if gateway UE1 determines that the destination address of the first IP data packet is included in the data flow information that is allowed to be routed, the first IP data packet may be forwarded to the identity authentication management server.

[0279] 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, the first IP data packet may be forwarded to the identity authentication management server.

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

[0281] 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.

[0282] 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).

[0283] In the process of the identity authentication management server sending 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 .

[0284] 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.

[0285] Exemplarily, the service device address that allows routing (such as the IP address and port number / URL of the service server (especially, the IP address and port number for the SIP connection), or the address and port number / URL of the SIP core) can be provided to the gateway UE1 by the identity authentication management server, or can also 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). Exemplarily, the service server can include but is not limited to the MC Service Server or the SIP Core, etc.

[0286] Among them, the success of the identity authentication of a specific user, this information or event 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 MCService Server obtains from the identity authentication management server whether the specific user has completed the identity authentication.

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

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

[0289] Exemplarily, the second IP data packet encapsulates a service authorization message or a SIP registration message, wherein 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.

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

[0291] 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 the service device address list allowed for routing), the second IP data packet can be forwarded to the MC Service Server.

[0292] 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 MC Service Server.

[0293] 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 service device address allowed for routing, the second IP data packet may be forwarded to the SIP core.

[0294] 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.

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

[0296] 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.

[0297] Exemplarily, the service authorization response message may carry information indicating that the service authorization is passed. In the process of the MCService Server sending the service authorization response message to the non-3GPP device 1, the service authorization response message first passes through the gateway UE1 and is forwarded by the gateway UE1 to the non-3GPP device 1. Optionally, the service authorization response message may also be encapsulated in a data packet for routing.

[0298] Optionally, when the second IP data packet encapsulates a SIP registration message, after completing the SIP registration, the SIP core may send a SIP registration response message to the non-3GPP device 1. Exemplarily, the SIP registration response message may carry information indicating that the SIP registration is successful. In the process of the SIP core sending the SIP registration response message to the non-3GPP device 1, the SIP registration response message first passes through the gateway UE1 and is forwarded to the non-3GPP device 1 by the gateway UE1.

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

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

[0301] 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.

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

[0303] 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.

[0304] 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.

[0305] Optionally, when gateway UE1 determines that the destination address of the third IP data packet is not included in the service device address allowed for routing, the third IP data 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.

[0306] 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.

[0307] Exemplarily, the service request response message may carry the corresponding result for the service request. In the process of MC ServiceServer sending the service request response message to the non-3GPP device 1, the service request response message first passes through gatewayUE1 and is forwarded to the non-3GPP device 1 by gateway UE1.

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

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

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

[0311] Exemplarily, the second condition may be one of the following: the first user has already connected through other gateway UEs (for example, if the first user has multiple IP addresses / SIP addresses, it is considered that there is 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 or logged in or logged off from the MC service server (or other service server); or after a period of time (for example, the time interval from the last data stream address provided to gateway UE1 for routing is greater than or equal to the 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 other users may be preempted.

[0312] For example, when the identity of the first user has been de-registered from the MC service server (or other service server), the first user may 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 may be routed in a packet encapsulated therein.

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

[0314] In the embodiment of the present application, after the MC service server (or other service server) provides the updated data stream address and / or service device address allowed for routing to the gateway UE1, it will cause the user to re-initiate the authentication and authorization process the next time the user sends a specific service. For example, after the gateway UE1 refuses to route the first IP data packet sent by the MC client in the non-3GPP device 1, it can send a re-authentication message or a re-authorization message to the MC client in the 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.

[0315] It can be seen from the above steps 501 to 513 that after the identity authentication management server passes the identity authentication for 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 allows routing, so that the gateway user device can accurately determine whether to route or reject the data packet from the non-3GPP device (such as the data packet encapsulated with the service authorization message or the SIP registration message). In addition, after the service server completes the service authorization or SIP registration for the first user, the data flow address that allows routing can be provided to the gateway user device, so that the gateway user device can accurately determine whether to route or reject the data packet from the non-3GPP device (such as the data packet encapsulated with the service request (such as group call request) message). In this way, the method can achieve effective control of the access of the data packet from the user device.

[0316] It should be noted that in the description of the present application, "at least one" refers to one or more, and "multiple" refers to two or more. "And / or" describes the association relationship of the associated objects, indicating that there may be three relationships, for example, A and / or B, which can represent: the situation where A exists alone, A and B exist at the same time, and B exists alone, wherein A and B can be singular or plural. The character " / " generally indicates that the associated objects before and after are an "or" relationship. "At least one of the following (individuals)" or its similar expression refers to any combination of these items, including any combination of single items (individuals) or plural items (individuals). 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 the present 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 the present application all mean "including but not limited to", unless otherwise specifically emphasized in other ways.

[0317] In addition, it should be noted that each step involved in the above embodiments can be performed by a corresponding device, or by a chip, processor, or chip system in the device, and the embodiments of the present application do not limit them. The above embodiments are only described by taking the corresponding device as an example.

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

[0319] 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 the various functions. It should be easily appreciated by 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.

[0320] It should be noted that the "steps" in the embodiments of the present application are only for illustration, and are a method of expression used to better understand the embodiments, and do not constitute a substantial limitation on the execution of the scheme of the present application. For example, the "steps" can also be understood as "features". In addition, the steps do not constitute any limitation on the execution order of the scheme of the present application. Any changes in the order of steps, step merging, or step splitting made on this basis that do not affect the implementation of the overall scheme, and the resulting new technical solutions are also within the scope of the disclosure of the present application.

[0321] Based on the same concept, the present application embodiment also provides a possible communication device, which is suitable for Figure 1a or Figure 1b or Figure 1cThe communication system architecture shown. Optionally, the communication device may be a communication device (e.g., a user device (e.g., a first user device or a second user device or a third user device, etc.), a gateway user device (e.g., gatewayUE1 or gatewayUE2, etc.) or a service device (e.g., an MC service server or other business server or a configuration management server or an identity authentication management server)) or a device capable of supporting the communication device to implement the functions required by the communication method. In one example, when the communication device is a first user device (or a second user device or a third user device) (e.g., 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 a module (e.g., 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 possessed by 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 disposed in the first user device (or the second user device or the third user device), the communication device includes a transceiver and a processor, but does not include a memory. Among them, the transceiver exists as an input and output interface, and the input and output interface is used for the chip to realize the transceiving of the first user device (or the second user device or the third user device). The input and output interface may include an input interface and / or an output interface, the input interface can realize the reception of the first user device (or the second user device or the third user device), and the output interface can be used to realize the sending of the first user device (or the second user device or the third user device). The processor is used to read and execute the corresponding computer program or instruction so that the corresponding function of the first user device (or the second user device or the third user device) is realized. Optionally, when the chip realizes the corresponding function of the first user device (or the second user device or the third user device) in the above embodiment, the input and output interface can realize the transceiving operation performed by the first user device (or the second user device or the third user device) in the above embodiment; the processor can realize other operations other than the transceiving operation 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 relevant description of the first user device (or the second user device or the third user device) in the above embodiment, which will not be described in detail here.

[0322] 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 (such as a chip) of the communication device is used to implement the technical solutions involved in the gateway user equipment in the above embodiments, so the beneficial effects of the gateway user equipment in the above embodiments can also be achieved. 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. Among them, the transceiver exists as 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 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 instruction so that the corresponding function of the gateway user equipment is implemented. Optionally, when the chip implements the corresponding function of the gateway user equipment in the above embodiments, the input and output interface can implement the transceiver operation performed by the gateway user equipment in the above embodiments; the processor can implement other operations except the transceiver operation performed by the gateway user equipment in the above embodiments. 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.

[0323] In another example, when the communication device is a service device (such as an MC service server or other business server or 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 the module (such as a chip) of the communication device is used to implement the technical solutions involved in the service device in the above embodiments, so the beneficial effects of the service device in the above embodiments can also be achieved. Exemplarily, when the communication device is a chip set in the service device, the communication device includes a transceiver and a processor, but does not include a memory. Among them, the transceiver exists as 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 service device, and the output interface can be used to implement the sending of the service device. The processor is used to read and execute the corresponding computer program or instruction so that the corresponding function of the service device is implemented. Optionally, when the chip implements the corresponding function of the service device in the above embodiments, the input and output interface can implement the transceiver operation performed by the service device in the above embodiments; the processor can implement other operations except the transceiver operation performed by the service device in the above embodiments. For specific related descriptions, please refer to the relevant description of the service device in the above embodiments, which will not be described in detail here.

[0324] See also Figure 6The communication device 600 includes a communication module 601 (or a transceiver module, used to send and receive data) and a processing module 602. The communication device 600 is used to implement the above Figures 2 to 3 The method embodiment shown includes functions of a first communication device (such as user equipment (eg, first user equipment or second user equipment or third user equipment, etc.)) or a second communication device (such as gateway user equipment) or a third communication device (such as service equipment).

[0325] Optionally, the communication module 601 may include a receiving module and / or a sending module. The receiving module may be used for the communication device 600 to receive signals (information or data, etc.); the sending module may be used for the communication device 600 to send signals (information or data, etc.). The sending module may send 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.

[0326] When the communication device 600 is used to implement the above Figures 2 to 3 The function of the gateway user equipment in the method embodiment shown is: a communication module 601 is used to receive a first message from a first user equipment. The first message includes an identifier of a first user associated with the first user equipment, and the first message is used to request authorization for a connection of the first user. A processing module 602 is used to send a second message to a service device according to the first message. 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 a connection of the first user.

[0327] When the communication device 600 is used to implement the above Figures 2 to 3 The function of the service device in the method embodiment shown is: a communication module 601 is used to receive a second message from a gateway user device. The second message includes an identifier of a first user associated with the first user device, the second 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. A processing module 602 is used to send a response message of the second message to the gateway user device according to the second message, and the response message of the second message is used to authorize or reject the connection of the first user.

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

[0329] When the communication device 600 is used to implement the above Figures 4 to 5The functions of the gateway user equipment in the method embodiment shown are: a communication module 601, which is used to receive a first data packet from a first user equipment. A processing module 602, which is used 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 also used to receive the authorized routing address information. The processing module 602 is also used to route or reject the data flow from the first user equipment according to the authorized routing address information.

[0330] When the communication device 600 is used to implement the above Figures 4 to 5 The function of the service device in the method embodiment shown is: a communication module 601, which is used 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 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 for the first user. A processing module 602 is used to send authorized routing address information to the gateway user device if the first user identity authentication passes.

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

[0332] Wherein, when the communication device 600 is used to implement Figures 2 to 5 In the method embodiment shown in FIG. 1 , the functions of the first communication device, the second communication device, or the third communication device are described in detail with reference to the above Figures 2 to 5 The relevant descriptions about the first communication device or the second communication device or the third communication device in the illustrated method embodiment are not repeated here.

[0333] 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.

[0334] It should be noted that the division of modules in the embodiments of the present application is schematic and is only a logical function division. There may be other division methods in actual implementation. In addition, each functional unit in each embodiment of the present application may be integrated into a processing unit, or may exist physically separately, or two or more units may be integrated into one unit. The above-mentioned integrated unit may be implemented in the form of hardware or in the form of software functional units.

[0335] 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, 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, which is stored in a storage medium and includes several instructions for a computer device (which can be a personal computer, or a server, etc.) or a processor (processor) to perform all or part of the steps of the various embodiments of the present application. The aforementioned storage medium includes: U disk, mobile hard disk, read-only memory (ROM), random access memory (RAM), disk or optical disk, and other media that can store program codes.

[0336] Based on the same concept, the present application embodiment also provides a possible communication device, which is suitable for Figure 1a or Figure 1b or Figure 1cThe communication system architecture shown. Exemplarily, the communication device may 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 may be a device including a device required for executing the communication method provided in the embodiment of the present application. Optionally, the communication device may 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. Among them, 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 may realize the reception of the communication device, and the output interface may 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 the second communication device or the third communication device) in the above embodiment, the input and output interface can implement the transceiver operation performed by the first communication device (or the second communication device or the third communication device) in the above embodiment; the processor can implement other operations other than the transceiver operation performed by the first communication device (or the second communication device or the third communication device) in the above embodiment. For specific related descriptions, please refer to the relevant descriptions in the above embodiments, which will not be described in detail here. Exemplarily, the communication device is a first communication device (such as a user device (such as 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) as an example. When the communication device is used to implement the technical solution 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 solution 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 solution 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.

[0337] See also Figure 7, the communication device 700 includes: a transceiver 701, a processor 702. Optionally, the communication device 700 also includes a memory 703. Among them, 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 function of the above communication module 701 when executing the technical solution involved in the first communication device, and the processor 702 is used to implement the function of the above processing module 702 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 function of the above communication module 701 when executing the technical solution involved in the second communication device, and the processor 702 is used to implement the function of the above processing module 702 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 701 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 702 when executing the technical solution involved in the third communication device.

[0338] Optionally, the transceiver 701, the processor 702, and the memory 703 are interconnected via a bus 704. The bus 704 may be a peripheral component interconnect (PCI) bus or an extended industry standard architecture (EISA) bus. The bus may be divided into an address bus, a data bus, a control bus, and the like. For ease of representation, Figure 7 Only one thick line is used in the diagram, but this does not mean that there is only one bus or only one type of bus.

[0339] The transceiver 701 is used to receive and send data. For example, when the communication device 700 is as follows Figure 1a The emergency task service user equipment (or emergency task service server) shown in FIG. Figure 1b The MCPTT UE (or MCPTT server) or Figure 1c When the non-3GPP device (or gateway user equipment) is used as shown in FIG. Figure 1a , Figure 1b or Figure 1c Communicate with the RAN device shown, or it can also be implemented with Figure 1a , Figure 1b or Figure 1cIn one example, the transceiver may be a transceiver with integrated data transceiver function. In another example, the transceiver may 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.

[0340] Optionally, the transceiver 701 may include a transmitter and / or a receiver. The transmitter is used to send signals, messages, information, or data, etc. The receiver is used to receive signals, messages, information, or data, etc. Exemplarily, the transmitter sends signals, messages, information, or data, etc. under the control of the processor 702. The receiver receives signals, messages, information, or data, etc. under the control of the processor 702.

[0341] The functions of the processor 702 can refer to the description of the corresponding functions involved in the first communication device or the second communication device or the third communication device in the above embodiments, and will not be repeated here. Among them, the processor 702 can be a central processing unit (CPU), a network processor (NP) or a combination of CPU and NP, etc. The processor 702 can further include a hardware chip. The above-mentioned hardware chip can be an application-specific integrated circuit (ASIC), a programmable logic device (PLD) or a combination thereof. The above-mentioned 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 the processor 702 implements the above-mentioned functions, it can be implemented by hardware, and of course, it can also be implemented by executing the corresponding software through hardware.

[0342] The memory 703 is used to store program instructions, etc. Specifically, the program instructions may include program codes, and the program codes include computer operation instructions. The memory 703 may include random access memory (RAM), and may also include non-volatile memory (non-volatile memory), such as at least one disk storage. The processor 702 executes the program instructions stored in the 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.

[0343] Based on the same concept, the embodiment of the present application also provides a possible communication system, which includes a first communication device (such as a user equipment (such as a first user equipment)), a second communication device (such as a gateway user equipment) and a third communication device (such as a service device). Among them, 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.

[0344] 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 executed on a computer, the computer executes the method provided in the above embodiment.

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

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

[0347] 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.

[0348] 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 a user device (such as a first user device)), the second communication device (such as a gateway user device) or the third communication device (such as a service device) 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.

[0349] In the method provided in the embodiment of the present application, it can be implemented in whole or in part by software, hardware, firmware or any combination thereof. When implemented using software, it 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 embodiment of the present application is generated in whole or in part. The computer may be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions may 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 may be transmitted from a website site, computer, server or data center by wired (e.g., coaxial cable, optical fiber, digital subscriber line (digital subscriber line, DSL)) or wireless (e.g., infrared, wireless, microwave, etc.) mode to another website site, computer, server or data center. The computer-readable storage medium may be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more available media integrated. The available medium may be a magnetic medium (eg, a floppy disk, a hard disk, a magnetic tape), an optical medium (eg, a digital video disc (DVD)), or a semiconductor medium (eg, a solid state drive (SSD)).

[0350] The steps of the method described in the embodiments of the present application can be directly embedded in the hardware, the software unit executed by the processor, or the combination of the two. The software unit can be stored in RAM, ROM, EEPROM, register, hard disk, removable disk, CD-ROM or other storage media of any form 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 can write information to the storage medium. Optionally, the storage medium can also be integrated into the processor. The processor and the storage medium can be arranged in an ASIC.

[0351] The present application is described with reference to the flowchart and / or block diagram of the method, device (system), and computer program product according to the present application. It should be understood that each process and / or box in the flowchart and / or block diagram, as well as the combination of the process and / or box in the flowchart 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 function specified in one process or multiple processes in the flowchart and / or one box or multiple boxes in the block diagram.

[0352] These computer program instructions may also be loaded onto a computer or other programmable data processing device so that a series of operational steps are executed on the computer or other programmable device to produce a computer-implemented process, whereby 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.

[0353] Obviously, those skilled in the art can make various changes and modifications to the present application without departing from the spirit and scope of the present application. Thus, if these modifications and variations of the present application fall within the scope of the claims of the present application and their equivalents, the present application is also 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, a third message is sent to the first user equipment, where 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; receiving a second message from the gateway user equipment, the second message being encapsulated in a second data packet and sent to the service device via the gateway user equipment, the second message being 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