Patent Application
20250142446
This application pertains to the field of communication technologies, and specifically relates to an identity configuration method and apparatus, a terminal, and a storage medium.
Some communication systems support terminal (User Equipment, UE) to terminal (UE-to-UE, U2U) relay (Relay) communication. Currently, in a U2U relay link, a layer-2 identity (Layer-2 IDentity, L2 ID) is mainly used to identify a terminal. The L2 ID is a global identity and is specifically 24 bits. Therefore, transmission overheads of the terminal are excessively high due to the large L2 ID of the terminal.
Embodiments of this application provide an identity configuration method and apparatus, a terminal, and a storage medium.
According to a first aspect, an identity configuration method is provided and includes:
According to a second aspect, an identity configuration method is provided and includes:
According to a third aspect, an identity configuration apparatus is provided and includes:
According to a fourth aspect, an identity configuration apparatus is provided and includes:
According to a fifth aspect, a terminal is provided. The terminal is a first terminal and includes a processor and a memory. The memory stores a program or instructions capable of running on the processor. When the program or instructions are executed by the processor, the steps of the identity configuration method on the first terminal side according to the embodiments of this application are implemented.
According to a sixth aspect, a terminal is provided and includes a processor and a communication interface. The communication interface is configured to: send a first message, where the first message is used to configure a local identity of a second terminal, and the local identity is used to uniquely identify the terminal in a U2U relay link, where the U2U relay link includes a source terminal, a target terminal, and a relay terminal, and the second terminal is the source terminal or the target terminal; and receive a second message, where the second message is a response message to the first message.
According to a seventh aspect, a terminal is provided. The terminal is a fourth terminal and includes a processor and a memory. The memory stores a program or instructions capable of running on the processor. When the program or instructions are executed by the processor, the steps of the identity configuration method on the fourth terminal side according to the embodiments of this application are implemented.
According to an eighth aspect, a terminal is provided and includes a processor and a communication interface. The communication interface is configured to: receive a first message sent by a first terminal, where the first message is used to configure a local identity of a second terminal, and the local identity is used to uniquely identify the terminal in a U2U relay link, where the U2U relay link includes a source terminal, a target terminal, and a relay terminal, and the second terminal is the source terminal or the target terminal; and send a second message to the first terminal, where the second message is a response message to the first message.
According to a ninth aspect, a readable storage medium is provided. The readable storage medium stores a program or instructions. When the program or instructions are executed by a processor, the steps of the identity configuration method on the first terminal side according to the embodiments of this application are implemented, or when the program or instructions are executed by a processor, the steps of the identity configuration method on the fourth terminal side according to the embodiments of this application are implemented.
According to a tenth aspect, a chip is provided. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a program or instructions to implement the identity configuration method on the first terminal side according to the embodiments of this application, or the processor is configured to run a program or instructions to implement the identity configuration method on the fourth terminal side according to the embodiments of this application.
According to an eleventh aspect, a computer program or program product is provided. The computer program or program product is stored in a storage medium. The computer program or program product is executed by at least one processor to implement the steps of the identity configuration method on the first terminal side according to the embodiments of this application, or the computer program or program product is executed by at least one processor to implement the steps of the identity configuration method on the fourth terminal side according to the embodiments of this application.
According to a twelfth aspect, an identity configuration system is provided and includes a first terminal and a fourth terminal. The first terminal may be configured to perform the steps of the identity configuration method on the first terminal side according to the embodiments of this application. The fourth terminal may be configured to perform the steps of the identity configuration method on the fourth terminal side according to the embodiments of this application.
In the embodiments of this application, the first terminal sends the first message, where the first message is used to configure the local identity of the second terminal, and the local identity is used to uniquely identify the terminal in the U2U relay link, where the U2U relay link includes the source terminal, the target terminal, and the relay terminal, and the second terminal is the source terminal or the target terminal; and the first terminal receives the second message, where the second message is the response message to the first message. In this way, the local identity can be configured for the second terminal. The local identity uniquely identifies the terminal in the U2U relay link. Compared with a global L2 ID, the local identity has fewer bits.
The following clearly describes the technical solutions in the embodiments of this application with reference to the accompanying drawings in the embodiments of this application. Apparently, the described embodiments are only some rather than all of the embodiments of this application. All other embodiments obtained by a person of ordinary skill in the art based on the embodiments of this application shall fall within the protection scope of this application.
The terms “first”, “second”, and the like in this specification and claims of this application are used to distinguish between similar objects instead of describing a specified order or sequence. It should be understood that the terms used in this way are interchangeable in appropriate circumstances, so that the embodiments of this application can be implemented in other orders than the order illustrated or described herein. In addition, objects distinguished by “first” and “second” usually fall within one class, and a quantity of objects is not limited. For example, there may be one or more first objects. In addition, the term “and/or” in the specification and claims indicates at least one of connected objects, and the character “/” generally represents an “or” relationship between associated objects.
It should be noted that technologies described in the embodiments of this application are not limited to a long term evolution (Long Term Evolution, LTE)/LTE-Advanced (LTE-Advanced, LTE-A) system, and can also be used in other wireless communication systems, such as code division multiple access (Code Division Multiple Access, CDMA), time division multiple access (Time Division Multiple Access, TDMA), frequency division multiple access (Frequency Division Multiple Access, FDMA), orthogonal frequency division multiple access (Orthogonal Frequency Division Multiple Access, OFDMA), single-carrier frequency-division multiple access (Single-carrier Frequency-Division Multiple Access, SC-FDMA), and other systems. The terms “system” and “network” in the embodiments of this application are usually used interchangeably. The described technologies may be used for the foregoing systems and radio technologies, and may also be used for other systems and radio technologies. However, in the following descriptions, the new radio (New Radio, NR) system is described for an illustrative purpose, and NR terms are used in most of the following descriptions. These technologies may also be applied to other applications than an NR system application, for example, a 6th Generation (6th Generation, 6G) communication system.
The present application aims to resolve a problem that transmission overheads of a terminal are excessively high due to a large L2 ID of the terminal.
Embodiments of the present application provide an identity configuration method and apparatus, a terminal, and a storage medium to reduce the transmission overheads of the terminal.
As shown in
In some embodiments, the source UE may also be referred to as remote terminal (Remote UE), and the target UE may also be referred to as destination terminal (Destination UE).
In some embodiments, a U2U relay protocol stack may be shown in
An identity configuration method and apparatus, a terminal, and a storage medium provided in embodiments of this application are hereinafter described in detail by using some embodiments and application scenarios thereof with reference to the accompanying drawings.
Step 401: A first terminal sends a first message, where the first message is used to configure a local identity (local ID) of a second terminal, and the local identity is used to uniquely identify the terminal in a U2U relay link, where the U2U relay link includes a source terminal, a target terminal, and a relay terminal, and the second terminal is the source terminal or the target terminal.
The first terminal may send the first message to the second terminal, or the first terminal may send the first message to the relay terminal.
The first terminal may be the source terminal or the target terminal, or the first terminal may be the relay terminal.
The local identity of the second terminal may be allocated by the first terminal.
That the local identity is used to uniquely identify the terminal in a U2U relay link may be understood as: the local identity may be used to identify uniqueness of the terminal in the U2U relay link, that is, the terminal may be identified in the U2U relay link by using the local identity, for example, the second terminal may be identified in the U2U relay link by using the local identity of the second terminal.
In addition, in this embodiment of this application, the U2U relay link may be a U2U relay link shown in
Step 402: The first terminal receives a second message, where the second message is a response message to the first message.
The second message may be a response message returned to the first terminal by a terminal that receives the first message, for example, used to indicate whether the first message is sent successfully or indicate whether the local identity of the second terminal is configured successfully.
In this embodiment of this application, the local identity can be configured for the second terminal through the foregoing steps. The local identity uniquely identifies the terminal in the U2U relay link, that is, the local identity needs to uniquely identify the terminal only in the U2U relay link. Compared with a global L2 ID, the local identity has fewer bits. Therefore, transmission overheads of the terminal can be reduced. For example, in some implementations, the local identity may use 8 or 4 bits.
In an optional implementation, the first message is an HbH PC5 radio resource control (Radio Resource Control, RRC) message, such as a sidelink RRC reconfiguration (RRCReconfigurationSidelink) message; and the second message is an HbH PC5 RRC message, such as an RRCReconfigurationCompleteSidelink message or a sidelink RRC reconfiguration failure (RRCReconfigurationFailureSidelink) message. In this implementation, the local identity can be configured by using the HbH PC5 RRC message. Therefore, the local identity can be configured without the need to define new messages, and complexity of standards can be reduced.
In some implementations, the first message and the second message may alternatively be of message types newly defined in this embodiment of this application. This is not limited.
In an optional implementation, the first message includes at least one of the following: a layer-2 identity (L2 ID) of the second terminal; and the local identity of the second terminal.
In a case that the first message includes only the layer-2 identity of the second terminal, the layer-2 identity is used to indicate that the local identity of the second terminal is a default local identity, or indicate that the local identity of the second terminal is a pre-agreed local identity.
In an optional implementation, before the first terminal sends the first message, the method further includes:
In this implementation, the first terminal is the source terminal or the target terminal.
In this implementation, the layer-2 identity of the second terminal may enable the first terminal to allocate the local identity to the second terminal by referring to the layer-2 identity; and the local identity already allocated, the local identity not allocated, and the local identity recommended for allocation may enable the first terminal to better configure the local identity of the second terminal, for example, to avoid configuring the local identity already allocated, or to configure the local identity recommended for allocation.
In an optional implementation, the third message is an HbH PC5 radio resource control (Radio Resource Control, RRC) message, such as a sidelink terminal assistance information (UEAssistanceInformationSidelink) message, a sidelink notification message (NotificationMessageSidelink) message, or a sidelink remote terminal information (RemoteUEInformationSidelink) message. In some implementations, the third message may alternatively be of a message type newly defined in this embodiment of this application. This is not limited.
In an optional implementation, the first terminal is the source terminal, the second terminal is the target terminal, the first message is a first message sent by the first terminal to the relay terminal, and the second message is a second message sent by the relay terminal and received by the first terminal; or
In this implementation, the source terminal can allocate a local identity to the target terminal, and the target terminal can allocate a local identity to the source terminal and send the allocated local identity to the relay terminal, so that the relay terminal can perform relay communication based on the local identities of the source terminal and the target terminal.
Optionally, the second message or a third message includes a local identity of the first terminal, and the third message is a message sent by the relay terminal and received by the first terminal.
In this way, the first terminal can obtain the local identity of the first terminal by using the second message or the third message, to reduce the transmission overheads.
Optionally, the method further includes:
In this way, the local identity of the first terminal can be obtained by using the fourth message.
In an optional implementation, the fourth message is an HbH PC5 radio resource control (Radio Resource Control, RRC) message, such as a UEAssistanceInformationSidelink message, a NotificationMessageSidelink message, or a RemoteUEInformationSidelink message. In some implementations, the fourth message may alternatively be of a message type newly defined in this embodiment of this application. This is not limited.
By using examples and referring to
In an embodiment, based on a signaling flow in which peer UE (peer UE) allocates a local ID, in this embodiment, target UE is responsible for allocating a local ID value used by source UE (hereinafter referred to as procedure A for simplicity of description), and source UE is responsible for allocating a local ID value used by target UE (hereinafter referred to as procedure B for simplicity of description). In addition, based on an implementation of HbH PC5 RRC message exchange, initiation of procedure A and procedure B (timing of a first message) is not sequential. As shown in
It should be noted that procedure A and procedure B may be completed simultaneously or sequentially.
In an embodiment, as shown in
Step 0a (optional): The relay UE sends a first HbH PC5 RRC message to the target UE to request the target UE to allocate a local ID to the source UE, where the HbH PC5 RRC message may carry at least one of the following content:
Step 1a: The target UE sends a second HbH PC5 RRC message to the relay UE to configure the local ID value of the source UE, where the HbH PC5 RRC message may carry at least one of the following content:
Step 2a: The relay UE sends a third HbH PC5 RRC message to the target UE to indicate that the configuration in step 1a is completed or fails.
Based on a result in step 2a, if it is determined that the configuration is completed, it is considered that the procedure for allocating the local ID of the source UE is completed; or if it is determined that the configuration fails, one of the following operations may be performed:
Step 0b (optional): The relay UE sends a fourth HbH PC5 RRC message to the source UE to request the source UE to allocate a local ID to the target UE, where the HbH PC5 RRC message may carry at least one of the following content:
Step 1b: The source UE sends a fifth HbH PC5 RRC message to the relay UE to configure the local ID value of the target UE, where the HbH PC5 RRC message may carry at least one of the following content:
Step 2b: The relay UE sends a sixth HbH PC5 RRC message to the source UE to indicate that the configuration in step 1b is completed or fails.
Based on a result in step 2b, if it is determined that the configuration is completed, it is considered that the procedure for allocating the local ID of the target UE is completed; or if it is determined that the configuration fails, one of the following operations may be performed:
After the configuration in step 2a is completed, the relay UE may further send the local ID value of the source UE to the source UE. A specific manner includes one of the following:
After step 2b (for example, step 3b, not shown in the figure), an HbH PC5 RRC message is used for sending, and a message type thereof is the same as that in step 0b or 1b.
After the configuration in step 2b is completed, the relay UE may further send the local ID value of the target UE to the target UE. A specific manner includes one of the following:
After step 2b (for example, step 3a, not shown in the figure), an HbH PC5 RRC message is used for sending, and a message type thereof is the same as that in step 0a or 1a.
In an embodiment, as shown in
Step 0b (optional): The relay UE sends a fourth HbH PC5 RRC message to the source UE to request the source UE to allocate a local ID to the target UE, where the HbH PC5 RRC message may carry at least one of the following content:
Step 1b: The source UE sends a fifth HbH PC5 RRC message to the relay UE to configure the local ID value of the target UE, where the HbH PC5 RRC message may carry at least one of the following content:
Step 2b: The relay UE sends a sixth HbH PC5 RRC message to the source UE to indicate that the configuration in step 1b is completed or fails.
Based on a result in step 2b, if it is determined that the configuration is completed, it is considered that the procedure for allocating the local ID of the target UE is completed; or if it is determined that the configuration fails, one of the following operations may be performed:
Step 0a (optional): The relay UE sends a first HbH PC5 RRC message to the target UE to request the target UE to allocate a local ID to the source UE, where the HbH PC5 RRC message may carry at least one of the following content:
Step 1a: The target UE sends a second HbH PC5 RRC message to the relay UE to configure the local ID value of the source UE, where the HbH PC5 RRC message may carry at least one of the following content:
Step 2a: The relay UE sends a third HbH PC5 RRC message to the target UE to indicate that the configuration in step 1a is completed or fails. Based on a result in step 2a, if it is determined that the configuration is completed, it is considered that the procedure for allocating the local ID of the source UE is completed; or if it is determined that the configuration fails, one of the following operations may be performed:
After the configuration in step 2a is completed, the relay UE may further send the local ID value of the source UE to the source UE. A specific manner includes one of the following:
After step 2b (for example, step 3b, not shown in the figure), an HbH PC5 RRC message is used for sending, and a message type thereof is the same as that in step 0b or 1b.
After step 2b is completed, the relay UE may further send the local ID value of the target UE to the target UE. A specific manner includes one of the following:
After step 2a (for example, step 3a, not shown in the figure), an HbH PC5 RRC message is used for sending, and a message type thereof is the same as that in step 0a or 1a.
In an optional implementation, the first terminal is the relay terminal, the first message is a message sent by the first terminal to the second terminal, and the second message is a message sent by the second terminal and received by the first terminal.
In this implementation, the relay terminal can configure a local identity for the second terminal, and can specifically configure a local identity for at least one of the source terminal and the target terminal. For example, the method further includes:
In this implementation, the relay terminal can configure the local identities of the second terminal and the third terminal, that is, local matching of both the source terminal and the target terminal is configured by the relay terminal.
In an optional implementation, the fifth message is an HbH PC5 radio resource control (Radio Resource Control, RRC) message, such as an RRCReconfigurationSidelink message, and the sixth message is an HbH PC5 RRC message, such as an RRCReconfigurationCompleteSidelink message or an RRCReconfigurationFailureSidelink message. In this implementation, the local identity can be configured by using the HbH PC5 RRC message. Therefore, the local identity can be configured without the need to define new messages, and complexity of standards can be reduced.
In some implementations, the fifth message and the sixth message may alternatively be of message types newly defined in this embodiment of this application. This is not limited.
Optionally, the first message is used to configure the local identity of the second terminal, or the first message is used to configure the local identities of the second terminal and the third terminal;
In this implementation, a local identity of the source terminal or the target terminal can be configured by using the first message, or local identities of the source terminal and the target terminal can be configured by using the first message; and the local identity of the source terminal or the target terminal can be configured by using the fifth message, or the local identities of the source terminal and the target terminal can be configured by using the fifth message.
For example, the first message may include at least one of the following:
The layer-2 identity of the second terminal included in the first message may be used to indicate that the local identity of the second terminal is a default local identity, or indicate that the local identity of the second terminal is a pre-agreed local identity.
For example, the fifth message may include at least one of the following:
The layer-2 identity of the third terminal included in the fifth message may be used to indicate that the local identity of the third terminal is a default local identity, or indicate that the local identity of the third terminal is a pre-agreed local identity.
In an embodiment, on a basis that relay UE allocates a local ID, in this embodiment, the relay UE is responsible for allocating a local ID value used by source UE (hereinafter referred to as procedure A for simplicity of description), and is responsible for allocating a local ID value used by target UE (hereinafter referred to as procedure B for simplicity of description). Based on an implementation of HbH PC5 RRC message exchange, specifically as shown in
Step 1a: The relay UE sends a first HbH PC5 RRC message to the target UE to configure the local ID value(s) of the source UE and/or the target UE, where the HbH PC5 RRC message may carry at least one of the following content:
Step 2a: The target UE sends a second HbH PC5 RRC message to the relay UE to indicate that the configuration in step 1a is completed or fails.
Based on a result in step 2a, if it is determined that the configuration is completed, it is considered that the procedure for allocating the local ID(s) of the source UE and/or the target UE is completed; or if it is determined that the configuration fails, one of the following operations may be performed:
Step 1b: The relay UE sends a third HbH PC5 RRC message to the source UE to configure the local ID value(s) of the source UE and/or the target UE, where the HbH PC5 RRC message may carry at least one of the following content:
Step 2b: The source UE sends a fourth HbH PC5 RRC message to the relay UE to indicate that the configuration in step 1b is completed or fails.
Based on a result in step 2b, if it is determined that the configuration is completed, it is considered that the procedure for allocating the local ID(s) of the source UE and/or the target UE is completed; or if it is determined that the configuration fails, one of the following operations may be performed:
In an optional implementation, the second message is used to indicate that the local identity configuration for the second terminal succeeds or fails.
The configuration success may indicate that the local identity of the second terminal can be used to identify the second terminal in the U2U relay link, and the configuration failure may indicate that the local identity of the second terminal cannot be used to identify the second terminal in the U2U relay link.
Optionally, in a case that the second message indicates that the local identity configuration for the second terminal fails, the method further includes one of the following:
The performing an identity reallocation operation may be performing step 201 again, or performing a step of requesting the first terminal to configure a local identity for the second terminal again. As described in the foregoing implementation, the first terminal receives a third message sent by the relay terminal.
In this implementation, in the case of configuration failure, the local identity can be reconfigured; or U2U relay reselection can be triggered to perform relay communication through another relay terminal, to improve reliability of relay communication; or HbH PC5 RRC connection release can be triggered, to release an HbH PC5 RRC connection in time and avoid resource waste.
In an optional implementation, in a case that the first terminal is the source terminal, before the first terminal sends the first message, the first terminal has a first E2E PC5-S message to be sent, where the first E2E PC5-S message is used to establish an E2E PC5-S link with the target terminal; or
The first E2E PC5-S message may be a first E2E PC5-S message for establishing an E2E PC5-S link, such as a direct communication request (Direct Communication Request, DCR) or a relay discovery (Relay Discovery) message.
Having the first E2E PC5-S message to be sent triggers a local identity allocation procedure, where the allocation procedure may be the procedure for allocating the local identity of the target terminal by the source terminal, or may be the procedure for allocating the local identity of the source terminal by the target terminal, or may be the procedure for allocating the local identities of the source terminal and the target terminal by the relay terminal.
Having the first E2E PC5-S message to be sent may be that an access stratum (Access Stratum, AS) layer of the first terminal has received an E2E message delivered by an upper-layer entity to the AS layer, but the AS layer has not yet delivered the E2E message to a lower layer (such as a physical layer) for sending over an air interface. Therefore, in a case that the first terminal is the source terminal and that local identity configuration for at least one of the source terminal and the target terminal is completed, the first terminal sends the first E2E PC5-S message to the relay terminal.
The first notification message is used to trigger local identity configuration for at least one of the source terminal and the target terminal, which may be triggering the relay terminal to allocate the local identity of at least one of the source terminal and the target terminal.
In this implementation, the local identity can be allocated before an E2E PC5-S link establishment procedure is performed, so that all E2E PC5-S messages can use the local identity to reduce signaling overheads. For example, all the E2E PC5-S messages can go through a PC5 sidelink relay adaptation protocol (Sidelink Relay Adaptation Protocol, SRAP) layer.
Optionally, the method further includes at least one of the following:
That the first terminal sends the first E2E PC5-S message to the relay terminal may indicate that the source terminal has allocated a local identity to the target terminal, and/or that the target terminal has allocated a local identity to the source terminal, and therefore the first E2E PC5-S message for establishing the E2E PC5-S link is sent.
That the first terminal receives the first E2E PC5-S message sent by the source terminal may also indicate that the source terminal has allocated a local identity to the target terminal, and/or that the target terminal has allocated a local identity to the source terminal, and therefore the first E2E PC5-S message for establishing the E2E PC5-S link is received.
Optionally, a SRAP header of the first E2E PC5-S message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-S message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
The second E2E PC5-S message may be an E2E DCR sent by the relay terminal to the target terminal.
In this implementation, because the SRAP headers of the first E2E PC5-S message and the second E2E PC5-S message use local identities, overheads of the E2E PC5-S messages can be reduced.
In some implementations, a media access control (Medium Access Control, MAC) header of the first E2E PC5-S message may include a layer-2 identity of the source terminal and a layer-2 identity of the relay terminal, and a MAC header of the second E2E PC5-S message may include the layer-2 identity of the relay terminal and a layer-2 identity of the target terminal.
In an embodiment, as shown in
If the source UE receives a first E2E PC5-S message (such as a DCR) from its upper layer, the source UE performs one of the following:
If it is determined that at least one of the following conditions is met, the source UE performs the step of sending the first E2E PC5-S message to the relay UE:
As shown in
After receiving a PC5 SRAP protocol data unit (Protocol Data Unit, PDU) from the source UE, the relay UE performs additional processing on the PC5 SRAP header format if the relay UE determines that the header format meets the foregoing conditions, that is, the relay UE translates the local ID and the L2 ID in association during forwarding per hop (per hop), finally replaces the UE ID information with the local ID value of the source UE, and then forwards the PC5 SRAP PDU to the target UE.
As shown in
After receiving a PC5 SRAP PDU from the source UE, the relay UE transparently forwards the PC5 SRAP PDU to the target UE if the relay UE determines that the header format meets the foregoing conditions, without performing additional processing on the PC5 SRAP header format.
In an optional implementation, before the first terminal sends the first message, the method further includes at least one of the following:
The third E2E PC5-S message may be a third E2E PC5-S message for establishing an E2E PC5-S link, such as a DCR.
That the first terminal sends a third E2E PC5-S message to the relay terminal may be triggering the relay terminal to request the source terminal to allocate a local identity, or triggering the source terminal to allocate a local identity.
That the first terminal receives a third E2E PC5-S message sent by the source terminal may be receiving the third E2E PC5-S message and triggering a local identity allocation procedure, where the allocation procedure may be a procedure in which the relay terminal allocates local identities of the source terminal and the target terminal.
In this implementation, the local identity can be allocated in the E2E PC5-S link establishment procedure, so that all E2E PC5-S messages except the first E2E PC5-S message can use the local identity to reduce signaling overheads. For example, all the E2E PC5-S messages except the first E2E PC5-S message can go through the PC5 sidelink relay adaptation protocol (Sidelink Relay Adaptation Protocol, SRAP) layer.
Optionally, the method further includes:
That the first terminal sends a fourth E2E PC5-S message to the target terminal may indicate that the source terminal has allocated a local identity to the target terminal, and/or that the target terminal has allocated a local identity to the source terminal, and therefore the fourth E2E PC5-S message for establishing an E2E PC5-S link is sent.
Optionally, a SRAP header of the third E2E PC5-S message includes a local identity of the target terminal, and a SRAP header of the fourth E2E PC5-S message includes a local identity of the source terminal; or
In this implementation, because the SRAP headers of the third E2E PC5-S message and the fourth E2E PC5-S message use local identities, overheads of the E2E PC5-S messages can be reduced.
In some implementations, a MAC header of the third E2E PC5-S message may include a layer-2 identity of the source terminal and a layer-2 identity of the relay terminal, and a MAC header of the fourth E2E PC5-S message may include the layer-2 identity of the relay terminal and a layer-2 identity of the target terminal.
In an embodiment, as shown in 12, 13, and 14, the local ID allocation procedure is completed in the E2E PC5-S link establishment procedure, and in this embodiment, all E2E PC5-S messages except a first E2E DCR go through the PC5 SRAP layer to further reduce signaling overheads, as shown in
If the source UE receives a first E2E PC5-S message (such as a DCR) from its upper layer, the source UE sends the first E2E PC5-S message to the relay UE.
If the first E2E PC5-S message sent by the source UE is received, the relay UE performs one of the following:
If it is determined that at least one of the following conditions is met, the relay UE performs the step of sending the first E2E PC5-S message to the target UE:
As shown in
After receiving a PC5 SRAP PDU from the source UE, the relay UE performs additional processing on the PC5 SRAP header format if the relay UE determines that the header format meets the foregoing conditions, that is, the relay UE translates the local ID and the L2 ID in association during forwarding per hop, finally replaces the UE ID information with the local ID value of the source UE, and then forwards the PC5 SRAP PDU to the target UE.
As shown in
After receiving a PC5 SRAP PDU from the source UE, the relay UE transparently forwards the PC5 SRAP PDU to the target UE if the relay UE determines that the header format meets the foregoing conditions, without performing additional processing on the PC5 SRAP header format.
In an optional implementation, before the first terminal sends the first message, the method further includes at least one of the following:
The fifth E2E PC5-S message may be a last E2E PC5-S message in the E2E PC5-S link establishment process, such as direct communication accept (Direct Communication Accept, DCA). Completion of E2E PC5-S link establishment may also be understood as success of E2E PC5-S link establishment.
That the first terminal receives a fifth E2E PC5-S message sent by the target terminal may indicate that establishment of the E2E PC5-S link is completed, thereby triggering the local identity allocation procedure, where the allocation procedure may be the procedure for allocating the local identity of the target terminal by the source terminal, or may be the procedure for allocating the local identity of the source terminal by the target terminal, or may be the procedure for allocating the local identities of the source terminal and the target terminal by the relay terminal.
The second notification message may indicate that establishment of the E2E PC5-S link is completed, thereby triggering the relay terminal to allocate the local identity of at least one of the source terminal and the target terminal.
In this implementation, in a case that the establishment of the E2E PC5-S link is completed, the local identity can be allocated after end-to-end security is activated, so that the source terminal, the target terminal, and the relay terminal can use the local identity in subsequent communication in the E2E PC5-S link to reduce signaling overheads.
Optionally, the method further includes at least one of the following: in a case that the first terminal is the source terminal and that local identity configuration for at least one of the source terminal and the target terminal is completed, the first terminal sends a first E2E PC5-RRC message to the relay terminal; and
The first E2E PC5-RRC message may be any E2E PC5-RRC message after the E2E PC5-S link is successfully established, such as a PC5 RRC reconfiguration (RRC Reconfiguration) message.
That the first terminal sends a first E2E PC5-S message to the relay terminal may indicate that the source terminal has allocated a local identity to the target terminal, and/or that the target terminal has allocated a local identity to the source terminal, and therefore the first E2E PC5-RRC message is sent.
That the first terminal receives the first PC5-RRC message sent by the source terminal may also indicate that the relay terminal has allocated a local identity to the target terminal, and/or that the relay terminal has allocated a local identity to the source terminal, and therefore the first E2E PC5-RRC message is received.
Optionally, a SRAP header of the first E2E PC5-RRC message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-RRC message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
In this implementation, because the SRAP headers of the first E2E PC5-RRC message and the second E2E PC5-RRC message use local identities, overheads of the E2E PC5-RRC messages can be reduced.
In some implementations, a MAC header of the first E2E PC5-RRC message may include a layer-2 identity of the source terminal and a layer-2 identity of the relay terminal, and a MAC header of the second E2E PC5-RRC message may include the layer-2 identity of the relay terminal and a layer-2 identity of the target terminal.
In an embodiment, as shown in 15, 16, and 17, after the E2E PC5-S link establishment procedure is completed, the local ID allocation procedure is completed, so that end-to-end security is ensured for local ID allocation. As shown in
When the source UE receives the last E2E PC5-S message (such as DCA) from the target UE, the source UE performs one of the following:
If it is determined that at least one of the following conditions is met, the source UE sends a first E2E PC5 RRC message (such as PC5 RRC Reconfiguration) to the relay UE, or optionally sends U2U relay communication service data, or sends any E2E PC5-S message after the E2E PC5-S link is successfully established, including a link modification request (Link Modification Request), a link identifier update (Link Identifier Update) request, or the like:
As shown in
After receiving a PC5 SRAP PDU from the source UE, the relay UE needs to perform additional processing on the PC5 SRAP header format if the relay UE determines that the header format meets the foregoing conditions, that is, the relay UE translates the local ID and the L2 ID in association during forwarding per hop, finally replaces the UE ID information with the local ID value of the source UE, and then forwards the PC5 SRAP PDU to the target UE.
As shown in
After receiving a PC5 SRAP PDU from the source UE, the relay UE transparently forwards the PC5 SRAP PDU to the target UE if the relay UE determines that the header format meets the foregoing conditions, without performing additional processing on the PC5 SRAP header format.
In addition, in this embodiment of this application, the first terminal may perform U2U relay link communication based on at least one of the local identity of the second terminal and the local identity of the first terminal.
In this embodiment of this application, the first terminal sends the first message, where the first message is used to configure the local identity of the second terminal, and the local identity is used to uniquely identify the terminal in the U2U relay link, where the U2U relay link includes the source terminal, the target terminal, and the relay terminal, and the second terminal is the source terminal or the target terminal; and the first terminal receives the second message, where the second message is the response message to the first message. In this way, the local identity can be configured for the second terminal. The local identity uniquely identifies the terminal in the U2U relay link. Compared with a global L2 ID, the local identity has fewer bits. Therefore, transmission overheads of the terminal can be reduced.
Step 1801: A fourth terminal receives a first message sent by a first terminal, where the first message is used to configure a local identity of a second terminal, and the local identity is used to uniquely identify the terminal in a terminal-to-terminal U2U relay link, where the U2U relay link includes a source terminal, a target terminal, and a relay terminal, and the second terminal is the source terminal or the target terminal; and the fourth terminal and the second terminal are the same terminal, or the fourth terminal is the relay terminal.
Step 1802: The fourth terminal sends a second message to the first terminal, where the second message is a response message to the first message.
Optionally, the first message includes at least one of the following:
Optionally, before the fourth terminal receives the first message sent by the first terminal, the method further includes:
Optionally, the first terminal is the source terminal, and the second terminal is the target terminal; or
Optionally, the second message or a third message includes a local identity of the first terminal, and the third message is a message sent by the relay terminal and received by the first terminal; or
Optionally, the first terminal is the relay terminal.
Optionally, the first message is used to configure the local identity of the second terminal, or the first message is used to configure local identities of the second terminal and a third terminal, where
Optionally, the first message includes at least one of the following:
Optionally, the second message is used to indicate that the local identity configuration for the second terminal succeeds or fails.
Optionally, in a case that the second message indicates that the local identity configuration for the second terminal fails, the method further includes one of the following:
Optionally, the first message is an HbH PC5 RRC message, and the second message is an HbH PC5 RRC message.
Optionally, in a case that the fourth terminal is the source terminal, before the fourth terminal receives the first message sent by the first terminal, the fourth terminal has a first end-to-end E2E PC5-S message to be sent, where the first E2E PC5-S message is used to establish an E2E PC5-S link with the target terminal; or
Optionally, the method further includes at least one of the following:
Optionally, a sidelink relay adaptation protocol SRAP header of the first E2E PC5-S message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-S message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
Optionally, before the fourth terminal receives the first message sent by the first terminal, the method further includes at least one of the following:
Optionally, the method further includes:
Optionally, a SRAP header of the third E2E PC5-S message includes a local identity of the target terminal, and a SRAP header of the fourth E2E PC5-S message includes a local identity of the source terminal; or
Optionally, before the fourth terminal receives the first message sent by the first terminal, the method further includes at least one of the following:
Optionally, the method further includes at least one of the following:
Optionally, a SRAP header of the first E2E PC5-RRC message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-RRC message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
It should be noted that this embodiment is used as an implementation of the fourth terminal corresponding to the embodiment shown in
The identity configuration apparatus corresponds to the first terminal, or it may be understood that the first terminal includes the identity configuration apparatus.
Optionally, the first message includes at least one of the following:
Optionally, the apparatus further includes:
Optionally, the first terminal is the source terminal, the second terminal is the target terminal, the first message is a first message sent by the first terminal to the relay terminal, and the second message is a second message sent by the relay terminal and received by the first terminal; or
Optionally, the second message or a third message includes a local identity of the first terminal, and the third message is a message sent by the relay terminal and received by the first terminal; or
Optionally, the first terminal is the relay terminal, the first message is a message sent by the first terminal to the second terminal, and the second message is a message sent by the second terminal and received by the first terminal.
Optionally, the apparatus further includes:
Optionally, the first message is used to configure the local identity of the second terminal, or the first message is used to configure the local identities of the second terminal and the third terminal;
Optionally, the first message includes at least one of the following:
Optionally, the second message is used to indicate that the local identity configuration for the second terminal succeeds or fails.
Optionally, the apparatus further includes one of the following:
Optionally, the first message is an HbH PC5 RRC message, and the second message is an HbH PC5 RRC message.
Optionally, in a case that the first terminal is the source terminal, before the first terminal sends the first message, the first terminal has a first end-to-end E2E PC5-S message to be sent, where the first E2E PC5-S message is used to establish an E2E PC5-S link with the target terminal; or
Optionally, the apparatus further includes at least one of the following:
Optionally, a sidelink relay adaptation protocol SRAP header of the first E2E PC5-S message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-S message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
Optionally, the apparatus further includes at least one of the following:
Optionally, the apparatus further includes:
Optionally, a SRAP header of the third E2E PC5-S message includes a local identity of the target terminal, and a SRAP header of the fourth E2E PC5-S message includes a local identity of the source terminal; or
Optionally, the apparatus further includes at least one of the following:
Optionally, the method further includes at least one of the following:
Optionally, a SRAP header of the first E2E PC5-RRC message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-RRC message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
The identity configuration apparatus can reduce transmission overheads.
The identity configuration apparatus in this embodiment of this application may be an electronic device, for example, an electronic device with an operating system, or may be a component in an electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. For example, the terminal may include but is not limited to the illustrated type of the terminal in the embodiment of this application. The other devices may be a server, a network attached storage (Network Attached Storage, NAS), and the like. This is not specifically limited in this embodiment of this application.
The identity configuration apparatus provided in this embodiment of this application can implement each process implemented in the method embodiment in
The identity configuration apparatus corresponds to the fourth terminal, or it may be understood that the fourth terminal includes the identity configuration apparatus. The fourth terminal and the second terminal are the same terminal, or the fourth terminal is the relay terminal.
Optionally, the first message includes at least one of the following:
Optionally, the apparatus further includes:
Optionally, the first terminal is the source terminal, and the second terminal is the target terminal; or
Optionally, the second message or a third message includes a local identity of the first terminal, and the third message is a message sent by the relay terminal and received by the first terminal; or
Optionally, the first terminal is the relay terminal.
Optionally, the first message is used to configure the local identity of the second terminal, or the first message is used to configure local identities of the second terminal and a third terminal, where
Optionally, the first message includes at least one of the following:
Optionally, the second message is used to indicate that the local identity configuration for the second terminal succeeds or fails.
Optionally, the apparatus further includes one of the following:
Optionally, the first message is an HbH PC5 RRC message, and the second message is an HbH PC5 RRC message.
Optionally, in a case that the fourth terminal is the source terminal, before the fourth terminal receives the first message sent by the first terminal, the fourth terminal has a first end-to-end E2E PC5-S message to be sent, where the first E2E PC5-S message is used to establish an E2E PC5-S link with the target terminal; or
Optionally, the apparatus further includes at least one of the following:
Optionally, a sidelink relay adaptation protocol SRAP header of the first E2E PC5-S message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-S message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
Optionally, the apparatus further includes at least one of the following:
Optionally, the apparatus further includes:
Optionally, a SRAP header of the third E2E PC5-S message includes a local identity of the target terminal, and a SRAP header of the fourth E2E PC5-S message includes a local identity of the source terminal; or
Optionally, the apparatus further includes at least one of the following:
Optionally, the apparatus further includes at least one of the following:
Optionally, a SRAP header of the first E2E PC5-RRC message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-RRC message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
The identity configuration apparatus can reduce transmission overheads.
The identity configuration apparatus in this embodiment of this application may be an electronic device, for example, an electronic device with an operating system, or may be a component in an electronic device, for example, an integrated circuit or a chip. The electronic device may be a terminal, or may be other devices than a terminal. For example, the terminal may include but is not limited to the illustrated type of the terminal in the embodiment of this application. The other devices may be a server, a network attached storage (Network Attached Storage, NAS), and the like. This is not specifically limited in this embodiment of this application.
The identity configuration apparatus provided in this embodiment of this application can implement each process implemented in the method embodiment in
Optionally, as shown in
An embodiment of this application further provides a terminal, including a processor and a communication interface. The communication interface is configured to: send a first message, where the first message is used to configure a local identity of a second terminal, and the local identity is used to uniquely identify the terminal in a U2U relay link, where the U2U relay link includes a source terminal, a target terminal, and a relay terminal, and the second terminal is the source terminal or the target terminal; and receive a second message, where the second message is a response message to the first message. The terminal embodiment corresponds to the foregoing method embodiment on the first terminal side, and each implementation process and implementation of the foregoing method embodiment can be applied to the terminal embodiment, with the same technical effect achieved.
An embodiment of this application further provides a terminal, including a processor and a communication interface. The communication interface is configured to: receive a first message sent by a first terminal, where the first message is used to configure a local identity of a second terminal, and the local identity is used to uniquely identify the terminal in a U2U relay link, where the U2U relay link includes a source terminal, a target terminal, and a relay terminal, and the second terminal is the source terminal or the target terminal; and send a second message to the first terminal, where the second message is a response message to the first message. The terminal embodiment corresponds to the foregoing method embodiment on the fourth terminal side, and each implementation process and implementation of the foregoing method embodiment can be applied to the terminal embodiment, with the same technical effect achieved.
Specifically,
The terminal 2200 includes but is not limited to at least some components such as a radio frequency unit 2201, a network module 2202, an audio output unit 2203, an input unit 2204, a sensor 2205, a display unit 2206, a user input unit 2207, an interface unit 2208, a memory 2209, and a processor 2210.
A person skilled in the art may understand that the terminal 2200 may further include a power supply (for example, a battery) supplying power to all components. The power supply may be logically connected to the processor 2210 through a power management system. In this way, functions such as charge management, discharge management, and power consumption management are implemented by using the power management system. The terminal structure shown in
It should be understood that, in this embodiment of this application, the input unit 2204 may include a graphics processing unit (Graphics Processing Unit, GPU) 22041 and a microphone 22042. The graphics processing unit 22041 processes image data of a still picture or video obtained by an image capture apparatus (such as a camera) in a video capture mode or an image capture mode. The display unit 2206 may include a display panel 22061, and the display panel 22061 may be configured in a form of a liquid crystal display, an organic light-emitting diode, or the like. The user input unit 2207 includes at least one of a touch panel 22071 and other input devices 22072. The touch panel 22071 is also referred to as a touchscreen. The touch panel 22071 may include two parts: a touch detection apparatus and a touch controller. The other input devices 22072 may include but are not limited to a physical keyboard, a function button (such as a volume control button or a power button), a trackball, a mouse, and a joystick. Details are not described herein again.
In this embodiment of this application, after receiving downlink data from a network-side device, the radio frequency unit 2201 may transmit the downlink data to the processor 2210 for processing. In addition, the radio frequency unit 2201 may send uplink data to the network-side device. Usually, the radio frequency unit 2201 includes but is not limited to an antenna, an amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like.
The memory 2209 may be configured to store software programs or instructions and various data. The memory 2209 may primarily include a first storage area for storing programs or instructions and a second storage area for storing data. The first storage area may store an operating system, an application program or instructions required by at least one function (such as an audio play function and an image play function), and the like. In addition, the memory 2209 may include a volatile memory or a non-volatile memory, or the memory 2209 may include both a volatile memory and a non-volatile memory. The non-volatile memory may 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. The volatile memory may be a random access memory (Random Access Memory, RAM), a static random access memory (Static RAM, SRAM), a dynamic random access memory (Dynamic RAM, DRAM), a synchronous dynamic random access memory (Synchronous DRAM, SDRAM), a double data rate synchronous dynamic random access memory (Double Data Rate SDRAM, DDR SDRAM), an enhanced synchronous dynamic random access memory (Enhanced SDRAM, ESDRAM), a synchlink dynamic random access memory (Synch Link DRAM, SLDRAM), and a direct rambus random access memory (Direct Rambus RAM, DRRAM). The memory 2209 in this embodiment of this application includes but is not limited to these and any other suitable types of memories.
The processor 2210 may include one or more processing units. Optionally, the processor 2210 integrates an application processor and a modem processor. The application processor mainly processes operations related to the operating system, a user interface, an application program, and the like. The modem processor mainly processes a wireless communication signal. For example, the modem processor is a baseband processor. It may be understood that the modem processor may alternatively be not integrated in the processor 2210.
In an embodiment in which the terminal is a first terminal:
Optionally, the first message includes at least one of the following:
Optionally, before sending the first message, the radio frequency unit 2201 is further configured to:
Optionally, the first terminal is the source terminal, the second terminal is the target terminal, the first message is a first message sent by the first terminal to the relay terminal, and the second message is a second message sent by the relay terminal and received by the first terminal; or
Optionally, the second message or a third message includes a local identity of the first terminal, and the third message is a message sent by the relay terminal and received by the first terminal; or
Optionally, the first terminal is the relay terminal, the first message is a message sent by the first terminal to the second terminal, and the second message is a message sent by the second terminal and received by the first terminal.
Optionally, the radio frequency unit 2201 is further configured to:
Optionally, the first message is used to configure the local identity of the second terminal, or the first message is used to configure the local identities of the second terminal and the third terminal;
Optionally, the first message includes at least one of the following:
Optionally, the second message is used to indicate that the local identity configuration for the second terminal succeeds or fails.
Optionally, in a case that the second message indicates that the local identity configuration for the second terminal fails, the radio frequency unit 2201 is further configured to perform at least one of the following:
Optionally, the first message is an HbH PC5 RRC message, and the second message is an HbH PC5 RRC message.
Optionally, in a case that the first terminal is the source terminal, before the first terminal sends the first message, the first terminal has a first end-to-end E2E PC5-S message to be sent, where the first E2E PC5-S message is used to establish an E2E PC5-S link with the target terminal; or
Optionally, the radio frequency unit 2201 is further configured to perform at least one of the following:
Optionally, a sidelink relay adaptation protocol SRAP header of the first E2E PC5-S message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-S message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
Optionally, before the first terminal sends the first message, the radio frequency unit 2201 is further configured to perform at least one of the following:
Optionally, the radio frequency unit 2201 is further configured to perform at least one of the following:
in a case that the first terminal is the relay terminal and that local identity configuration for at least one of the source terminal and the target terminal is completed, sending, by the first terminal, a fourth E2E PC5-S message to the target terminal.
Optionally, a SRAP header of the third E2E PC5-S message includes a local identity of the target terminal, and a SRAP header of the fourth E2E PC5-S message includes a local identity of the source terminal; or
Optionally, before the first terminal sends the first message, the radio frequency unit 2201 is further configured to perform at least one of the following:
Optionally, the radio frequency unit 2201 is further configured to perform at least one of the following:
Optionally, a SRAP header of the first E2E PC5-RRC message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-RRC message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
In an embodiment in which the terminal is a fourth terminal:
Optionally, the first message includes at least one of the following:
Optionally, before the fourth terminal receives the first message sent by the first terminal, the radio frequency unit 2201 is further configured to:
Optionally, the first terminal is the source terminal, and the second terminal is the target terminal; or
Optionally, the second message or a third message includes a local identity of the first terminal, and the third message is a message sent by the relay terminal and received by the first terminal; or the radio frequency unit 2201 is further configured to:
Optionally, the first terminal is the relay terminal.
Optionally, the first message is used to configure the local identity of the second terminal, or the first message is used to configure local identities of the second terminal and a third terminal, where
Optionally, the first message includes at least one of the following:
Optionally, the second message is used to indicate that the local identity configuration for the second terminal succeeds or fails.
Optionally, in a case that the second message indicates that the local identity configuration for the second terminal fails, the radio frequency unit 2201 is further configured to perform at least one of the following:
Optionally, the first message is an HbH PC5 RRC message, and the second message is an HbH PC5 RRC message.
Optionally, in a case that the fourth terminal is the source terminal, before the fourth terminal receives the first message sent by the first terminal, the fourth terminal has a first end-to-end E2E PC5-S message to be sent, where the first E2E PC5-S message is used to establish an E2E PC5-S link with the target terminal; or
Optionally, the radio frequency unit 2201 is further configured to perform at least one of the following:
Optionally, a sidelink relay adaptation protocol SRAP header of the first E2E PC5-S message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-S message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
Optionally, before the fourth terminal receives the first message sent by the first terminal, the radio frequency unit 2201 is further configured to perform at least one of the following:
Optionally, the radio frequency unit 2201 is further configured to:
Optionally, a SRAP header of the third E2E PC5-S message includes a local identity of the target terminal, and a SRAP header of the fourth E2E PC5-S message includes a local identity of the source terminal; or
Optionally, before the fourth terminal receives the first message sent by the first terminal, the radio frequency unit 2201 is further configured to perform at least one of the following:
Optionally, the radio frequency unit 2201 is further configured to perform at least one of the following:
Optionally, a SRAP header of the first E2E PC5-RRC message includes a local identity of the target terminal; and a SRAP header of a second E2E PC5-RRC message sent by the relay terminal to the target terminal includes a local identity of the source terminal; or
The terminal can reduce transmission overheads of the terminal.
An embodiment of this application further provides a readable storage medium. The readable storage medium stores a program or instructions. When the program or instructions are executed by a processor, the steps of the identity configuration method according to the embodiments of this application are implemented.
The processor is a processor in the terminal in the foregoing 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 disc.
In addition, an embodiment of this application provides a chip. The chip includes a processor and a communication interface. The communication interface is coupled to the processor. The processor is configured to run a program or instructions to implement each process of the foregoing embodiment of the identity configuration method, with the same technical effect achieved. To avoid repetition, details are not described herein again.
It should be understood that the chip provided in this embodiment of this application may also be referred to as a system-level chip, a system chip, a chip system, a system-on-chip, or the like.
In addition, an embodiment of this application provides a computer program or program product. The computer program or program product is stored in a storage medium. The computer program or program product is executed by at least one processor of a first terminal to implement each process of the identity configuration method on the first terminal side according to the embodiment of the identity configuration method, or the computer program or program product is executed by at least one processor of a fourth terminal to implement each process of the identity configuration method on the fourth terminal side according to the embodiment of the identity configuration method, with the same technical effect achieved. To avoid repetition, details are not described herein again.
An embodiment of this application further provides an identity configuration system, including a first terminal and a fourth terminal. The first terminal may be configured to perform the steps of the identity configuration method on the first terminal side according to the embodiments of this application. The fourth terminal may be configured to perform the steps of the identity configuration method on the fourth terminal side according to the embodiments of this application.
It should be noted that in this specification, the term “comprise”, “include”, or any of their variants are intended to cover a non-exclusive inclusion, so that a process, a method, an article, or an apparatus that includes a list of elements not only includes those elements but also includes other elements that are not expressly listed, or further includes elements inherent to such process, method, article, or apparatus. In absence of more constraints, an element preceded by “includes a . . . ” does not preclude existence of other identical elements in the process, method, article, or apparatus that includes the element. In addition, it should be noted that the scope of the method and apparatus in the implementations of this application is not limited to performing the functions in an order shown or discussed, and may further include performing the functions in a substantially simultaneous manner or in a reverse order depending on the functions used. For example, the method described may be performed in an order different from that described, and various steps may be added, omitted, or combined. In addition, features described with reference to some examples may be combined in other examples.
Based on the foregoing descriptions of the implementations, a person skilled in the art may clearly understand that the foregoing embodiment methods can be implemented by using software in combination to a hardware platform, or by using hardware only. Based on such an understanding, the technical solutions of this application may be implemented in a form of a computer software product. The computer software product is stored in a storage medium (such as a ROM/RAM, a magnetic disk, or an optical disc), and includes several instructions for instructing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the methods described in the embodiments of this application.
The foregoing describes the embodiments of this application with reference to the accompanying drawings. However, this application is not limited to the foregoing specific embodiments. The foregoing specific embodiments are merely illustrative rather than restrictive. Inspired by this application, a person of ordinary skill in the art may develop many other manners without departing from principles of this application and the protection scope of the claims, and all such manners fall within the protection scope of this application.
| Number | Date | Country | Kind |
|---|---|---|---|
| 202210771401.1 | Jun 2022 | CN | national |
This application is a continuation of International Patent Application No. PCT/CN2023/102106, filed on Jun. 25, 2023, which claims priority to Chinese Patent Application No. 202210771401.1, filed in China on Jun. 30, 2022, both of which are incorporated herein by reference in their entireties.
| Number | Date | Country | |
|---|---|---|---|
| Parent | PCT/CN2023/102106 | Jun 2023 | WO |
| Child | 19004506 | US |
