Credit relay communication method, device, terminal and network side equipment

By receiving the relationship information and identification information sent by the network side, the trust of the second UE is judged, and the problem of untrustworthy relay communications on the other side is solved, ensuring the security of relay communications.

CN114650537BActive Publication Date: 2024-11-15VIVO MOBILE COMM CO LTD
View PDF 0 Cites 0 Cited by

Patent Information

Application Number
CN202011503936.8
Authority / Receiving Office
CN · China
Patent Type
Patents(China)
Current Assignee / Owner
Filing Date
2020-12-17
Publication Date
2024-11-15
Estimated Expiration
2040-12-17

AI Technical Summary

Technical Problem

In the existing communication system, the relay terminal cannot determine whether the communication partner is trustworthy during relay connection and communication, which poses a security risk.

Method used

By receiving the relationship information and identification information sent by the network side, it is determined whether the second UE is a trusted terminal and whether to perform relay connection and communication.

Benefits of technology

Ensure that only relay connections and communications are performed with credit terminals, and the security of relay communications is improved.

✦ Generated by Eureka AI based on patent content.

Smart Images

  • Figure CN114650537B_ABST
    Figure CN114650537B_ABST
Patent Text Reader

Abstract

The present application discloses a trusted relay communication method, apparatus, terminal and network-side equipment, belonging to the field of wireless communication technology. Among them, a trusted relay communication method is applied to a first UE, the method comprising: receiving relationship information sent by the network side, wherein the relationship information is used to indicate the trust relationship of the first UE; receiving identification information sent by a second UE, and based on the relationship information and the identification information, performing relay connection and / or relay communication with the second UE, or refusing to perform relay connection and / or relay communication with the second UE.
Need to check novelty before this filing date? Find Prior Art

Description

Technical Field

[0001] The present application belongs to the field of wireless communication technology, and specifically relates to a trusted relay communication method, device, terminal and network-side equipment. Background Art

[0002] In the existing communication system, for Layer 3 (L3) relay communication, in the scenario where there is no Non-3GPP InterWorking Function (N3IWF) involved, the relay terminal (User Equipment, UE) can identify the data of the remote UE at the Protocol Data Unit (PDU) layer level (Packet Data Convergence Protocol (PDCP) and above). If the relay UE is not a trusted relay, there are security or privacy risks. However, in the current relay communication, when establishing a relay connection and / or relay communication, there is no technical solution for determining whether the communication counterpart is trustworthy. Summary of the invention

[0003] The embodiments of the present application provide a trusted relay communication method, apparatus, terminal and network-side equipment, which can solve the problem of being unable to determine whether the communication counterpart is trustworthy when establishing a relay connection and / or relay communication.

[0004] In a first aspect, a trusted relay communication method is provided, which is applied to a first UE, and the method includes: receiving relationship information sent by a network side, wherein the relationship information is used to indicate a trust relationship of the first UE; receiving identification information sent by a second UE, and based on the relationship information and the identification information, performing a relay connection and / or relay communication with the second UE, or refusing to perform a relay connection and / or relay communication with the second UE.

[0005] In the second aspect, a trusted relay communication device is provided, including: a first receiving module, used to receive relationship information sent by the network side, wherein the relationship information is used to indicate the trust relationship of the first UE; a second receiving module, used to receive identification information sent by the second UE; and a communication module, used to perform relay connection and / or relay communication with the second UE based on the relationship information and the identification information, or refuse to perform relay connection and / or relay communication with the second UE.

[0006] According to a third aspect, a trusted relay communication method is provided, which is applied to a first network function entity, and includes: sending relationship information to a first UE, wherein the relationship information is used to indicate a trust relationship of the first UE.

[0007] In a fourth aspect, a trusted relay communication device is provided, comprising: a first acquisition module, used to acquire relationship information, wherein the relationship information is used to indicate a trust relationship of the first UE; and a second sending module, used to send the relationship information.

[0008] In a fifth aspect, a trusted relay communication method is provided, which is applied to a second network function, including: receiving a first trust relationship acquisition request sent by a first network function, wherein the first trust relationship acquisition request carries a user identifier or a terminal identifier of a first UE; and sending the trust relationship of the first UE to the first network function.

[0009] In the sixth aspect, a trusted relay communication device is provided, including: a fourth receiving module, used to receive a first trust relationship acquisition request sent by a first network function, wherein the first trust relationship acquisition request carries a user identifier or terminal identifier of the first UE; a third sending module, used to send the trust relationship of the first UE to the first network function.

[0010] In the seventh aspect, a trusted relay communication method is provided, which is applied to a third network function, including: receiving a trust relationship authentication request sent by a first UE, wherein the trust relationship authentication request carries user identification or terminal identification information of the second UE; based on the trust relationship of the first UE, sending a trust relationship authentication result to the first UE.

[0011] In the eighth aspect, a trusted relay communication device is provided, including: a fifth receiving module, used to receive a trust relationship authentication request sent by a first UE, wherein the trust relationship authentication request carries user identification or terminal identification information of a second UE; a fourth sending module, used to send a trust relationship authentication result to the first UE based on the trust relationship of the first UE.

[0012] In the ninth aspect, a trusted relay communication method is provided, which is applied to a first access network device, including: receiving a trust relationship of a first UE sent by a second access network device or a third network function; based on the trust relationship, executing resource scheduling established between the first UE and the second UE in the PC5 connection or rejecting the resource scheduling established between the first UE and the second UE in the PC5 connection.

[0013] In the tenth aspect, a trusted relay communication device is provided, including: a sixth receiving module, used to receive the trust relationship of the first UE sent by the second access network device or the third network function; an execution module, used to execute the resource scheduling established between the first UE and the second UE in the PC5 connection or reject the resource scheduling established between the first UE and the second UE in the PC5 connection based on the trust relationship.

[0014] In the eleventh aspect, a terminal is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect.

[0015] In the twelfth aspect, a network side device is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the third aspect, or implements the steps of the method described in the fifth aspect, or implements the steps of the method described in the seventh aspect, or implements the steps of the method described in the ninth aspect.

[0016] In the thirteenth aspect, a readable storage medium is provided, on which a program or instruction is stored. When the program or instruction is executed by a processor, the steps of the method described in the first aspect are implemented, or the steps of the method described in the third aspect are implemented, or the steps of the method described in the fifth aspect are implemented, or the steps of the method described in the seventh aspect are implemented, or the steps of the method described in the ninth aspect are implemented.

[0017] In a fourteenth aspect, a chip is provided, comprising a processor and a communication interface, wherein the communication interface is coupled to the processor, the processor is used to run a terminal program or instruction to implement the steps of the method described in the first aspect, and the processor is used to run a network-side device program or instruction to implement the steps of the method described in the third aspect, or to implement the steps of the method described in the fifth aspect, or to implement the steps of the method described in the seventh aspect, or to implement the steps of the method described in the ninth aspect.

[0018] In the fifteenth aspect, a computer program product is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the method described in the first aspect, or implements the steps of the method described in the third aspect, or implements the steps of the method described in the fifth aspect, or implements the steps of the method described in the seventh aspect, or implements the steps of the method described in the ninth aspect.

[0019] In an embodiment of the present application, the first UE receives relationship information indicating the trust relationship of the first UE sent by the network side, and upon receiving identification information sent by the second UE, based on the relationship information and the identification information, performs relay connection and / or relay communication with the second UE, or refuses to perform relay connection and / or relay communication with the second UE, that is, when the first UE determines that the second UE is a trusted UE based on the trust relationship and the identification information, it performs relay connection and / or relay communication with the second UE, otherwise, it refuses to perform relay connection and / or relay communication with the second UE. This ensures that relay connection and / or relay communication is performed only with the authorized terminal, ensuring the security of relay communication. BRIEF DESCRIPTION OF THE DRAWINGS

[0020] Figure 1 A schematic diagram showing a wireless communication system to which the embodiments of the present application can be applied;

[0021] Figure 2 A schematic diagram showing a flow chart of a credit relay communication method provided in an embodiment of the present application;

[0022] Figure 3 Another schematic diagram showing a flow chart of the credit relay communication method provided in an embodiment of the present application;

[0023] Figure 4 Another schematic diagram showing a flow chart of the credit relay communication method provided in an embodiment of the present application;

[0024] Figure 5 Another schematic diagram showing a flow chart of the credit relay communication method provided in an embodiment of the present application;

[0025] Figure 6 Another schematic diagram showing a flow chart of the credit relay communication method provided in an embodiment of the present application;

[0026] Figure 7 Another schematic diagram showing a flow chart of the credit relay communication method provided in an embodiment of the present application;

[0027] Figure 8 Another schematic diagram showing a flow chart of the credit relay communication method provided in an embodiment of the present application;

[0028] Fig. 9 Another schematic diagram showing a flow chart of the credit relay communication method provided in an embodiment of the present application;

[0029] Fig.10 A schematic diagram showing a structure of a credit relay communication device provided in an embodiment of the present application is shown;

[0030] Fig.11 Another structural schematic diagram of the credit relay communication device provided in an embodiment of the present application is shown;

[0031] Fig.12 Another structural schematic diagram of the credit relay communication device provided in the embodiment of the present application is shown;

[0032] Fig.13 Another structural schematic diagram of the credit relay communication device provided in the embodiment of the present application is shown;

[0033] Fig.14 Another structural schematic diagram of the credit relay communication device provided in the embodiment of the present application is shown;

[0034] Fig.15 A schematic diagram showing the structure of a communication device provided in an embodiment of the present application is shown;

[0035] Fig.16 A schematic diagram showing the hardware structure of a terminal provided in an embodiment of the present application is shown;

[0036] Fig.17 A schematic diagram of the hardware structure of a network side device provided in an embodiment of the present application is shown. DETAILED DESCRIPTION

[0037] The following will be combined with the drawings in the embodiments of the present application to clearly and completely describe the technical solutions in the embodiments of the present application. Obviously, the described embodiments are part of the embodiments of the present application, not all of the embodiments. Based on the embodiments in the present application, all other embodiments obtained by ordinary technicians in this field belong to the scope of protection of this application.

[0038] The terms "first", "second", etc. in the specification and claims of the present application are used to distinguish similar objects, and are not used to describe a specific order or sequence. It should be understood that the data used in this way can be interchangeable under appropriate circumstances, so that the embodiments of the present application can be implemented in an order other than those illustrated or described here, and the objects distinguished by "first" and "second" are generally of the same type, and the number of objects is not limited. For example, the first object can be one or more. In addition, "and / or" in the specification and claims represents at least one of the connected objects, and the character " / " generally represents that the objects associated with each other are in an "or" relationship.

[0039] It is worth noting that the technology described in the embodiments of the present application is not limited to the Long Term Evolution (LTE) / LTE-Advanced (LTE-A) system, but can also be used in other wireless communication systems, such as Code Division Multiple Access (CDMA), Time Division Multiple Access (TDMA), Frequency Division Multiple Access (FDMA), Orthogonal Frequency Division Multiple Access (OFDMA), Single-carrier Frequency-Division Multiple Access (SC-FDMA) and other systems. The terms "system" and "network" in the embodiments of the present application are often used interchangeably, and the described technology can be used for the systems and radio technologies mentioned above as well as for other systems and radio technologies. The following description describes a New Radio (NR) system for example purposes, and NR terminology is used in most of the following descriptions, but these technologies can also be applied to applications other than NR system applications, such as the 6th generation (6 th Generation, 6G) communication system.

[0040] Figure 1A schematic diagram of a wireless communication system applicable to an embodiment of the present application is shown. The wireless communication system includes a terminal 11 and a network side device 12. Among them, the terminal 11 can also be called a terminal device or a user terminal (User Equipment, UE), and the terminal 11 can be a mobile phone, a tablet computer (Tablet Personal Computer), a laptop computer (Laptop Computer) or a notebook computer, a personal digital assistant (Personal Digital Assistant, PDA), a handheld computer, a netbook, an ultra-mobile personal computer (ultra-mobile personal computer, UMPC), a mobile Internet device (Mobile Internet Device, MID), a wearable device (Wearable Device) or a vehicle-mounted device (VUE), a pedestrian terminal (PUE) and other terminal side devices, and the wearable device includes: a bracelet, a headset, glasses, etc. It should be noted that the specific type of the terminal 11 is not limited in the embodiment of the present application. The network side device 12 can be a base station (i.e., access network equipment) or a core network, wherein the base station can be referred to as a node B, an evolved node B, an access point, a base transceiver station (Base Transceiver Station, BTS), a radio base station, a radio transceiver, a basic service set (Basic Service Set, BSS), an extended service set (Extended Service Set, ESS), a B node, an evolved B node (eNB), a home B node, a home evolved B node, a WLAN access point, a WiFi node, a transmitting and receiving point (Transmitting Receiving Point, TRP) or some other suitable term in the field. As long as the same technical effect is achieved, the base station is not limited to a specific technical vocabulary. It should be noted that in the embodiment of the present application, only the base station in the NR system is taken as an example, but the specific type of the base station is not limited.

[0041] The core network can be composed of multiple network functions, such as Direct Discovery Name Management Function (DDNMF), Unified Data Management Function (UDM) and Access and Mobility Management Function (AMF), etc. These network functions can be set on the same network entity or on different network entities.

[0042] The following is a detailed description of the credit relay communication method provided in the embodiment of the present application through specific embodiments and their application scenarios in conjunction with the accompanying drawings.

[0043] Figure 2 A flow chart of a trusted relay communication method in an embodiment of the present application is shown, and the method 200 can be executed by a first UE. In other words, the method can be executed by software or hardware installed on the first UE. Figure 2 As shown, the method may include the following steps.

[0044] S210: Receive relationship information sent by the network side, where the relationship information is used to indicate a trust relationship of the first UE.

[0045] In an embodiment of the present application, the network side may send relationship information indicating the trust relationship (also referred to as a binding relationship) of the first UE to the first UE, and the first UE may determine which UEs are trusted UEs, i.e., authorized UEs, based on the relationship information.

[0046] In a possible implementation, the relationship information may include at least one of the following:

[0047] (1) First relay service code; for example, the network side may send the association identifier to the first UE and the second UE having a trust relationship. In the relay discovery phase or the connection establishment phase, the second UE may send the first relay service code as part or all of the identification information to the first UE. The first UE confirms that the second UE is a trusted terminal based on the received identification information and the first relay service code sent by the network side, and selects the second UE to establish a relay connection.

[0048] (2) An association identifier, wherein the association identifier is used to indicate that the first UE has a trust relationship with the second UE, or the association identifier is used to indicate the terminal identifier or user identifier of the second UE that has a trust relationship with the first UE. That is, in this possible implementation, the relationship information sent by the network side may be an indication that the first UE has a trust relationship with the second UE, for example, it may be a correspondence between the terminal identifier or user identifier of the first UE and the terminal identifier or user identifier of the second UE. Alternatively, the association identifier may also be the terminal identifier or user identifier of the second UE that has a trust relationship with the first UE, that is, the association identifier may be one or more terminal identifiers or user identifiers, indicating that the second UE corresponding to the one or more terminal identifiers or user identifiers has a trust relationship with the first UE, that is, the second UE corresponding to the one or more terminal identifiers or user identifiers is a trusted UE.

[0049] (3) A first set of keys; communication terminals with a trust relationship have the same first set of keys. For example, the network side can issue a first set of keys to a first UE and a second UE with a trust relationship. During the relay discovery or relay connection process, the second UE can use the first set of keys to encrypt the communication information. If the first UE successfully decrypts the communication information using the first set of keys, the second UE is confirmed to be a trusted terminal. Alternatively, during the relay discovery or relay connection process, the second UE can also use the first set of keys to sign the authentication information (for example, the terminal identification or user identification of the second UE), and send the signature information (which can be called verification information) to the first UE. The first UE uses the first set of keys issued by the network side to verify the signature information. If the verification passes, the second UE is confirmed to be a trusted terminal.

[0050] (4) Authentication information, which is used to verify the identification information. For example, the network side can send authentication information to the first UE and the second UE with a trust relationship. During the relay discovery or relay connection process, the second UE can use the authentication information to generate identification information and send it to the first UE. The first UE uses the authentication information to verify the identification information. If the verification is successful, the second UE is confirmed to be a trusted terminal. The authentication information can be information such as a verification code and a password.

[0051] (5) First service type information; through the first service type information, it is indicated that the terminal executing the service indicated by the first service type information has a trust relationship. In this possible implementation, the network side may consider that there is a trust relationship between communication terminals of a specific service type. During the relay discovery or relay connection process, the first UE determines the service type of the second UE based on the identification information of the second UE, and determines whether the service type of the second UE is a specific service type. If so, the second UE is confirmed to be a trusted terminal.

[0052] (6) First slice information; indicating that the communication terminals on the slice indicated by the first slice information have a trust relationship. In this possible implementation, the network side may consider that there is a trust relationship between the communication terminals on a specific slice. During relay discovery or relay connection, the first UE determines the slice where the second UE is located based on the identification information of the second UE, and determines whether the slice where the second UE is located is the slice indicated by the first slice information. If so, the second UE is confirmed to be a trusted terminal.

[0053] (7) First protocol data unit (PDU) session type information. Indicates that the communication terminals that execute the PDU session of the type indicated by the first PDU session type information have a trust relationship. In this possible implementation, the network side may consider that there is a trust relationship between the communication terminals that execute a specific PDU session type. During the relay discovery or relay connection process, the first UE determines the PDU session executed by the second UE based on the identification information of the second UE, and determines whether the PDU session executed by the second UE is the PDU session indicated by the first PDU session type information. If so, the second UE is confirmed to be a trusted terminal.

[0054] It should be noted that the relationship information may include only any one of the above (1) to (7), or any combination of two or more of the above (1) to (7). For example, the relationship information may include a first relay service code and a first group of secret keys. The first UE may determine whether to select the second UE for relay communication according to the first relay service code during relay discovery or relay connection. If selected, the first UE and the second UE perform mutual authentication based on the second group of secret keys to determine whether the other end is a trusted terminal. Of course, in specific applications, there may be other combinations, which are not limited in the specific embodiments of the present application.

[0055] S212, receiving identification information sent by the second UE, and based on the relationship information and the identification information, performing relay connection and / or relay communication with the second UE, or refusing to perform relay connection and / or relay communication with the second UE.

[0056] In S212, the first UE determines whether the second UE is a trusted terminal based on the relationship and the identification information, that is, determines whether the second UE is trustworthy, and if it is determined that the second UE is a trusted terminal, selects the second UE to perform relay connection and / or relay communication.

[0057] In a possible implementation, the identification information may include at least one of the following:

[0058] (1) A second relay service code; wherein the second relay service may be sent from the network side to the second UE.

[0059] (2) The terminal identifier or user identifier of the second UE. In this possible implementation, correspondingly, the relationship information sent by the network side includes the association identifier.

[0060] (3) Encrypted information or authentication information generated based on the second group of keys; in this possible implementation, the second UE may generate the encrypted information or authentication information based on the second group of keys sent by the network side. In a specific application, the encrypted information may be information obtained by the second UE using the second group of keys to encrypt the information to be encrypted. For example, the information to be encrypted may be the terminal identifier or user identifier of the second UE, or the information to be encrypted may also be communication information sent by the second UE to the first UE. The authentication information may be the result (for example, signature information) obtained by the second UE using the second group of keys to calculate the information to be authenticated according to a predetermined algorithm. The information to be authenticated may be the terminal identifier or user identifier of the second UE, or may be a random number generated by the second UE, etc. In this possible implementation, the corresponding relationship information sent by the network side includes the group of keys.

[0061] (4) verification information, where the verification information is a result obtained by performing verification calculation on the specified information to be verified. For example, the information to be verified may be a second relay service code sent by the network side to the second UE, or may be slice information where the second UE is located, or may be PDU session information executed by the second UE, etc. The second UE uses predetermined authentication information to perform verification calculation on the information to be verified to obtain the verification information, where the predetermined authentication information may be a verification code or password sent by the network side, etc.;

[0062] (5) Second service type information: The second service type information indicates the service type of the service executed by the second UE.

[0063] (6) Second slice information: The second slice information indicates a slice where the second UE is located. In this possible implementation, the relationship information may include the slice information.

[0064] (7) Second PDU session type information; the second PDU session type information indicates the PDU session type executed by the second UE.

[0065] It should be noted that the identification information may include only any one of the above (1) to (7), or any combination of two or more of the above (1) to (7). For example, the identification information may include a second relay service code and a second group of secret keys. The first UE may determine whether to select the second UE for relay communication according to the second relay service code sent by the second UE during the relay discovery or relay connection process. If selected, the first UE and the second UE perform mutual authentication based on the second group of secret keys to determine whether the other end is a trusted terminal. Of course, in specific applications, there may be other combinations, which are not limited in the specific embodiments of the present application.

[0066] In addition, the identification information may correspond to the relationship information. For example, if the relationship information includes a first relay service code, the identification information includes a second relay service code. If the relationship information includes a PDU session type, the identification information includes the PDU session type executed by the second UE. Of course, the identification information may not correspond to the relationship information. For example, the identification information may include a second PDU session type and a second relay service code executed by the second UE, and the relationship information may not include a PDU session type but include a first relay service code. The first UE may determine whether the second UE is a trusted terminal based on the first relay service code and the second relay service code. This is not specifically limited in the embodiments of the present application, as long as the first UE can determine whether the second UE has a trust relationship with the first UE based on the relationship information and the identification information.

[0067] It should be noted that, in actual applications, there is no specific order for receiving the relationship information sent by the network side and receiving the identification information sent by the second UE. For example, the first UE may first receive the relationship information sent by the network side, and then receive the identification information sent by the second UE, or may first receive the identification information sent by the second UE, and then receive the relationship information sent by the network side.

[0068] For example, in a possible implementation, before S210, the method further includes: sending the identification information of the second UE to the network side; then S210 includes: receiving the result returned by the network side for the identification information of the second UE, wherein the result includes the relationship information. That is, in this possible implementation, after receiving the identification information sent by the second UE, the first UE sends the identification information of the second UE to the network side, and after receiving the identification information of the second UE, the network side returns the relationship information to the first UE. Through this possible implementation, the first UE can obtain the relationship information from the network side during relay discovery or relay connection, that is, when it is necessary to verify whether the second UE is a trusted UE.

[0069] In a possible implementation, in S212, after the first UE determines that the second UE is a trusted UE, it can choose to perform relay connection and / or relay communication with the second UE. In the process of performing relay connection and / or relay communication, in order to avoid the received relationship information being obtained by other non-trusted UEs during the discovery process, the first UE can also request the network side to authenticate the second UE again. Therefore, in this possible implementation, the method may also include: when performing relay connection and / or relay communication with the second UE, the first UE sends a trust relationship authentication request to a third network function, wherein the trust relationship authentication request carries the user identification or terminal identification information of the second UE; receiving the trust relationship authentication result sent by the third network function; performing relay connection and / or relay communication with the second UE based on the trust relationship authentication result, or refusing to perform relay connection and / or relay communication with the second UE. In this possible implementation, the first UE sends a trust relationship authentication request to the third network function, requesting the third network function to authenticate the trust relationship between the first UE and the second UE. After receiving the trust relationship authentication request, the third network function authenticates the trust relationship between the first UE and the second UE, and returns the authentication result to the first UE. When the trust relationship authentication result returned by the third network function indicates that the first UE and the second UE have a trust relationship, the first UE performs relay connection and / or relay communication with the second UE, or, when the trust relationship authentication result indicates that the first UE and the second UE do not have a trust relationship, refuses to perform relay connection and / or relay communication with the second UE. Through this possible implementation, it can be avoided that the relationship information is obtained by other non-trusted UEs during the discovery process, and the trusted UE pretends to be the first UE, which can further ensure the security of relay communication.

[0070] In the above possible implementation manner, optionally, the third network function may be an AMF. The third network function may determine whether the first UE and the second UE have a trust relationship according to the trust relationship of the first UE.

[0071] In the above-mentioned trusted relay communication method provided in the embodiment of the present application, the first UE receives the relationship information indicating the trust relationship of the first UE sent by the network side, and when receiving the identification information sent by the second UE, based on the relationship information and the identification information, performs relay connection and / or relay communication with the second UE, or refuses to perform relay connection and / or relay communication with the second UE, that is, when the first UE determines that the second UE is a trusted UE based on the trust relationship and the identification information, it performs relay connection and / or relay communication with the second UE, otherwise, it refuses to perform relay connection and / or relay communication with the second UE. Thereby, it ensures that relay connection and / or relay communication is performed only with the trusted terminal, and ensures the security of relay communication.

[0072] Figure 3 Another flow chart of the trusted relay communication method provided in the embodiment of the present application is shown. The method 300 can be executed by the first network function. In other words, the method can be executed by software or hardware installed on the first network function. Figure 3 As shown, the method may include the following steps.

[0073] S310: Send relationship information to a first UE, where the relationship information is used to indicate a trust relationship of the first UE.

[0074] In the application embodiment, the relationship information is the same as the relationship information in method 200. For details, please refer to the relevant description in method 200, which will not be repeated here.

[0075] In an embodiment of the present application, the first network function may send the relationship information to each member terminal having a trust relationship. For example, if the first UE and the second UE have a trust relationship, the first network function may send the relationship information to both the first UE and the second UE.

[0076] In a possible implementation, the first network function may obtain the trust relationship of the first UE from the second network function or the application server, and send the relationship information to the first UE based on the trust relationship. Therefore, in this possible implementation, before S310, the method may further include:

[0077] Sending a trust relationship acquisition request to a second network function or application server, wherein the trust relationship acquisition request carries a user identifier or a terminal identifier of the first UE;

[0078] Receive the trust relationship of the first UE returned by the second network function or application server.

[0079] Optionally, the trust relationship may be an association relationship between two or more users, that is, the trust relationship indicates an association relationship between two or more users. For example, there is an association relationship at the contract level, for example, when signing a contract, the first UE indicates that it can be used as a remote terminal of the second UE, or when signing a contract, the second UE indicates that it can be used as a relay terminal of the first UE, then the first UE and the second UE have an association relationship.

[0080] Optionally, the trust relationship acquisition request may also carry a user identifier or a terminal identifier of the second UE, that is, the trust relationship acquisition request is used to request to obtain the trust relationship between the first UE and the second UE.

[0081] Optionally, the two or more users may be one of the following users: a specific service, a specific slice, a specific data network name (DNN), and a specific PDU session. That is, there is an association relationship between two or more users with a specific service, a specific slice, a specific DNN or a specific PDU session, that is, these users can be trusted terminals, and the terminal corresponding to one user can serve as a relay terminal for the terminal corresponding to another user.

[0082] In the above possible implementations, the second network function may return the trust relationship to the first network function, and the application server may generate the relationship information based on the trust relationship, and transparently transmit the relationship information to the first UE through the first network function. Therefore, optionally, S310 may include: generating the relationship information based on the trust relationship returned by the second network function, and sending it to the first UE; or forwarding the trust relationship returned by the application server to the first UE.

[0083] In a possible implementation manner of the embodiment of the present application, the first network function may send the relationship information to the first UE upon receiving the identification information of the second UE sent by the first UE.

[0084] In the embodiment of the present application, the first network function includes but is not limited to DDNMF.

[0085] Through the trusted relay communication method provided in the embodiment of the present application, the first network function can send the relationship information to the first UE, so that the first UE can determine whether the communication counterpart, i.e., the second UE, is a trusted UE based on the relationship information, thereby improving the security of relay communication.

[0086] Figure 4 Another flow chart of the trusted relay communication method provided by the embodiment of the present application is shown. The method 400 can be executed by the second network function. In other words, the method can be executed by software or hardware installed on the second network function. Figure 4 As shown, the method may include the following steps.

[0087] S410: Receive a first trust relationship acquisition request sent by a first network function, wherein the first trust relationship acquisition request carries a user identifier or a terminal identifier of a first UE.

[0088] In the embodiment of the present application, the first network function may be the first network function in method 300 , and the second network function may be the second network function in method 300 .

[0089] In an embodiment of the present application, after receiving the first trust relationship acquisition request, the trust relationship of the first UE can be acquired according to the user identifier or terminal identifier of the first UE.

[0090] In a possible implementation, the trust relationship is an association relationship between two or more users.

[0091] Optionally, the two or more users are one of the following users: a specific service, a specific slice, a specific DNN, and a specific PDU session. After receiving the first trust relationship acquisition request, the second network function can determine whether the first UE belongs to the specific service, the specific slice, the specific DNN, and the specific PDU session according to the user identifier or terminal identifier of the first UE. If so, the trust relationship of the first UE can be obtained based on the specific service, the specific slice, the specific DNN, and the specific PDU session.

[0092] In one possible implementation, the first trust relationship acquisition request may also carry the user identifier or terminal identifier of the second UE. The second network function may determine whether the first UE and the second UE both belong to a specific service, a specific slice, a specific DNN, and a specific PDU session based on the user identifier or terminal identifier of the first UE and the user identifier or terminal identifier of the second UE. If so, it is determined that the first UE and the second UE have a trust relationship.

[0093] S412: Send the trust relationship of the first UE to the first network function.

[0094] In the embodiment of the present application, after receiving the trust relationship of the first UE, the first network function generates the relationship information and sends it to the first UE. For details, please refer to the description in the above method 300, which will not be repeated here.

[0095] In a possible implementation, the method may further include: receiving a second trust relationship acquisition request from a third network function, wherein the second trust relationship acquisition request carries identification information of the first UE; and sending the trust relationship of the first UE to the third network function.

[0096] In the embodiment of the present application, the second network function includes but is not limited to UDM.

[0097] Through the trusted relay communication method provided in the embodiment of the present application, the second network function can send the trust relationship of the first UE to the first network function when receiving the trust relationship acquisition request of the first network function, so that the first network function can obtain the relationship information described in the above methods 200 and 300 based on the trust relationship, and send the relationship information to the first UE, so that the first UE can determine whether the relay peer is a trusted UE based on the relationship information in the relay connection and / or relay communication to ensure the security of the relay communication.

[0098] Figure 5 Another flow chart of the trusted relay communication method provided in the embodiment of the present application is shown. The method 500 can be executed by a third network function. In other words, the method can be executed by software or hardware installed on the third network function. Figure 5 As shown, the method may include the following steps.

[0099] S500: Receive a trust relationship authentication request sent by a first UE, wherein the trust relationship authentication request carries user identification or terminal identification information of a second UE.

[0100] In a possible implementation, the first UE may send the trust relationship authentication request to the third network function when receiving the identification information of the second UE. For details, please refer to the relevant description in method 200, which will not be repeated here.

[0101] In the embodiment of the present application, the third network function may be the third network function in methods 200 to 400.

[0102] S512: Based on the trust relationship of the first UE, send a trust relationship authentication result to the first UE.

[0103] In the embodiment of the present application, the third network function may determine whether the second UE is a trusted UE of the first UE based on the trust relationship of the first UE, that is, determine whether the second UE has a trust relationship with the first UE.

[0104] In a possible implementation, the trust relationship may be the same as the trust relationship in method 400, and for details, refer to the relevant description in the above method 400.

[0105] In one possible implementation, the third network function can determine whether the first UE and the second UE both belong to a specific service, a specific slice, a specific DNN, and a specific PDU session based on the user identifier or terminal identifier of the first UE and the user identifier or terminal identifier of the second UE. If so, it is determined that the first UE and the second UE have a trust relationship.

[0106] Alternatively, when the trust relationship is one or more user identifiers or terminal identifiers, the third network function may determine whether the user identifier or terminal identifier of the second UE is one of the one or more user identifiers or terminal identifiers, and if so, the second UE is a trusted UE of the first UE.

[0107] In a possible implementation, the first UE may send the trust relationship authentication result to the third network function when the second UE performs relay connection and / or relay communication. For details, please refer to the relevant description in method 200, which will not be repeated here.

[0108] In a possible implementation, the third network function may obtain the trust relationship of the first UE from the second network function. Therefore, in this possible implementation, before sending the trust relationship authentication result to the first UE, the method further includes: sending a trust relationship acquisition request to the second network function, wherein the trust relationship acquisition request carries the identification information of the first UE; and receiving the trust relationship of the first UE returned by the second network function. For details, please refer to the relevant description in the above method 400, which will not be repeated here.

[0109] In another possible implementation, the third network function may also send the trust relationship of the first UE to the access network device corresponding to the first UE, so that the access network device can determine whether the first UE and the second UE are mutually trusted UEs when allocating relay communication resources between the first UE and the second UE, thereby determining whether to agree or reject the resource allocation of the network scheduling mode in the relay communication between the first UE and the second UE.

[0110] Through the trusted relay communication method provided in the embodiment of the present application, the third network function can authenticate the trust relationship between the first UE and the second UE after receiving the trust relationship authentication request sent by the first UE, and return the authentication result to the first UE, so that the first UE can know whether the second UE is a trusted UE, and then determine whether to continue to perform relay connection and / or relay communication with the second UE to ensure the security of relay communication.

[0111] Figure 6 Another flow chart of the trusted relay communication method provided in the embodiment of the present application is shown. The method 600 can be executed by the first access network. In other words, the method can be executed by software or hardware installed on the first access network device. Figure 6 As shown, the method may include the following steps.

[0112] S610: Receive a trust relationship of a first UE sent by a second access network device or a third network function.

[0113] In an embodiment of the present application, the first access network device may receive the trust relationship of the first UE sent by the third network function. For details, please refer to the relevant description in method 500.

[0114] For example, the first access network device receives the trust relationship of the first UE sent by the third network function during the registration process or service request process of the first UE.

[0115] Alternatively, the first access network device may also receive the trust relationship sent by the second access network device. For example, during the switching process of the first UE, the trust relationship sent by the second access device is received, wherein the second access device is the source access device in the switching process, and the first access device is the target access device in the switching process.

[0116] In the embodiment of the present application, the trust relationship of the first UE is the same as the trust relationship of the first UE in the above methods 200 to 500. For details, please refer to the relevant descriptions in the above methods 200 to 500, which will not be repeated here.

[0117] S620: Based on the trust relationship, execute resource scheduling between the first UE and the second UE in the PC5 connection establishment or reject resource scheduling between the first UE and the second UE in the PC5 connection establishment.

[0118] In an embodiment of the present application, the first access network device can determine whether the second UE is a trusted UE of the first UE based on the trust relationship. If so, the resource scheduling established between the first UE and the second UE in the PC5 connection is executed; otherwise, the resource scheduling established between the first UE and the second UE in the PC5 connection is rejected, thereby further ensuring the security of relay communication.

[0119] Figure 7 Another flow chart of the trusted relay communication method provided in the embodiment of the present application is shown. The method 700 can be executed by the first UE, 5G DDNMF, UDM and application server (AF). In other words, the method can be executed by software or hardware installed on the first UE, 5G DDNMF, UDM and application server (AF). Figure 7 As shown, the method may include the following steps.

[0120] S711, the first UE sends a discovery request to the 5G DDNMF, where the discovery request is used to request the network side to provide a relay service code. Optionally, the discovery request can carry 0 to multiple second UE identifiers (user identifiers or terminal identifiers).

[0121] S712, 5G DDNMF sends a binding relationship acquisition request (also called a trust relationship acquisition request) to the UDM and / or application server, where the binding relationship acquisition request is used to obtain the binding relationship (also called a trust relationship) of the first UE, where the binding relationship is a relationship between two or more users.

[0122] Optionally, the binding relationship acquisition request also includes an identifier of the second UE, which is used to indicate a request to obtain an association relationship between the first UE and the second UE.

[0123] S713: UDM provides a binding relationship to 5G DDNMF, and 5G DDNMF generates relationship information based on the binding relationship provided by UDM; or, the application server determines the binding relationship with the first UE based on the service level, and generates relationship information based on the binding relationship.

[0124] Among them, the relationship information may include at least one of the following: a first relay service code, a group key, indication information indicating whether the first UE and the second UE have a binding relationship (for example, if the indication information includes the identifier of the second UE, it indicates that the first UE and the second UE have a binding relationship), or a user identifier or a terminal identifier (the identifier may include one or more, that is, representing one or more users bound to the first UE), authentication information, service type (such as a binding relationship on a specific service), binding slice (binding relationship on a specific slice), binding DNN (binding relationship on a specific DNN), binding PDU session type (binding relationship on a specific PDU session type), etc.

[0125] In a possible implementation, the 5G DDNMF may send the relationship information to each user device having a binding relationship, that is, to each user device having a binding relationship.

[0126] S714, 5G DDNMF or application server sends the first relay service code and / or group key to the first UE.

[0127] Figure 8 Another flow chart of the trusted relay communication method provided in the embodiment of the present application is shown. The method 800 can be executed by the first UE, AMF and UDM. In other words, the method can be executed by software or hardware installed on the first UE, AMF and UDM. Figure 8 As shown, the method may include the following steps.

[0128] S811, the first UE sends a binding relationship authentication request (also called a trust relationship acquisition request) to the AMF, and the binding relationship authentication request carries the identifier of the second UE. The binding relationship authentication request is used to request the AMF to authenticate whether the second UE has a binding relationship with the first UE.

[0129] S812, AMF sends a binding relationship retrieval to UDM, which is used to retrieve the binding relationship of the first UE. The retrieval request message carries the first UE identifier.

[0130] S813: AMF receives the binding relationship provided by UDM.

[0131] S814: AMF determines whether the first UE and the second UE have a binding relationship based on the binding relationship, and sends the determination result to the first UE.

[0132] Fig. 9 Another flow chart of the trusted relay communication method provided in the embodiment of the present application is shown. The method 900 can be executed by the first UE and the second UE. In other words, the method can be executed by software or hardware installed in the first UE and the second UE. Fig. 9 As shown, the method may include the following steps.

[0133] S911, the first UE and the second UE are performing a discovery process or a connection establishment process.

[0134] S912, identification information carried by the first UE in a discovery message or a direct communication request message, where the identification information is used to indicate a trust relationship of the first UE.

[0135] The identification information may include a first relay service code and a group key.

[0136] S913: The second UE selects the first UE based on the identification information and the relationship information sent by the network side.

[0137] The second UE can determine whether the first relay service code sent by the first UE is the same as the second relay service code in the relationship information sent by the network side. If they are the same, the second UE can select the first UE for relay.

[0138] S914, the second UE and the first UE mutually authenticate each other based on the group key to determine whether the other party is a trusted UE.

[0139] Through the above-mentioned trusted relay communication method provided in the embodiment of the present application, the second UE can determine whether the other party is a trusted UE when conducting relay connection and / or relay communication with the first UE, thereby ensuring the security of relay communication.

[0140] It should be noted that the execution subject of the credit relay communication method provided in the embodiment of the present application may be a credit relay communication device, or a control module in the credit relay communication device for executing the credit relay communication method. In the embodiment of the present application, the credit relay communication device provided in the embodiment of the present application is described by taking the execution of the credit relay communication method by the credit relay communication device as an example.

[0141] Fig.10 A schematic diagram of the structure of a credit relay communication device provided in an embodiment of the application is shown. Fig.10 The trusted relay communication device 1000 shown may include: a first receiving module 1001 , a second receiving module 1002 and a communication module 1003 .

[0142] In an embodiment of the present application, the first receiving module 1001 is used to receive relationship information sent by the network side, wherein the relationship information is used to indicate the trust relationship of the first UE; the second receiving module 1002 is used to receive identification information sent by the second UE; the communication module 1003 is used to perform relay connection and / or relay communication with the second UE based on the relationship information and the identification information, or refuse to perform relay connection and / or relay communication with the second UE.

[0143] In a possible implementation, the relationship information includes at least one of the following:

[0144] The first relay service code;

[0145] an association identifier, where the association identifier is used to indicate that the first UE has a trust relationship with the second UE, or the association identifier is used to indicate a terminal identifier or a user identifier of the second UE that has a trust relationship with the first UE;

[0146] The first set of keys;

[0147] Authentication information, the authentication information is used to verify the identification information;

[0148] First business type information;

[0149] First slice information;

[0150] First PDU session type information.

[0151] In a possible implementation, the identification information includes at least one of the following:

[0152] Second relay service code;

[0153] The terminal identifier or user identifier of the second UE;

[0154] Encrypted information or authentication information generated based on the second set of secret keys;

[0155] Verification information, which is the result of performing verification calculation on the specified information to be verified;

[0156] Second business type information;

[0157] Second slice information;

[0158] The second protocol data unit PDU session type information.

[0159] In a possible implementation, the method further includes: a first sending module, wherein:

[0160] The first sending module is configured to send the identification information of the second UE to the network side before the first receiving module 1001 receives the relationship information sent by the network side;

[0161] The first receiving module 1001 receives the relationship information sent by the network side, including: receiving the result returned by the network side for the identification information of the second UE, wherein the result includes the relationship information.

[0162] In a possible implementation, the communication module 1003 is further configured to:

[0163] When performing relay connection and / or relay communication with the second UE, sending a trust relationship authentication request to a third network function, wherein the trust relationship authentication request carries user identification or terminal identification information of the second UE;

[0164] receiving a trust relationship authentication result sent by a third network function;

[0165] Based on the trust relationship authentication result, a relay connection and / or relay communication is performed with the second UE, or the relay connection and / or relay communication is refused to be performed with the second UE.

[0166] The credit relay communication device in the embodiment of the present application can be a device, or a component, integrated circuit, or chip in a terminal. The device can be a mobile terminal or a non-mobile terminal. Exemplarily, the mobile terminal can include but is not limited to the types of terminals 11 listed above, and the non-mobile terminal can be a server, a network attached storage (Network Attached Storage, NAS), a personal computer (personal computer, PC), a television (television, TV), a teller machine or a self-service machine, etc., which is not specifically limited in the embodiment of the present application.

[0167] The credit relay communication device in the embodiment of the present application may be a device having an operating system. The operating system may be an Android operating system, an iOS operating system, or other possible operating systems, which are not specifically limited in the embodiment of the present application.

[0168] The credit relay communication device provided in the embodiment of the present application can achieve Figures 2 to 9 The various processes implemented by the first UE in the method embodiment achieve the same technical effect and are not described again here to avoid repetition.

[0169] Fig.11 Another structural diagram of the credit relay communication device provided in the embodiment of the present application is shown as follows: Fig.11 As shown, the trusted relay communication device 1100 includes: a first acquisition module 1101 and a second sending module 1102 .

[0170] In the embodiment of the present application, the first acquisition module 1101 is used to acquire relationship information, wherein the relationship information is used to indicate the trust relationship of the first UE; the second sending module 1102 is used to send the relationship information.

[0171] In a possible implementation, the relationship information includes at least one of the following:

[0172] The first relay service code;

[0173] an association identifier, where the association identifier is used to indicate that the first UE has a trust relationship with the second UE, or the association identifier is used to indicate a terminal identifier or a user identifier of the second UE that has a trust relationship with the first UE;

[0174] The first set of keys;

[0175] Authentication information, the authentication information is used to verify the identification information;

[0176] First business type information;

[0177] First slice information;

[0178] First PDU session type information.

[0179] In a possible implementation, the method further includes: a third receiving module, wherein:

[0180] The second sending module 1102 is further configured to send a trust relationship acquisition request to a second network function or an application server before sending the relationship information to the first UE, wherein the trust relationship acquisition request carries a user identifier or a terminal identifier of the first UE;

[0181] The third receiving module is used to receive the trust relationship of the first UE returned by the second network function or application server.

[0182] In a possible implementation, the trust relationship is an association relationship between two or more users.

[0183] In one possible implementation, the two or more users are users of one of the following: a specific service, a specific slice, a specific DNN, and a specific PDU session.

[0184] In a possible implementation, the second sending module 1102 sending the relationship information to the first UE includes:

[0185] generating the relationship information based on the trust relationship returned by the second network function, and delivering the relationship information to the first UE; or,

[0186] Forward the trust relationship returned by the application server to the first UE.

[0187] The credit relay communication device provided in the embodiment of the present application can achieve Figures 2 to 9 In the method embodiment, the various processes of implementing the first network function can achieve the same technical effect. To avoid repetition, they will not be described here.

[0188] Fig.12 Another structural diagram of the credit relay communication device provided in the embodiment of the present application is shown as follows: Fig.12 As shown, the trusted relay communication device 1200 may include: a fourth receiving module 1201 and a third sending module 1202 .

[0189] In an embodiment of the present application, the fourth receiving module 1201 is used to receive a first trust relationship acquisition request sent by a first network function, wherein the first trust relationship acquisition request carries a user identifier or a terminal identifier of the first UE; the third sending module 1202 is used to send the trust relationship of the first UE to the first network function.

[0190] In a possible implementation, the trust relationship is an association relationship between two or more users.

[0191] In one possible implementation, the two or more users are users of one of the following: a specific service, a specific slice, a specific DNN, and a specific PDU session.

[0192] In a possible implementation manner, the first trust relationship acquisition request also carries a user identifier or a terminal identifier of the second UE.

[0193] In a possible implementation, the fourth receiving module 1202 is further used to receive a second trust relationship acquisition request of a third network function, wherein the second trust relationship acquisition request carries identification information of the first UE; the third sending module 1202 is further used to send the trust relationship of the first UE to the third network function.

[0194] The credit relay communication device provided in the embodiment of the present application can achieve Figures 2 to 9 The various processes of implementing the second network function in the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0195] Fig.13 Another structural diagram of the credit relay communication device provided in the embodiment of the present application is shown as follows: Fig.13 As shown, the trusted relay communication device 1300 may include: a fifth receiving module 1301 and a fourth sending module 1302 .

[0196] In an embodiment of the present application, the fifth receiving module 1301 is used to receive a trust relationship authentication request sent by the first UE, wherein the trust relationship authentication request carries the user identification or terminal identification information of the second UE; the fourth sending module 1302 is used to send the trust relationship authentication result to the first UE based on the trust relationship of the first UE.

[0197] In one possible implementation, the fourth sending module 1302 is also used to send a trust relationship acquisition request to the second network function before sending the trust relationship authentication result to the first UE, wherein the trust relationship acquisition request carries the identification information of the first UE; the fifth receiving module 1301 is also used to receive the trust relationship of the first UE returned by the second network function.

[0198] In a possible implementation, the fourth sending module 1302 is further configured to send the trust relationship to an access network device corresponding to the first UE.

[0199] The credit relay communication device provided in the embodiment of the present application can achieve Figures 2 to 9 The various processes of implementing the third network function in the method embodiment and achieving the same technical effect are not described here to avoid repetition.

[0200] Fig.14 Another structural diagram of the credit relay communication device provided in the embodiment of the present application is shown as follows: Fig.14 As shown, the trusted relay communication device 1400 may include a sixth receiving module 1401 and an execution module 1402 .

[0201] In an embodiment of the present application, the sixth receiving module 1401 is used to receive the trust relationship of the first UE sent by the second access network device or the third network function; the execution module 1402 is used to execute the resource scheduling established between the first UE and the second UE in the PC5 connection or reject the resource scheduling established between the first UE and the second UE in the PC5 connection based on the trust relationship.

[0202] In a possible implementation, the sixth receiving module 1401 receives the trust relationship of the first UE sent by the second access network device or the third network function, including:

[0203] In a registration process or a service request process of the first UE, receiving the trust relationship sent by the third network function; or,

[0204] During the switching process of the first UE, the trust relationship sent by the second access device is received, wherein the second access device is a source access device in the switching process, and the first access device is a target access device in the switching process.

[0205] The credit relay communication device provided in the embodiment of the present application can achieve Figures 2 to 9 In the method embodiment, the first access network device implements each process and achieves the same technical effect. To avoid repetition, they are not described here.

[0206] Optional, such as Fig.15 As shown, the embodiment of the present application also provides a communication device 1500, including a processor 1501, a memory 1502, and a program or instruction stored in the memory 1502 and executable on the processor 1501. For example, when the communication device 1500 is a terminal, the program or instruction is executed by the processor 1501 to implement the various processes of the above-mentioned credit relay communication method 200 embodiment, and can achieve the same technical effect. When the communication device 1500 is a network side device, the program or instruction is executed by the processor 1501 to implement the various processes of the above-mentioned credit relay communication method 300 to 600 embodiments, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0207] Fig.16 A schematic diagram of the hardware structure of a terminal for implementing an embodiment of the present application.

[0208] The terminal 1600 includes but is not limited to: a radio frequency unit 1601, a network module 1602, an audio output unit 1603, an input unit 1604, a sensor 1605, a display unit 1606, a user input unit 1607, an interface unit 1608, a memory 1609, and a processor 1610 and other components.

[0209] Those skilled in the art will appreciate that the terminal 1600 may also include a power source (such as a battery) for supplying power to each component, and the power source may be logically connected to the processor 1610 through a power management system, thereby implementing functions such as managing charging, discharging, and power consumption management through the power management system. Fig.16 The terminal structure shown in the figure does not constitute a limitation on the terminal. The terminal may include more or fewer components than shown in the figure, or combine certain components, or arrange the components differently, which will not be described in detail here.

[0210] It should be understood that in the embodiment of the present application, the input unit 1604 may include a graphics processor (Graphics Processing Unit, GPU) 16041 and a microphone 16042, and the graphics processor 16041 processes the image data of the static picture or video obtained by the image capture device (such as a camera) in the video capture mode or the image capture mode. The display unit 1606 may include a display panel 16061, and the display panel 16061 may be configured in the form of a liquid crystal display, an organic light emitting diode, etc. The user input unit 1607 includes a touch panel 16071 and other input devices 16072. The touch panel 16071 is also called a touch screen. The touch panel 16071 may include two parts: a touch detection device and a touch controller. Other input devices 16072 may include, but are not limited to, a physical keyboard, function keys (such as volume control keys, switch keys, etc.), a trackball, a mouse, and a joystick, which will not be repeated here.

[0211] In the embodiment of the present application, the radio frequency unit 1601 receives downlink data from the network side device and sends it to the processor 1610 for processing; in addition, the uplink data is sent to the network side device. Generally, the radio frequency unit 1601 includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, etc.

[0212] The memory 1609 can be used to store software programs or instructions and various data. The memory 1609 can mainly include a program or instruction storage area and a data storage area, wherein the program or instruction storage area can store an operating system, an application program or instruction required for at least one function (such as a sound playback function, an image playback function, etc.), etc. In addition, the memory 1609 can include a high-speed random access memory, and can also include a non-volatile memory, wherein the non-volatile memory can be a read-only memory (Read-Only Memory, ROM), a programmable read-only memory (Programmable ROM, PROM), an erasable programmable read-only memory (Erasable PROM, EPROM), an electrically erasable programmable read-only memory (Electrically EPROM, EEPROM) or a flash memory. For example, at least one disk storage device, a flash memory device, or other non-volatile solid-state storage device.

[0213] The processor 1610 may include one or more processing units; optionally, the processor 1610 may integrate an application processor and a modem processor, wherein the application processor mainly processes an operating system, a user interface, and application programs or instructions, and the modem processor mainly processes wireless communications, such as a baseband processor. It is understandable that the modem processor may not be integrated into the processor 1610.

[0214] The radio frequency unit 1601 is configured to receive relationship information sent by the network side, wherein the relationship information is used to indicate the trust relationship of the first UE; and receive identification information sent by the second UE;

[0215] Processor 1610 is configured to perform a relay connection and / or relay communication with the second UE based on the relationship information and the identification information, or refuse to perform a relay connection and / or relay communication with the second UE.

[0216] Specifically, the embodiment of the present application also provides a network side device. Fig.17 As shown, the network device 1700 includes: an antenna 1701, a radio frequency device 1702, and a baseband device 1703. The antenna 1701 is connected to the radio frequency device 1702. In the uplink direction, the radio frequency device 1702 receives information through the antenna 1701 and sends the received information to the baseband device 1703 for processing. In the downlink direction, the baseband device 1703 processes the information to be sent and sends it to the radio frequency device 1702, and the radio frequency device 1702 processes the received information and sends it out through the antenna 1701.

[0217] The frequency band processing device may be located in the baseband device 1703 . The method performed by the network-side device in the above embodiment may be implemented in the baseband device 1703 . The baseband device 1703 includes a processor 1704 and a memory 1705 .

[0218] The baseband device 1703 may include, for example, at least one baseband board on which a plurality of chips are arranged. Fig.17 As shown, one of the chips is, for example, a processor 1704, which is connected to a memory 1705 to call a program in the memory 1705 to execute the network device operations shown in the above method embodiment.

[0219] The baseband device 1703 may further include a network interface 1706 for exchanging information with the radio frequency device 1702 . The interface may be, for example, a common public radio interface (CPRI).

[0220] Specifically, the network side device of the embodiment of the present invention further includes: instructions or programs stored in the memory 1705 and executable on the processor 1704, and the processor 1704 calls the instructions or programs in the memory 1705 to execute Figures 11 to 14 The methods executed by the modules shown achieve the same technical effects, and therefore will not be described here in detail to avoid repetition.

[0221] An embodiment of the present application also provides a readable storage medium, on which a program or instruction is stored. When the program or instruction is executed by a processor, each process of the above-mentioned credit relay communication method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be repeated here.

[0222] The processor is the processor in the terminal described in the above embodiment. The readable storage medium includes a computer readable storage medium, such as a computer read-only memory (ROM), a random access memory (RAM), a magnetic disk or an optical disk.

[0223] An embodiment of the present application further provides a chip, which includes a processor and a communication interface, wherein the communication interface is coupled to the processor, and the processor is used to run network-side device programs or instructions to implement the various processes of the above-mentioned credit relay communication method embodiment, and can achieve the same technical effect. To avoid repetition, it will not be repeated here.

[0224] A computer program product is provided, which includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor. When the program or instruction is executed by the processor, each process of the above-mentioned credit relay communication method embodiment is implemented, and the same technical effect can be achieved. To avoid repetition, it will not be described here.

[0225] It should be understood that the chip mentioned in the embodiments of the present application can also be called a system-level chip, a system chip, a chip system or a system-on-chip chip, etc.

[0226] It should be noted that, in this article, the terms "comprise", "include" or any other variant thereof are intended to cover non-exclusive inclusion, so that the process, method, article or device including a series of elements includes not only those elements, but also includes other elements not explicitly listed, or also includes elements inherent to such process, method, article or device. In the absence of further restrictions, the elements defined by the sentence "comprise one..." do not exclude the presence of other identical elements in the process, method, article or device including the element. In addition, it should be pointed out that the scope of the methods and devices in the embodiments of the present application is not limited to performing functions in the order shown or discussed, and may also include performing functions in a substantially simultaneous manner or in reverse order according to the functions involved, for example, the described method may be performed in an order different from that described, and various steps may also be added, omitted, or combined. In addition, the features described with reference to certain examples may be combined in other examples.

[0227] Through the description of the above implementation methods, those skilled in the art can clearly understand that the above-mentioned embodiment methods can be implemented by means of software plus a necessary general hardware platform, and of course by hardware, but in many cases the former is a better implementation method. Based on such an understanding, the technical solution of the present application, or the part that contributes to the prior art, can be embodied in the form of a software product, which is stored in a storage medium (such as ROM / RAM, a disk, or an optical disk), and includes a number of instructions for a terminal (which can be a mobile phone, a computer, a server, or a network device, etc.) to execute the methods described in each embodiment of the present application.

[0228] The embodiments of the present application are described above in conjunction with the accompanying drawings, but the present application is not limited to the above-mentioned specific implementation methods. The above-mentioned specific implementation methods are merely illustrative and not restrictive. Under the guidance of the present application, ordinary technicians in this field can also make many forms without departing from the purpose of the present application and the scope of protection of the claims, all of which are within the protection of the present application.

Claims

1. A trusted relay communication method, It is characterized in that Applied to a first terminal UE, comprising: Receiving relationship information sent by a network side, wherein the relationship information is used to indicate a trust relationship of the first UE, and the relationship information is used to determine a trusted UE of the first UE; Receive identification information sent by the second UE, and based on the relationship information and the identification information, perform relay connection and / or relay communication with the second UE, or refuse to perform relay connection and / or relay communication with the second UE, wherein the second UE is a relay terminal.

2. The method according to claim 1, It is characterized in that The relationship information includes at least one of the following: First relay service code; an association identifier, where the association identifier is used to indicate that the first UE has a trust relationship with the second UE, or the association identifier is used to indicate a terminal identifier or a user identifier of the second UE that has a trust relationship with the first UE; The first set of keys; Authentication information, the authentication information is used to verify the identification information; First business type information; First slice information; The first protocol data unit PDU session type information.

3. The method according to claim 1, It is characterized in that The identification information includes at least one of the following: Second relay service code; The terminal identifier or user identifier of the second UE; Encrypted information or authentication information generated based on the second set of secret keys; Verification information, which is the result of performing verification calculation on the specified information to be verified; Second business type information; Second slice information; The second protocol data unit PDU session type information.

4. The method according to claim 1, It is characterized in that Before receiving the relationship information sent by the network side, the method further includes: sending identification information of the second UE to the network side; Receiving the relationship information sent by the network side includes: receiving a result returned by the network side for the identification information of the second UE, wherein the result includes the relationship information.

5. The method according to any one of claims 1 to 4, It is characterized in that The method further comprises: When performing relay connection and / or relay communication with the second UE, sending a trust relationship authentication request to a third network function, wherein the trust relationship authentication request carries user identification or terminal identification information of the second UE; receiving a trust relationship authentication result sent by a third network function; Based on the trust relationship authentication result, a relay connection and / or relay communication is performed with the second UE, or the relay connection and / or relay communication is refused to be performed with the second UE.

6. A trusted relay communication method, It is characterized in that Applied to the first network function, including: Sending relationship information to a first UE, so that the first UE determines a trusted UE according to the relationship information, wherein the relationship information is used to indicate a trust relationship of the first UE; Before sending the relationship information to the first UE, the method further includes: Sending a trust relationship acquisition request to a second network function or application server, wherein the trust relationship acquisition request carries a user identifier or a terminal identifier of the first UE; Receive the trust relationship of the first UE returned by the second network function or application server.

7. The method according to claim 6, It is characterized in that The relationship information includes at least one of the following: First relay service code; An association identifier, where the association identifier is used to indicate that the first UE has a trust relationship with the second UE, or the association identifier is used to indicate a terminal identifier or a user identifier of the second UE that has a trust relationship with the first UE; The first set of keys; Authentication information, the authentication information is used to verify the identification information; First business type information; First slice information; The first protocol data unit PDU session type information.

8. The method according to claim 6, It is characterized in that The trust relationship is an association relationship between two or more users.

9. The method according to claim 8, It is characterized in that The two or more users are users of one of the following: a specific service, a specific slice, a specific data network name DNN, and a specific PDU session.

10. The method according to claim 6, It is characterized in that Sending relationship information to the first UE includes: generating the relationship information based on the trust relationship returned by the second network function, and delivering the relationship information to the first UE; or, Forward the relationship information returned by the application server to the first UE.

11. A trusted relay communication method, It is characterized in that Applicable to the second network function, including: Receiving a first trust relationship acquisition request sent by a first network function, wherein the first trust relationship acquisition request carries a user identifier or a terminal identifier of the first UE; The trust relationship of the first UE is sent to the first network function, so that the first network function obtains and sends relationship information to the first UE based on the trust relationship of the first UE, so that the first UE determines the trusted UE of the first UE according to the relationship information.

12. The method according to claim 11, It is characterized in that The trust relationship is an association relationship between two or more users.

13. The method according to claim 12, It is characterized in that The two or more users are users of one of the following: a specific service, a specific slice, a specific DNN, and a specific PDU session.

14. The method according to claim 11, It is characterized in that The first trust relationship acquisition request also carries a user identifier or a terminal identifier of the second UE.

15. The method according to claim 11, It is characterized in that The method further comprises: receiving a second trust relationship acquisition request from a third network function, wherein the second trust relationship acquisition request carries identification information of the first UE; Sending the trust relationship of the first UE to the third network function.

16. A trusted relay communication method, It is characterized in that Applicable to third network functions, including: Receiving a trust relationship authentication request sent by the first UE, wherein the trust relationship authentication request carries user identification or terminal identification information of the second UE; Based on the trust relationship of the first UE, sending a trust relationship authentication result to the first UE; Before sending the trust relationship authentication result to the first UE, the method further includes: Sending a trust relationship acquisition request to the second network function, wherein the trust relationship acquisition request carries identification information of the first UE; Receive the trust relationship of the first UE returned by the second network function.

17. The method according to claim 16, It is characterized in that Also includes: The trust relationship is sent to an access network device corresponding to the first UE.

18. A trusted relay communication method, It is characterized in that Applicable to the first access network device, including: Receiving a trust relationship of the first UE sent by the second access network device or the third network function; Based on the trust relationship, resource scheduling between the first UE and the second UE in the PC5 connection establishment is performed or resource scheduling between the first UE and the second UE in the PC5 connection establishment is rejected.

19. The method according to claim 18, It is characterized in that Receiving the trust relationship of the first UE sent by the second access network device or the third network function includes: In a registration process or a service request process of the first UE, receiving the trust relationship sent by the third network function entity; or, During the switching process of the first UE, the trust relationship sent by the second access device is received, wherein the second access device is a source access device in the switching process, and the first access device is a target access device in the switching process.

20. A trusted relay communication device, applied to a first UE, It is characterized in that include: A first receiving module, configured to receive relationship information sent by a network side, wherein the relationship information is used to indicate a trust relationship of the first UE, and the relationship information is used to determine a trusted UE of the first UE; A second receiving module, configured to receive identification information sent by a second UE, wherein the second UE is a relay terminal; A communication module is used to perform a relay connection and / or relay communication with the second UE based on the relationship information and the identification information, or refuse to perform a relay connection and / or relay communication with the second UE.

21. The device according to claim 20, It is characterized in that The relationship information includes at least one of the following: First relay service code; an association identifier, where the association identifier is used to indicate that the first UE has a trust relationship with the second UE, or the association identifier is used to indicate a terminal identifier or a user identifier of the second UE that has a trust relationship with the first UE; The first set of keys; Authentication information, the authentication information is used to verify the identification information; First business type information; First slice information; The first protocol data unit PDU session type information.

22. The device according to claim 20, It is characterized in that The identification information includes at least one of the following: Second relay service code; The terminal identifier or user identifier of the second UE; Encrypted information or authentication information generated based on the second set of secret keys; Verification information, which is the result of performing verification calculation on the specified information to be verified; Second business type information; Second slice information; The second protocol data unit PDU session type information.

23. The device according to claim 20, It is characterized in that Also includes: The first sending module, wherein The first sending module is configured to send the identification information of the second UE to the network side before the first receiving module receives the relationship information sent by the network side; The first receiving module receives the relationship information sent by the network side, including: receiving a result returned by the network side for the identification information of the second UE, wherein the result includes the relationship information.

24. The device according to any one of claims 20 to 23, It is characterized in that The communication module is also used for: When performing relay connection and / or relay communication with the second UE, sending a trust relationship authentication request to a third network function, wherein the trust relationship authentication request carries user identification or terminal identification information of the second UE; receiving a trust relationship authentication result sent by a third network function; Based on the trust relationship authentication result, a relay connection and / or relay communication is performed with the second UE, or the relay connection and / or relay communication is refused to be performed with the second UE.

25. A trusted relay communication device, applied to a first network function, It is characterized in that include: A first acquisition module, configured to acquire relationship information so that the first UE determines a trusted UE according to the relationship information, wherein the relationship information is used to indicate a trust relationship of the first UE; A second sending module is configured to send the relationship information; before sending the relationship information to the first UE, send a trust relationship acquisition request to a second network function or an application server, wherein the trust relationship acquisition request carries a user identifier or a terminal identifier of the first UE; The third receiving module is used to receive the trust relationship of the first UE returned by the second network function or application server.

26. The device of claim 25, It is characterized in that The relationship information includes at least one of the following: First relay service code; An association identifier, where the association identifier is used to indicate that the first UE has a trust relationship with the second UE, or the association identifier is used to indicate a terminal identifier or a user identifier of the second UE that has a trust relationship with the first UE; The first set of keys; Authentication information, the authentication information is used to verify the identification information; First business type information; First slice information; The first protocol data unit PDU session type information.

27. The device according to claim 25, It is characterized in that The trust relationship is an association relationship between two or more users.

28. The device according to claim 27, It is characterized in that The two or more users are users of one of the following: a specific service, a specific slice, a specific DNN, and a specific PDU session.

29. The device according to claim 25, It is characterized in that The second sending module sending the relationship information to the first UE includes: generating the relationship information based on the trust relationship returned by the second network function, and delivering the relationship information to the first UE; or, Forward the trust relationship returned by the application server to the first UE.

30. A trusted relay communication device, It is characterized in that include: A fourth receiving module, configured to receive a first trust relationship acquisition request sent by the first network function, wherein the first trust relationship acquisition request carries a user identifier or a terminal identifier of the first UE; The third sending module is used to send the trust relationship of the first UE to the first network function, so that the first network function obtains and sends relationship information to the first UE based on the trust relationship of the first UE, so that the first UE determines the trusted UE according to the relationship information.

31. The device according to claim 30, It is characterized in that The trust relationship is an association relationship between two or more users.

32. The device according to claim 31, It is characterized in that The two or more users are users of one of the following: a specific service, a specific slice, a specific DNN, and a specific PDU session.

33. The device according to claim 30, It is characterized in that The first trust relationship acquisition request also carries a user identifier or a terminal identifier of the second UE.

34. The device according to claim 30, It is characterized in that The fourth receiving module is further configured to receive a second trust relationship acquisition request from a third network function, wherein the second trust relationship acquisition request carries identification information of the first UE; The third sending module is further used to send the trust relationship of the first UE to a third network function.

35. A trusted relay communication device, It is characterized in that include: A fifth receiving module, configured to receive a trust relationship authentication request sent by the first UE, wherein the trust relationship authentication request carries a user identification or terminal identification information of the second UE; a fourth sending module, configured to send a trust relationship authentication result to the first UE based on the trust relationship of the first UE; before sending the trust relationship authentication result to the first UE, send a trust relationship acquisition request to the second network function, wherein the trust relationship acquisition request carries identification information of the first UE; The fifth receiving module is further used to receive the trust relationship of the first UE returned by the second network function.

36. The device according to claim 35, It is characterized in that The fourth sending module is further configured to send the trust relationship to an access network device corresponding to the first UE.

37. A trusted relay communication device, applied to a first access network device, It is characterized in that include: A sixth receiving module, configured to receive a trust relationship of the first UE sent by the second access network device or the third network function; An execution module is used to execute resource scheduling established between the first UE and the second UE in the PC5 connection or reject resource scheduling established between the first UE and the second UE in the PC5 connection based on the trust relationship.

38. The device according to claim 37, It is characterized in that The sixth receiving module receives the trust relationship of the first UE sent by the second access network device or the third network function, including: In a registration process or a service request process of the first UE, receiving the trust relationship sent by the third network function; or, During the switching process of the first UE, the trust relationship sent by the second access device is received, wherein the second access device is a source access device in the switching process, and the first access device is a target access device in the switching process.

39. A terminal, It is characterized in that It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the trusted relay communication method as described in any one of claims 1 to 5.

40. A network side device, It is characterized in that It includes a processor, a memory, and a program or instruction stored in the memory and executable on the processor, wherein the program or instruction, when executed by the processor, implements the steps of the credit relay communication method as described in any one of claims 5 to 10, or implements the steps of the credit relay communication method as described in any one of claims 11 to 14, or implements the steps of the credit relay communication method as described in any one of claims 15 to 17, or implements the steps of the credit relay communication method as described in claim 18 or 19.

41. A readable storage medium, It is characterized in that The readable storage medium stores programs or instructions, and when the programs or instructions are executed by the processor, they implement the steps of the trusted relay communication method as described in any one of claims 1 to 5, or implement the steps of the trusted relay communication method as described in any one of claims 5 to 10, or implement the steps of the trusted relay communication method as described in any one of claims 11 to 14, or implement the steps of the trusted relay communication method as described in any one of claims 15 to 17, or implement the steps of the trusted relay communication method as described in claim 18 or 19.