Patent Description:
With the continuous development of communications technologies, vehicle to X (Vehicle to X, V2X) technologies such as communication interactions of vehicle to vehicle (Vehicle to Vehicle, V2V), vehicle to pedestrian (Vehicle to Pedestrian, V2P), and vehicle to infrastructure (Vehicle to Infrastructure, V2I) have emerged. V2X services such as V2V and V2P may be transmitted through a PC5 interface between user equipments (User Equipment, UE).

For example, currently for transmitting a <NUM> NR-based V2X service between UE <NUM> and UE <NUM> through a PC5 interface, a PC5 link needs to be established between UE <NUM> and UE <NUM> in advance. Specifically, UE <NUM> broadcasts a direct communication request message (hereinafter referred to as direct communication request message <NUM>) that carries at least a layer <NUM> address of UE <NUM>. In this case, UE <NUM> near UE <NUM> can reply to UE <NUM> with a direct communication accept message after UE <NUM> receives direct communication request message <NUM>. Thus, UE <NUM> can establish the PC5 link with UE <NUM>.

However, in the foregoing process, in one aspect, when UE <NUM> needs to establish another PC5 link for the same service with another UE, UE <NUM> again broadcasts a direct communication request message in which the layer <NUM> address of UE <NUM> may have been changed. Therefore, UE <NUM> may establish another PC5 link with UE <NUM> after receiving the direct communication request message broadcast again. In other words, a plurality of PC5 links for the same service may be established between UE <NUM> and UE <NUM>, resulting in waste of air interface resources. In another aspect, when the foregoing direct communication request message <NUM> also carries identifiers of a plurality of UEs, only some of the UEs may reply to UE <NUM> with direct communication accept messages. As a result, UE <NUM> may fail to identify which UEs accept the direct communication request, further leading to a PC5 link establishment failure. Therefore, in the foregoing two aspects, PC5 links between UEs cannot be well established.

The document <NPL>)) discusses layer-<NUM> link establishment procedure for unicast mode of V2X communication over PC5. The document <NPL>) discusses UE oriented layer <NUM> link establishment procedure. The document <NPL>) discusses how to implement the above-mentioned stage <NUM> requirements in stage <NUM> and to propose a way forward. <CIT> provides a method and apparatus for performing D2D communication. The method includes being assigned a transmission and reception indicator and an index during D2D connection setup between a User Equipment (UE) and a Base Station (BS) by the UE, the transmission and reception indicator indicating a transmission role or a reception role and the index indicating another UE for D2D communication, receiving the transmission and reception indicator, the index, and resource information for the D2D communication on a control channel by the UE, and performing, by the UE, a transmission operation or a reception operation to or from the other UE indicated by the index in resources indicated by the resource information according to the transmission role or the reception role indicated by the transmission and reception indicator. <CIT> provides a connection establishment method, a terminal device, and a network device, where the connection establishment method includes: sending a first request message to a network device, where the first request message is used to request, from the network device, related information of a unicast connection between the first terminal device and a second terminal device; and receiving a first response message sent by the network device.

According to a first aspect, the present invention provides a method for PC5 link establishment, performed by a first UE, as defined by independent claim <NUM>. According to a second aspect, the present invention provides a method for PC5 link establishment, performed by a second UE, as defined by independent claim <NUM>. According to a third aspect, the present invention provides a UE as defined by independent claim <NUM>. According to a fourth aspect, the present invention provides a UE as defined by independent claim <NUM>. According to a fifth aspect, the present invention provides a communications system as defined by independent claim <NUM>. According to a sixth aspect, the present invention provides a computer-readable storage medium as defined by independent claim <NUM>.

In particular, the embodiments referring to <FIG> are not according to the invention and are present for illustration purposes only. The following clearly and completely describes the technical solutions in the embodiments of this disclosure with reference to the accompanying drawings in the embodiments of this disclosure. Apparently, the described embodiments are merely some rather than all of the embodiments of this disclosure. All other embodiments obtained by persons of ordinary skill in the art without creative efforts based on the embodiments of this disclosure shall fall within the protection scope of this disclosure.

In the embodiments of this disclosure, terms such as "an example" or "for example" are used to represent examples, illustrations, or explanations. Any embodiment or design solution described as "an example" or "for example" in the embodiments of this disclosure shall not be interpreted as being more preferred or advantageous than other embodiments or design solutions. Specifically, the terms such as "an example" or "for example" are used to present related concepts in a specific manner.

The following first explains some nouns/terms in the claims and the specification of this application as an example.

In the descriptions of the embodiments of this disclosure, "a plurality of" means two or more than two, for example, a plurality of processing units mean two or more processing units; a plurality of elements mean two or more elements; or the like, unless otherwise specified.

The term "and/or" in the specification describes an association relationship for describing associated objects and represents that three relationships may exist. The symbol "/" herein indicates an "or" relationship of associated objects. For example, A/B means A or B.

According to a method for PC5 link establishment in this embodiment of this disclosure, first UE sends a direct communication request message, and receives a direct communication accept message sent by second UE, where the direct communication request message carries an identifier of the first UE, and is used to request establishment of a PC5 link, and the direct communication accept message carries an identifier of the second UE, and is used to accept the establishment of the PC5 link with the first UE. In this solution, because the direct communication request message carries the identifier that uniquely identifies the first UE, and the direct communication accept message carries the identifier that uniquely identifies the second UE, the first UE and the second UE can recognize each other. This not only ensures that the PC5 link can be successfully established between the first UE and the second UE, but also ensures that only one PC5 link for a same service is established between the first UE and the second UE. In this way, a PC5 link between UEs can be well established.

The method for PC5 link establishment, the device, and the system in the embodiments of this disclosure may be applied to communications systems, for example, a long term evolution (Long Term Evolution, LTE) system, a new radio (new radio, NR) system, or a plurality of communications fusion systems, and may be specifically applied to transmission of a V2X service, such as V2V or V2P, through a PC5 interface between UEs based on the communications system.

For example, <FIG> is a schematic architectural diagram of a communications system according to an embodiment of this disclosure. As shown in <FIG>, the communications system includes at least one UE (UE <NUM> and UE <NUM> in <FIG> are used as an example of the at least one UE). As shown in <FIG>, a PC5 link is established between two UEs of the at least one UE through a PC5 interface, and a service may be transmitted through the established PC5 link.

For example, the UE is a device that provides a user with voice and/or data connectivity, a handheld device with a wireless or wired connection function, or another processing device connected to a wireless modem. The UE may communicate with one or more core network devices through a radio access network (Radio Access Network, RAN). The UE may be a mobile terminal, such as a mobile phone (or referred to as a "cellular" phone) and a computer with a mobile terminal, or may be a portable, pocket-sized, handheld, computer built-in or vehicle-mounted mobile apparatus, which exchanges a voice and/or data with the RAN. For example, the UE is a device such as a personal communication service (Personal Communication Service, PCS) phone, a cordless telephone set, a session initiation protocol (SIP) phone, a wireless local loop (Wireless Local Loop, WLL) station, or a personal digital assistant (Personal Digital Assistant, PDA). The UE may also be referred to as a user agent (User Agent), a terminal device, or the like.

The method for PC5 link establishment provided in this embodiment of this disclosure may be applied to but is not limited to the following two scenarios. The following provides an exemplary description by using an example in which UE <NUM> is UE that sends a direct communication request message (direct communication request) (a UE that initiates PC5 link establishment), and UE <NUM> and/or UE <NUM> is UE(s) that send(s) a direct communication accept message (direct communication accept).

First scenario: In a case that a V2X application layer of UE <NUM> provides an identifier of UE <NUM> and an identifier of UE <NUM> (that is, UE <NUM> knows an identifier of at least one target UE (user info)), UE <NUM> broadcasts the direct communication request message carrying a source layer2 identifier, an application layer ID (application layer ID) of UE <NUM>, and an application layer ID of UE <NUM>. After receiving the direct communication request message, UE <NUM> and UE <NUM> determine, based on the application layer IDs (for example, based on whether the direct communication request message includes the application layer IDs), whether to send a direct communication accept message to UE <NUM>, and then determine whether to establish a PC5 link with UE <NUM>. A direct communication accept message sent by UE as a reply does not carry an identifier of the UE.

It should be noted that, in the first scenario, if UE <NUM> receives only one direct communication accept message, because the direct communication accept message does not carry an identifier of a corresponding UE (a UE that sends the direct communication accept message), UE <NUM> cannot identify whether UE <NUM> or UE <NUM> accepts the direct communication request message sent by UE <NUM>. In this case, UE <NUM> may fail to establish the PC5 links (that is, UE <NUM> cannot establish the PC5 link with UE <NUM> or the PC5 link with UE <NUM>).

To resolve the problem in the first scenario, in the method for PC5 link establishment provided in this embodiment of this disclosure, the direct communication request message carries the identifier of UE <NUM>, and the direct communication accept message carries the identifier of the corresponding UE (if UE <NUM> replies with the direct communication accept message, the direct communication accept message carries the identifier of UE <NUM> (for example, the application layer ID of UE <NUM>); or if UE <NUM> replies with the direct communication accept message, the direct communication accept message carries the identifier of UE <NUM> (for example, the application layer ID of UE <NUM>)). Therefore, when receiving only one direct communication accept message, UE <NUM> can identify, based on the identifier of the corresponding UE carried in the direct communication accept message, whether UE <NUM> or UE <NUM> replies with the direct communication accept message. In this way, UE <NUM> can successfully establish a PC5 link with the UE (UE <NUM> or UE <NUM>) that replies with the direct communication accept message.

Second scenario: In a case that UE <NUM> does not know any UE identifier, UE <NUM> broadcasts a direct communication request message carrying a source layer2 identifier. After receiving the direct communication request message, UE <NUM> and/or UE <NUM> may determine, based on service interests (that is, whether a service needs to be transmitted), whether to send the direct communication accept message to UE <NUM>, and further determine whether to establish the PC5 link with UE <NUM>. A direct communication accept message sent by UE as a reply does not carry an identifier of the UE.

It should be noted that, it can be learned from the description of the second scenario that UE <NUM> does not need to know whether UE <NUM> or UE <NUM> replies to the direct communication request of UE <NUM>. However, if UE <NUM> has established one PC5 link for service <NUM> with UE <NUM>, and needs to establish PC5 links for service <NUM> with more UEs, UE <NUM> broadcasts a direct communication request message again. However, from the perspective of security, a source layer2 identifier carried in the direct communication request message broadcast again by UE <NUM> may be different from the source layer2 identifier carried in the previously broadcast direct communication request message (that is, the layer <NUM> address of UE <NUM> is changed). In this case, when UE <NUM> also needs to establish PC5 links for service <NUM> with more UEs, UE <NUM> may establish another PC5 link with UE <NUM> after receiving the direct communication request message broadcast again by UE <NUM>. As a result, UE <NUM> and UE <NUM> may establish two or more PC5 links for service <NUM>. However, establishing a plurality of PC5 links for a same service between two UEs is unnecessary, and only leads to waste of air interface resources.

To resolve the problem in the second scenario, in the method for PC5 link establishment in this embodiment of this disclosure, the direct communication request message carries the identifier of UE <NUM>, and the direct communication accept message carries the identifier of the corresponding UE (if UE <NUM> replies with the direct communication accept message, the direct communication accept message carries the identifier of UE <NUM>; or if UE <NUM> replies with the direct communication accept message, the direct communication accept message carries the identifier of UE <NUM>). Therefore, after receiving the direct communication accept message, UE <NUM> can identify, based on the identifier of the corresponding UE carried in the direct communication accept message, whether UE <NUM> or UE <NUM> replies with the direct communication accept message. In this way, UE <NUM> can successfully establish the PC5 link with UE <NUM> that replies with the direct communication accept message, and/or successfully establish the PC5 link with UE <NUM> that replies with the direct communication accept message.

It should be noted that the following problem may also exist in the second scenario: Because each UE generates its own layer <NUM> address, when UE <NUM> receives direct communication accept messages (carrying layer <NUM> addresses of UEs) sent by a plurality of UEs, source layer2 identifiers carried in direct communication accept messages sent by different UEs may be the same (this case has a relatively low probability). As a result, UE <NUM> may fail to determine whether the direct communication accept messages are direct communication accept messages sent by different UEs, or one direct communication accept message sent twice by same UE (for example, the UE does not receive a confirmation message from UE <NUM> in time).

To resolve the foregoing problem, in the method for PC5 link establishment in this embodiment of this disclosure, the direct communication request message carries the identifier of UE <NUM>, and the direct communication accept message carries the identifier of the corresponding UE (if UE <NUM> replies with the direct communication accept message, the direct communication accept message carries the identifier of UE <NUM>; or if UE <NUM> replies with the direct communication accept message, the direct communication accept message carries the identifier of UE <NUM>). Therefore, when receiving a plurality of direct communication accept messages carrying a same source layer2 identifier, UE <NUM> can identify whether the direct communication accept messages are direct communication accept messages sent by different UEs, or one direct communication accept message sent repeatedly by a same UE (for example, the UE does not receive a confirmation message from UE <NUM> in time).

In conclusion, the method for PC5 link establishment provided in this embodiment of this disclosure can resolve a problem that a PC5 link between UEs cannot be well established in the related art.

With reference to the accompanying drawings, the following describes in detail a method for PC5 link establishment, a device, and a system provided in the embodiments of this disclosure based on specific embodiments and application scenarios of the embodiments.

Based on the communications system shown in <FIG>, an embodiment of this disclosure provides a method for PC5 link establishment. As shown in <FIG>, the method may include the following step <NUM> to step <NUM>.

Step <NUM>. First UE sends a direct communication request message.

It may be understood that the first UE broadcasts the direct communication request message. All UEs near the first UE can receive the direct communication request message.

Any UE that receives the direct communication request message may or may not reply with a direct communication accept message. This may be specifically determined based on an actual usage status, and is not limited in this embodiment of this disclosure.

For example, if both second UE and third UE are near the first UE, the second UE may receive the direct communication request message, and the third UE may also receive the direct communication request message. The following provides an exemplary description by using an example in which the second UE replies with the direct communication accept message, but the third UE does not reply with the direct communication accept message.

Second UE receives the direct communication request message sent by the first UE.

The second UE receives the direct communication request message broadcast by the first UE. The direct communication request message carries an identifier of the first UE, and is used to request establishment of a PC5 link.

In this embodiment of this disclosure, the identifier of the first UE is used to uniquely identify the first UE. A layer <NUM> address of the first UE is not the identifier of the first UE.

It should be noted that, in this embodiment of this disclosure, an identifier of UE is an identifier that uniquely identifies the UE. Because a layer <NUM> address of UE is not an identifier that uniquely identifies the UE, and the UE may have a plurality of different layer <NUM> addresses at the same time, the layer <NUM> address of the UE is not the identifier of the UE.

According to the present invention, the identifier of the first UE is either an international mobile subscriber identification number (International Mobile Subscriber Identification Number, IMSI) of the first UE, or a permanent equipment identifier (Permanent Equipment Identifier, PEI) of the first UE.

It should be noted that, after receiving the direct communication request message sent by the first UE, the second UE may determine, based on a preset rule, whether to reply with the direct communication accept message.

Optionally, the direct communication request message further carries the layer <NUM> address of the first UE, and may further carry other information. This may be specifically determined according to an actual usage requirement, and is not limited in this embodiment of this disclosure.

A third UE receives the direct communication request message sent by the first UE.

The third UE does not send the direct communication accept message to the first UE.

Step <NUM>. The second UE sends a direct communication accept message to the first UE.

Step <NUM>. The first UE receives the direct communication accept message sent by the second UE.

The direct communication accept message carries an identifier of the second UE, and is used to accept the establishment of the PC5 link with the first UE.

The identifier of the second UE is used to uniquely identify the second UE. A layer <NUM> address of the second UE is not the identifier of the second UE.

The identifier of the second UE is either an IMSI of the second UE, or a PEI of the second UE.

Optionally, the direct communication accept message further carries the layer <NUM> address of the second UE, and may also carry other information. This may be specifically determined according to an actual usage requirement, and is not limited in this embodiment of this disclosure.

According to the method for PC5 link establishment in this embodiment of this disclosure, the first UE sends sends the direct communication request message, and receives receives the direct communication accept message sent by the second UE, where the direct communication request message carries the identifier of the first UE, and is used to request the establishment of the PC5 link, and the direct communication accept message carries the identifier of the second UE, and is used to accept the establishment of the PC5 link with the first UE. In this solution, because the direct communication request message carries the identifier that uniquely identifies the first UE, and the direct communication accept message carries the identifier that uniquely identifies the second UE, the first UE and the second UE can recognize each other. This not only ensures that the PC5 link can be successfully established between the first UE and the second UE, but also ensures that only one PC5 link for a same service is established between the first UE and the second UE. In this way, a PC5 link between UEs can be well established.

In the foregoing first scenario, optionally, the direct communication request message further carries an identifier of at least one target UE. An identifier of each target UE in the identifier of the at least one target UE may uniquely identify the target UE. The identifier of each target UE may be an application layer ID of the target UE, an IMSI of the target UE, a PEI of the target UE, or another identifier that is used to uniquely identify the target UE. This is not limited in this embodiment of this disclosure.

The direct communication request message is specifically used to request establishment of a PC5 link with the at least one target UE. Specifically, the direct communication request message is used to request establishment of a PC5 link with each of the at least one target UE. The identifier of the at least one target UE may include the identifier of the second UE (in this case, the second UE is a target UE), or may not include the identifier of the second UE (in this case, the second UE is not the target UE). This may be specifically determined according to an actual usage requirement, and is not limited in this embodiment of this disclosure.

For example, step <NUM> may be specifically implemented by using the following step 203a.

In a case that the identifier of the at least one target UE includes the identifier of the second UE, the second UE sends the direct communication accept message to the first UE.

It may be understood that, in a case that the second UE detects that the identifier of the at least one target UE that is carried in the direct communication request message includes the identifier of the second UE, the second UE sends the direct communication accept message to the first UE.

It should be noted that, in a case that the third UE detects that the identifier of the at least one target UE that is carried in the direct communication request message does not include the identifier of the third UE, the third UE dost not reply to the direct communication request message (that is, the third UE does not send the direct communication accept message to the first UE).

In this embodiment of this disclosure, the identifier of the at least one target UE carried in the direct communication request message can identify target UE with which the first UE needs to establish a PC5 link. Therefore, the first UE can establish a better PC5 link.

It should be noted that, in the foregoing first scenario, in this embodiment of this disclosure, the second UE may further determine, with reference to information that is in the identifier of the at least one target UE and that is different from the identifier of the second UE, whether to send the direct communication accept message to the first UE. This may be specifically determined according to an actual usage requirement, and is not limited in this embodiment of this disclosure.

The direct communication request message further carries an identifier of a first service. The identifier of the first service is used to indicate the first service. The target UE is specifically UE that is in the at least one target UE and that needs to transmit the first service.

For example, step 203a may be specifically implemented by using the following step 203a1.

Step 203a1. In a case that the identifier of the at least one target UE includes the identifier of the second UE, and the second UE needs to transmit the first service, the second UE sends the direct communication accept message to the first UE.

It may be understood that, in a case that the second UE detects that the direct communication accept message carries the identifier of the at least one target UE and the identifier of the first service, detects that the identifier of the at least one target UE includes the identifier of the second UE, and determines that the second UE needs to transmit the first service (that is, the second UE is a target UE), the second UE sends the direct communication accept message to the first UE.

It should be noted that, in a case that the third UE detects that the identifier of the at least one target UE does not include the identifier of the third UE, and/or, determines that the third UE does not need to transmit the first service, the third UE does not reply to the direct communication request message.

In this embodiment of this disclosure, the identifier of the at least one target UE and the identifier of the first service that are carried in the direct communication request message can further identify the target UE with which the first UE needs to establish the PC5 link. Therefore, the first UE can establish a better PC5 link.

The direct communication request message further carries an identifier of a first service. The identifier of the first service is used to indicate the first service. The direct communication request message is specifically used to request the establishment of the PC5 link with the target UE. The target UE is UE that needs to transmit the first service.

Step <NUM> is specifically implemented by using the following step 203b.

In a case that the second UE needs to transmit the first service, the second UE sends the direct communication accept message to the first UE.

It may be understood that, in a case that the second UE detects that the direct communication request message carries the identifier of the first service, and the second UE needs to transmit the first service, the second UE sends the direct communication accept message to the first UE.

It should be noted that, in a case that the third UE detects that the direct communication request message carries the identifier of the first service, but the third UE does not need to transmit the first service, the third UE does not reply to the direct communication request message.

In this embodiment of this disclosure, the identifier of the first service carried in the direct communication request message can further identify the target UE with which the first UE needs to establish the PC5 link, and help UE (for example, the second UE) that receives the direct communication request message to determine, based on the identifier of the first service, whether to reply to the direct communication request message. Therefore, the first UE can establish a better PC5 link.

Optionally, the direct communication accept message further carries the identifier of the first service, where the direct communication accept message is specifically used to accept establishment of a PC5 link with the first UE for transmitting the first service.

It may be understood that, the direct communication accept message further carries the identifier of the first service, which can clearly indicate that the second UE accepts the establishment of the PC5 link with the first UE for transmitting the first service, helping the first UE establish the PC5 link.

It should be noted that, in the foregoing second scenario, in this embodiment of this disclosure, the second UE may further determine, with reference to information that is different from the identifier of the first service, whether to send the direct communication accept message to the first UE. This may be specifically determined according to an actual usage requirement, and is not limited in this embodiment of this disclosure.

With reference to <FIG>, as shown in <FIG>, after step <NUM>, the method for PC5 link establishment provided in this embodiment of this disclosure further includes the following step <NUM> and step <NUM>.

Step <NUM>. The first UE saves an association relationship among a first link identifier, an identifier of the first UE, an identifier of the second UE, and an identifier of a first service.

The first link identifier is used to indicate the PC5 link (hereinafter referred to as first link) established between the first UE and the second UE.

The first link identifier is an identifier generated by the first UE according to its own requirements to indicate the PC5 link established between the first UE and the second UE. For a specific generation method, refer to any related art. This is not limited in this embodiment of this disclosure.

According to the present invention, the first UE saves the association relationship (hereinafter referred to as first association relationship) among the first link identifier, the identifier of the first UE, the identifier of the second UE, and the identifier of the first service in text of the first link in the first UE. For a format of the link text, refer to any related art. Optionally, the first association relationship may be specifically an association relationship among the first link identifier, the identifier of the first UE, the identifier of the second UE, the identifier of the first service, the layer <NUM> address of the first UE, and the layer <NUM> address of the second UE.

The first UE saves the first association relationship, to identify the second UE more conveniently, thereby helping the first UE establish the PC5 link with the second UE.

Step <NUM>. The second UE saves an association relationship among a target link identifier, the identifier of the first UE, the identifier of the second UE, and the identifier of the first service.

The target link identifier is used to indicate the PC5 link (the same as the first link in step <NUM>) established between the first UE and the second UE.

The target link identifier is an identifier generated by the second UE according to its own requirements to indicate the PC5 link established between the first UE and the second UE. For a specific generation method, refer to any related art. This is not limited in this embodiment of this disclosure.

According to the present invention, the second UE saves a the association relationship (hereinafter referred to as second association relationship) among the target link identifier, the identifier of the first UE, the identifier of the second UE, and the identifier of the first service in text of the first link in the second UE. For a format of the link text, refer to any related art. Optionally, the second association relationship may be specifically an association relationship among the target link identifier, the identifier of the first UE, the identifier of the second UE, the identifier of the first service, the layer <NUM> address of the first UE, and the layer <NUM> address of the second UE.

It should be noted that, the first link identifier may be the same as or different from the target link identifier. This may be specifically determined according to an actual usage requirement, and is not limited in this embodiment of this disclosure.

It should be noted that step <NUM> is executed after step <NUM>. However, neither an execution sequence of step <NUM> and step <NUM> nor an execution sequence of step <NUM> and step <NUM> is limited in this embodiment of this disclosure. For example, the execution sequence of step <NUM> and step <NUM> is not limited. Step <NUM> may be executed before or after step <NUM>, or step <NUM> and step <NUM> may be executed simultaneously.

The second UE saves the second association relationship, to identify the first UE more conveniently. Therefore, the second UE can better establish the PC5 link with the first UE.

The following describes in detail specific establishment processes of the two PC5 links provided in this embodiment of this disclosure by using an example in which UE <NUM> (the first UE) establishes the PC5 links with UE <NUM> (the second UE) and UE <NUM> (the third UE) respectively and the identifier of the UE is the application layer ID of the UE.

The specific establishment process of the first PC5 link is as follows (please note that in the following the application layer ID is mentioned as an example of the identifier of the first or second UE; however, according to the invention, said identifier of an UE must be either the IMSI of the UE or the PEI of the UE): <NUM>. In a case that a V2X application layer of UE <NUM> provides an application layer ID of UE <NUM> and an application layer ID of UE <NUM>, UE <NUM> sends the direct communication request message through broadcasting, where the direct communication request message carries the identifier of the first service, the layer <NUM> address of UE <NUM>, the application layer ID of UE <NUM>, the application layer ID of UE <NUM>, and the application layer ID of UE <NUM>. After receiving the direct communication request message sent by UE <NUM>, UE <NUM> detects that the direct communication request message carries the application layer ID of UE <NUM>, and sends to UE <NUM> the direct communication accept message carrying the identifier of the first service, the layer <NUM> address of UE <NUM>, and the application layer ID of UE <NUM>. After receiving the direct communication request message sent by UE <NUM>, UE <NUM> does not send the direct communication accept message to UE <NUM>, although it detects that the direct communication request message carries the application layer ID of UE <NUM>. After receiving the direct communication request message sent by UE <NUM>, UE <NUM> does not send a direct communication accept message to UE <NUM> because it detects that the direct communication request message does not carry an application layer ID of UE <NUM>. UE <NUM> creates and saves text (hereinafter referred to as text <NUM>) of a PC5 link (hereinafter referred to as PC5 link <NUM>) used to transmit the first service with UE <NUM> (the first association relationship among identifier <NUM> of PC5 link <NUM>, the layer <NUM> address of UE <NUM>, the layer <NUM> address of UE <NUM>, the identifier of the first service, the application layer ID of UE <NUM>, and the application layer ID of UE <NUM> is stored in text <NUM>, where identifier <NUM> of PC5 link <NUM> is generated by UE <NUM>). UE <NUM> creates and saves text (hereinafter referred to as text <NUM>) of PC5 link <NUM> (the second association relationship among identifier <NUM> of PC5 link <NUM>, the layer <NUM> address of UE <NUM>, the layer <NUM> address of UE <NUM>, the identifier of the first service, the application layer ID of UE <NUM>, and the application layer ID of UE <NUM> is stored in text <NUM>, where identifier <NUM> of PC5 link <NUM> is generated by UE <NUM>, and may be different from identifier <NUM> of PC5 link <NUM>). After UE <NUM> creates text <NUM> and UE <NUM> creates text <NUM>, PC5 link <NUM> between UE <NUM> and UE <NUM> is successfully established, and UE <NUM> and UE <NUM> can transmit the first service through PC5 link <NUM>.

The specific establishment process of the second PC5 link is as follows: <NUM>. In a case that UE <NUM> does not obtain any UE identifier information through a V2X application layer, UE <NUM> sends the direct communication request message through broadcasting, where the direct communication request message carries the identifier of the first service, the layer <NUM> address of UE <NUM>, and the application layer ID of UE <NUM>. If UE <NUM> needs to transmit the first service after receiving the direct communication request message, UE <NUM> sends to UE <NUM> the direct communication accept message carrying the identifier of the first service, the layer <NUM> address of UE <NUM>, and the application layer ID of UE <NUM>. If UE <NUM> does not need to transmit the first service after receiving the direct communication request message sent by UE <NUM>, UE <NUM> does not send a direct communication accept message to UE <NUM>. UE <NUM> creates and saves text (hereinafter referred to as text <NUM>) of a PC5 link (hereinafter referred to as PC5 link <NUM>) used to transmit the first service with UE <NUM> (the first association relationship among identifier <NUM> of PC5 link <NUM>, the layer <NUM> address of UE <NUM>, the layer <NUM> address of UE <NUM>, the identifier of the first service, the application layer ID of UE <NUM>, and the application layer ID of UE <NUM> is stored in text <NUM>, where identifier <NUM> of PC5 link <NUM> is generated by UE <NUM>). UE <NUM> creates and saves text (hereinafter referred to as text <NUM>) of PC5 link <NUM> (the second association relationship among identifier <NUM> of PC5 link <NUM>, the layer <NUM> address of UE <NUM>, the layer <NUM> address of UE <NUM>, the identifier of the first service, the application layer ID of UE <NUM>, and the application layer ID of UE <NUM> is stored in text <NUM>, where identifier <NUM> of PC5 link <NUM> is generated by UE <NUM>, and may be different from identifier <NUM> of PC5 link <NUM>). After UE <NUM> creates text <NUM> and UE <NUM> creates text <NUM>, PC5 link <NUM> between UE <NUM> and UE <NUM> is successfully established, and UE <NUM> and UE <NUM> can transmit the first service through PC5 link <NUM>.

As shown in <FIG>, an embodiment of this disclosure provides UE <NUM>. The UE <NUM> is first UE, and includes a sending module <NUM> and a receiving module <NUM>. The sending module <NUM> is configured to send a direct communication request message, where the direct communication request message carries an identifier of the first UE, and is used to request establishment of a PC5 link. The receiving module <NUM> is configured to receive a direct communication accept message sent by second UE, where the direct communication accept message carries an identifier of the second UE, and is used to accept the establishment of the PC5 link with the first UE.

Optionally, the direct communication request message further carries an identifier of at least one target UE, where the direct communication request message is specifically used to request establishment of a PC5 link with the at least one target UE.

The direct communication request message further carries an identifier of a first service, where the direct communication request message is specifically used to request establishment of a PC5 link with UE that needs to transmit the first service.

The UE <NUM> further includes a saving module <NUM>. The saving module <NUM> is configured to: after the receiving module <NUM> receives the direct communication accept message sent by the second UE, save an association relationship among a first link identifier, the identifier of the first UE, the identifier of the second UE, and the identifier of the first service, where the first link identifier is used to indicate the PC5 link established between the first UE and the second UE.

The direct communication accept message further carries the identifier of the first service, where the direct communication accept message is specifically used to accept establishment of a PC5 link with the first UE for transmitting the first service.

According to the invention, the identifier of the first UE is either an IMSI of the first UE, or a PEI of the first UE; and the identifier of the second UE is either an IMSI of the second UE, or a PEI of the second UE.

The terminal device provided in this embodiment of this disclosure can implement the process in the foregoing embodiment. To avoid repetition, details are not described herein again.

An embodiment of this disclosure provides UE. The UE may be first UE. The first UE may send a direct communication request message, and receive a direct communication accept message sent by second UE, where the direct communication request message carries an identifier of the first UE, and is used to request establishment of a PC5 link, and the direct communication accept message carries an identifier of second UE, and is used to accept the establishment of the PC5 link with the first UE. In this solution, because the direct communication request message carries the identifier that uniquely identifies the first UE, and the direct communication accept message carries the identifier that uniquely identifies the second UE, the first UE and the second UE can recognize each other. This not only ensures that the PC5 link can be successfully established between the first UE and the second UE, but also ensures that only one PC5 link for a same service is established between the first UE and the second UE. In this way, a PC5 link between UEs can be well established.

As shown in <FIG>, an embodiment of this disclosure provides UE <NUM>. The UE <NUM> is second UE, and includes a receiving module <NUM> and a sending module <NUM>. The receiving module <NUM> is configured to receive a direct communication request message sent by first UE, where the direct communication request message carries an identifier of the first UE, and is used to request establishment of a PC5 link. The sending module <NUM> is configured to send a direct communication accept message to the first UE, where the direct communication accept message carries an identifier of the second UE, and is used to accept the establishment of the PC5 link with the first UE.

Optionally, the direct communication request message further carries an identifier of at least one target UE, and the sending module <NUM> is specifically configured to: in a case that the identifier of the at least one target UE includes the identifier of the second UE, send the direct communication accept message to the first UE.

The direct communication request message further carries an identifier of a first service, and the sending module <NUM> is specifically configured to: in a case that the second UE needs to transmit the first service, send the direct communication accept message to the first UE.

The UE <NUM> further includes a saving module <NUM>. The saving module <NUM> is configured to: after the receiving module <NUM> receives the direct communication request message sent by the first UE, save an association relationship among a target link identifier, the identifier of the first UE, the identifier of the second UE, and the identifier of the first service, where the target link identifier is used to indicate the PC5 link established between the first UE and the second UE.

An embodiment of this disclosure provides UE. The UE may be second UE. The second UE may receive a direct communication request message sent by first UE, and send a direct communication accept message to the first UE, where the direct communication request message carries an identifier of the first UE, and is used to request establishment of a PC5 link, and the direct communication accept message carries an identifier of the second UE, and is used to accept the establishment of the PC5 link with the first UE. In this solution, because the direct communication request message carries the identifier that uniquely identifies the first UE, and the direct communication accept message carries the identifier that uniquely identifies the second UE, the first UE and the second UE can recognize each other. This not only ensures that the PC5 link can be successfully established between the first UE and the second UE, but also ensures that only one PC5 link for a same service is established between the first UE and the second UE. In this way, a PC5 link between UEs can be well established.

<FIG> is a schematic structural diagram of hardware of UE according to an embodiment of this disclosure. The UE <NUM> includes but is not limited to: a radio frequency unit <NUM>, a network module <NUM>, an audio output unit <NUM>, an input unit <NUM>, a sensor <NUM>, a display unit <NUM>, a user input unit <NUM>, an interface unit <NUM>, a memory <NUM>, a processor <NUM>, a power supply <NUM>, and the like. A person skilled in the art may understand that a structure of the UE <NUM> shown in <FIG> does not constitute a limitation on the UE, and the UE <NUM> may include more or fewer components than those shown in the figure, or some components may be combined, or there may be a different component arrangement. In this embodiment of this disclosure, the UE <NUM> includes but is not limited to: a mobile phone, a tablet computer, a notebook computer, a palmtop computer, a vehicle-mounted UE, a wearable device, a pedometer, or the like.

The radio frequency unit <NUM> is configured to: send a direct communication request message, where the direct communication request message carries an identifier of first UE, and is used to request establishment of a PC5 link; and receive a direct communication accept message sent by second UE, where the direct communication accept message carries an identifier of the second UE, and is used to accept the establishment of the PC5 link with the first UE.

Alternatively, the radio frequency unit <NUM> is configured to: receive a direct communication request message sent by first UE, where the direct communication request message carries an identifier of the first UE, and is used to request establishment of a PC5 link; and send a direct communication accept message to the first UE, where the direct communication accept message carries an identifier of the second UE, and is used to accept the establishment of the PC5 link with the first UE.

It should be understood that, in this embodiment of this disclosure, the radio frequency unit <NUM> may be configured to transmit and receive a signal in an information transmitting/receiving or call process. Specifically, the radio frequency unit <NUM> receives downlink data from a base station and transmits the downlink data to the processor <NUM> for processing; and transmits uplink data to the base station. Generally, the radio frequency unit <NUM> includes but is not limited to an antenna, at least one amplifier, a transceiver, a coupler, a low noise amplifier, a duplexer, and the like. In addition, the radio frequency unit <NUM> may also communicate with a network and another device via a wireless communications system.

The UE <NUM> provides the user with wireless broadband Internet access by using the network module <NUM>, for example, helps the user send or receive an email, browse a web page, access streaming media, and the like.

The audio output unit <NUM> may convert audio data received by the radio frequency unit <NUM> or the network module <NUM> or stored in the memory <NUM> into an audio signal and output the audio signal as a sound. In addition, the audio output unit <NUM> may further provide an audio output (for example, a call signal reception sound or a message reception sound) related to a specific function performed by the UE <NUM>. The audio output unit <NUM> includes a speaker, a buzzer, a receiver, and the like.

The input unit <NUM> is configured to receive an audio or video signal. The input unit <NUM> may include a graphics processing unit (Graphics Processing Unit, GPU) <NUM> and a microphone <NUM>. The graphics processing unit <NUM> processes image data of a static picture or a video obtained by an image capture apparatus (for example, a camera) in an image capture mode or a video capture mode. A processed image frame may be displayed on the display unit <NUM>. An image frame processed by the graphics processing unit <NUM> may be stored in the memory <NUM> (or another storage medium) or transmitted by the radio frequency unit <NUM> or the network module <NUM>. The microphone <NUM> can receive sounds and process such sounds into audio data. The processed audio data may be converted in a call mode into a format that can be sent by the radio frequency unit <NUM> to a mobile communication base station for outputting.

The UE <NUM> further includes at least one sensor <NUM>, for example, an optical sensor, a motion sensor, and another sensor. Specifically, the optical sensor includes an ambient light sensor and a proximity sensor, where the ambient light sensor can adjust luminance of the display panel <NUM> based on brightness of ambient light, and the proximity sensor can turn off the display panel <NUM> and/or backlight when the UE <NUM> is moved to an ear. As a type of motion sensor, an accelerometer sensor can detect magnitudes of accelerations in all directions (usually three axes), can detect a magnitude and a direction of gravity when the mobile phone is in a static state, and can be applied to UE posture recognition (such as screen switching between portrait and landscape, related games, and magnetometer posture calibration), functions related to vibration recognition (such as pedometer and tapping), and the like. The sensor <NUM> may also include a fingerprint sensor, a pressure sensor, an iris sensor, a molecular sensor, a gyroscope, a barometer, a hygrometer, a thermometer, an infrared sensor, and the like.

The display unit <NUM> is configured to display information input by the user or information provided to the user.

The user input unit <NUM> may be configured to receive input digit or character information and generate key signal input related to user setting and function control of the UE <NUM>. Specifically, the user input unit <NUM> includes a touch panel <NUM> and other input devices <NUM>. The touch panel <NUM> is also referred to as a touchscreen, and may collect a touch operation of the user on or near the touch panel (for example, an operation performed on or near the touch panel <NUM> by the user by using any appropriate object or accessory such as a finger or a stylus). The touch panel <NUM> may include two parts: a touch detection apparatus and a touch controller. The touch detection apparatus detects a touch orientation of the user, detects a signal brought by the touch operation, and transmits the signal to the touch controller. The touch controller receives touch information from the touch detection apparatus, converts the touch information into touch point coordinates, transmits the touch point coordinates to the processor <NUM>, and receives and executes a command transmitted by the processor <NUM>. In addition, the touch panel <NUM> may be implemented in a plurality of forms, for example, as a resistive, capacitive, infrared, or surface acoustic wave touch panel. In addition to the touch panel <NUM>, the user input unit <NUM> may further include other input devices <NUM>. Specifically, the other input devices <NUM> may include but are not limited to a physical keyboard, a function key (for example, a volume control key or a power on/off key), a trackball, a mouse, and a joystick.

Further, the touch panel <NUM> may cover the display panel <NUM>. When detecting a touch operation on or near the touch panel <NUM>, the touch panel <NUM> transmits the touch operation to the processor <NUM> for determining a type of the touch event. Then, the processor <NUM> provides a corresponding visual output on the display panel <NUM> based on the type of the touch event. Although in <FIG>, the touch panel <NUM> and the display panel <NUM> act as two separate parts to implement input and output functions of the UE <NUM>, in some embodiments, the touch panel <NUM> and the display panel <NUM> may be integrated to implement the input and output functions of the UE <NUM>. This is not specifically limited herein.

The interface unit <NUM> is an interface connecting an external apparatus to the UE <NUM>. For example, the external apparatus may include a wired or wireless headphone port, an external power supply (or battery charger) port, a wired or wireless data port, a memory card port, a port for connecting an apparatus with an identification module, an audio input/output (I/O) port, a video I/O port, a headset port, or the like. The interface unit <NUM> may be configured to receive input (for example, data information and power) from the external apparatus, and transmit the received input to one or more elements of the UE <NUM>, or may be configured to transmit data between the UE <NUM> and the external apparatus.

The memory <NUM> may be configured to store software programs and various data. The memory <NUM> may mainly include a program storage area and a data storage area. The program storage area may store an operating system, an application program required for at least one function (for example, a sound play function and an image play function), and the like. The data storage area may store data created based on use of the mobile phone (for example, audio data and a phone book), and the like. In addition, the memory <NUM> may include a high-speed random access memory, and may further include a non-volatile memory such as a disk storage device, a flash memory device, or another volatile solid-state storage device.

The processor <NUM> is a control center of the UE <NUM>, and is connected to all components of the UE <NUM> by using various interfaces and lines. By running or executing a software program and/or module that is stored in the memory <NUM> and calling data stored in the memory <NUM>, the processor <NUM> executes various functions of the UE <NUM> and processes data, so as to perform overall monitoring on the UE <NUM>. The processor <NUM> may include one or more processing units. Optionally, the processor <NUM> may integrate an application processor and a modem processor. The application processor mainly processes an operating system, a user interface, an application program, and the like. The modem processor mainly processes wireless communication. It can be understood that the modem processor may alternatively be not integrated in the processor <NUM>.

The UE <NUM> may further include the power supply <NUM> (for example, a battery) supplying power to each component. Optionally, the power supply <NUM> may be logically connected to the processor <NUM> by using a power management system, so that functions such as charge and discharge management and power consumption management are implemented by using the power management system.

In addition, the UE <NUM> includes some function modules that are not shown, details of which are not described herein.

Optionally, an embodiment of this disclosure further provides UE, where the UE is first UE, and the UE includes the processor <NUM> and the memory <NUM> that are shown in <FIG>, and a computer program that is stored in the memory <NUM> and capable of running on the processor <NUM>. When the computer program is executed by the processor <NUM>, the processes of the foregoing method embodiments are implemented, with the same technical effects achieved. To avoid repetition, details are not described again herein.

Optionally, an embodiment of this disclosure further provides UE, where the UE is second UE, and the UE includes the processor <NUM> and the memory <NUM> that are shown in <FIG>, and a computer program that is stored in the memory <NUM> and capable of running on the processor <NUM>. When the computer program is executed by the processor <NUM>, the processes of the foregoing method embodiments are implemented, with the same technical effects achieved. To avoid repetition, details are not described again herein.

An embodiment of this disclosure further provides a communications system. The communications system includes the first UE and the second UE that are provided in the foregoing embodiments.

An embodiment of this disclosure further provides a computer-readable storage medium, where the computer-readable storage medium stores a computer program. When the computer program is executed by the processor <NUM> shown in <FIG>, the processes of the foregoing method embodiments are implemented, with the same technical effects achieved. To avoid repetition, details are not described herein again. The computer-readable storage medium may be a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), a magnetic disk, an optical disc, or the like.

It should be noted that the terms "comprise", "include", or any of their variants in this specification are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that includes a list of elements includes not only those elements but also 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 the existence of other identical elements in the process, method, article, or apparatus that includes the element.

According to the description of the foregoing implementations, persons skilled in the art can clearly understand that the method in the foregoing embodiments may be implemented by software on a necessary universal hardware platform or by hardware only. In most cases, the former is a more preferred implementation though. Based on such an understanding, the technical solutions of this disclosure essentially, or the part contributing to the related art may be implemented in a form of a software product. The computer software product is stored in a storage medium (for example, a ROM/RAM, a magnetic disk, or an optical disc), and includes several instructions for instructing a terminal device (which may be a mobile phone, a computer, a server, an air conditioner, a network device, or the like) to perform the method described in the embodiments of this disclosure.

Claim 1:
A method for PC5 link establishment, performed by first user equipment, UE, and comprising:
sending (<NUM>) a direct communication request message, wherein the direct communication request message carries an identifier of the first UE, and is used to request establishment of a PC5 link; and
receiving (<NUM>) a direct communication accept message sent by second UE, wherein the direct communication accept message carries an identifier of the second UE, and is used to accept the establishment of the PC5 link with the first UE;
wherein the identifier of the first UE is an international mobile subscriber identity, IMSI, of the first UE, or a permanent equipment identifier, PEI, of the first UE; and
the identifier of the second UE is an IMSI of the second UE, or a PEI of the second UE;
wherein the direct communication request message further carries an identifier of a first service, the direct communication request message is specifically used to request establishment of a PC5 link with UE that needs to transmit the first service;
wherein
after the receiving (<NUM>) a direct communication accept message sent by second UE, the method further comprises:
saving (<NUM>) an association relationship among a first link identifier, the identifier of the first UE, the identifier of the second UE, and the identifier of the first service, wherein the first link identifier is used to indicate the PC5 link established between the first UE and the second UE.