CN113411911B - Identification updating method and equipment - Google Patents
Identification updating method and equipment Download PDFInfo
- Publication number
- CN113411911B CN113411911B CN202010188363.8A CN202010188363A CN113411911B CN 113411911 B CN113411911 B CN 113411911B CN 202010188363 A CN202010188363 A CN 202010188363A CN 113411911 B CN113411911 B CN 113411911B
- Authority
- CN
- China
- Prior art keywords
- identification
- update
- indication information
- updating
- identifier
- Prior art date
- Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
- Active
Links
Images
Classifications
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/10—Connection setup
- H04W76/11—Allocation or use of connection identifiers
-
- H—ELECTRICITY
- H04—ELECTRIC COMMUNICATION TECHNIQUE
- H04W—WIRELESS COMMUNICATION NETWORKS
- H04W76/00—Connection management
- H04W76/30—Connection release
Landscapes
- Engineering & Computer Science (AREA)
- Computer Networks & Wireless Communication (AREA)
- Signal Processing (AREA)
- Mobile Radio Communication Systems (AREA)
Abstract
The embodiment of the invention discloses a method and equipment for updating an identifier, which solve the problem that communication is easy to interrupt because the trigger reasons of an initiating terminal equipment and a target terminal equipment for the updating process of a PC5 unicast link identifier are inconsistent. The method may be performed by an originating terminal equipment, comprising: sending a PC5 unicast link identification update request message; wherein, in case that the PC5 unicast link identification update request message includes indication information, the indication information is used to indicate whether the target terminal device updates the identification.
Description
Technical Field
The embodiment of the invention relates to the field of communication, in particular to a method and equipment for updating an identifier.
Background
The introduction of the PC5 unicast link identification update procedure mainly takes into account the privatization (privacy) problem of the terminal device, with the aim of preventing the identification and tracking by other terminal devices or third party devices by updating the identification (e.g., application layer identification) of the terminal device.
In the related art, the triggering of the PC5 unicast link identifier updating process may not be caused by the privatization problem, for example, the application layer temporary indication identifier updating, or the layer two ID collision problem, etc., all trigger the PC5 unicast link identifier updating process.
For the target terminal device, it cannot identify whether the PC5 unicast link identifier update process triggered by the originating terminal device is triggered by the privatization problem, so that it cannot determine whether the identifier of the target terminal device needs to be updated. If the originating terminal device triggers the PC5 unicast link identifier update process due to the privatization problem and the target terminal device does not update its own identifier, the originating terminal device will release the established PC5 unicast link, resulting in unnecessary communication interruption.
Disclosure of Invention
The embodiment of the invention aims to provide an identification updating method and equipment, which solve the problem that communication interruption is easy to occur due to inconsistent understanding of trigger reasons of an initiating terminal device and a target terminal device to a PC5 unicast link identification updating process.
In a first aspect, there is provided an identifier updating method, the method being performed by an originating terminal device, the method comprising:
sending a PC5 unicast link identification update request message;
and under the condition that the PC5 unicast link identification updating request message comprises indication information, the indication information is used for indicating whether the target terminal equipment updates the identification.
In a second aspect, there is provided an identifier updating method, the method being performed by a target end terminal device, the method comprising:
receiving a PC5 unicast link identification update request message;
and under the condition that the indication information is included in the unicast link identification updating request message of the PC5, determining whether to update the identification according to the indication information.
In a third aspect, there is provided a terminal device comprising:
the sending module is used for sending a PC5 unicast link identification update request message;
and under the condition that the PC5 unicast link identification updating request message comprises indication information, the indication information is used for indicating whether the target terminal equipment updates the identification.
In a fourth aspect, there is provided a terminal device comprising:
the receiving module is used for receiving the update request message of the PC5 unicast link identification;
and the identifier updating module is used for determining whether to update the identifier according to the indication information when the indication information is included in the unicast link identifier updating request message of the PC 5.
In a fifth aspect, there is provided a terminal device comprising a processor, a memory and a computer program stored on the memory and executable on the processor, the computer program implementing the method of updating an identity according to any one of the first and second aspects when executed by the processor.
In a sixth aspect, there is provided a computer readable storage medium having stored thereon a computer program which, when executed by a processor, implements the method of updating an identity according to any one of the first and second aspects.
In the embodiment of the invention, the indication information can be carried in the PC5 unicast link identification update request message, and the indication information is used for indicating whether the target terminal equipment updates the identification, so that the problem that communication is interrupted easily due to inconsistent understanding of trigger reasons of the initiating terminal equipment and the target terminal equipment to the PC5 unicast link identification update process is solved, and the communication effectiveness is improved.
Drawings
The accompanying drawings, which are included to provide a further understanding of the application and are incorporated in and constitute a part of this application, illustrate embodiments of the application and together with the description serve to explain the application and do not constitute an undue limitation to the application. In the drawings:
FIG. 1 is a schematic flow chart diagram of a method of identity updating in accordance with one embodiment of the invention;
FIG. 2 is a schematic flow chart of an identity updating method according to another embodiment of the invention;
FIG. 3 is a schematic flow chart of an identity updating method according to yet another embodiment of the present invention;
FIG. 4 is a schematic flow chart diagram of an identity updating method according to yet another embodiment of the present invention;
FIG. 5 is a schematic flow chart diagram of an identity updating method according to a next embodiment of the present invention;
fig. 6 is a schematic structural view of a terminal device according to an embodiment of the present invention;
fig. 7 is a schematic structural view of a terminal device according to another embodiment of the present invention;
fig. 8 is a schematic structural view of a terminal device according to still another embodiment of the present invention.
Detailed Description
For the purposes, technical solutions and advantages of the present application, the technical solutions of the present application will be clearly and completely described below with reference to specific embodiments of the present application and corresponding drawings. It will be apparent that the described embodiments are only some, but not all, of the embodiments of the present application. All other embodiments, which can be made by one of ordinary skill in the art without undue burden from the present disclosure, are within the scope of the present disclosure. "and/or" in various embodiments of the present description means at least one of the former and latter.
It should be understood that the technical solution of the embodiment of the present invention may be applied to various communication systems, for example: a long term evolution (Long Term Evolution, LTE) system, an LTE frequency division duplex (Frequency Division Duplex, FDD) system, an LTE time division duplex (Time Division Duplex, TDD), a universal mobile telecommunications system (Universal Mobile Telecommunication System, UMTS) or worldwide interoperability for microwave access (Worldwide Interoperability for Microwave Access, wiMAX) telecommunications system, a 5G system, or a New Radio (NR) system, an LTE sidelink system, an NR sidelink system, or a subsequent evolution telecommunications system.
In an embodiment of the present invention, the Terminal device may include, but is not limited to, a Mobile Station (MS), a Mobile Terminal (Mobile Terminal), a Mobile phone (Mobile phone), a User Equipment (UE), a handset (handset), a portable device (portable Equipment), a vehicle (vehicle), and the like, and may communicate with one or more core networks via a radio access network (Radio Access Network, RAN), for example, the Terminal device may be a Mobile phone (or referred to as a "cellular" phone), a computer with a wireless communication function, and the like, and the Terminal device may also be a portable, pocket, hand-held, computer-built-in, or vehicle-mounted Mobile device.
As shown in fig. 1, one embodiment of the present invention provides an identification updating method 100, which can be performed by a terminal device, in other words, by software or hardware installed in the terminal device, the method comprising the steps of:
s102: and sending a PC5 unicast link identification updating request message, wherein the indication information is used for indicating whether the target terminal equipment updates the identification or not when the indication information is included in the PC5 unicast link identification updating request message.
In this embodiment, the transmitting end terminal device may send a PC5 unicast link identifier update request (PC 5 unicast link Identifier update request) message to the target end terminal device, where the PC5 unicast link identifier update request message includes indication information, where the indication information is used to indicate whether the target end terminal device updates an identifier, for example, the indication information may be used to indicate that the target end terminal device updates an identifier; or, the indication information may be used to indicate that the target terminal device does not need to update the identifier; or, the indication information may be used to instruct the target terminal device to determine whether to update the identifier according to a preset rule.
Thus, after receiving the request message for updating the unicast link identification of the PC5, the target terminal device can update the identification of the target terminal device according to the indication information or does not need to update the identification of the target terminal device.
Optionally, embodiment 100 may further include: if the PC5 unicast link identification updating request message does not include the indication information, the target terminal equipment determines whether to update the identification according to a preset rule. Or, if the PC5 unicast link identification update request message does not include the indication information, the PC5 unicast link identification update request message may indicate the target terminal device to determine whether to update the identification according to a preset rule.
The preset rule may be protocol contract information, or information of (pre) configuration, etc. Specific examples are protocol conventions: if the target terminal equipment receives a PC5 unicast link identification updating request message which does not contain the indication information, the target terminal equipment does not need to update the identification of the target terminal equipment; for another example, the protocol convention: if the target terminal equipment receives the PC5 unicast link identification updating request message which does not contain the indication information, the target terminal equipment updates the identification of the target terminal equipment.
According to the identification updating method provided by the embodiment of the invention, the indication information can be carried in the PC5 unicast link identification updating request message, and the indication information is used for indicating whether the target terminal equipment updates the identification, so that the problem that communication is interrupted easily due to inconsistent understanding of triggering reasons of the initiating terminal equipment and the target terminal equipment to the PC5 unicast link identification updating process is solved, and the communication effectiveness is improved.
Optionally, in one embodiment, embodiment 100 may further include the steps of: receiving a PC5 unicast link update accept (PC 5 unicast link Identifier update accept) message; the PC5 unicast link update acceptance message comprises an identifier updated by the target terminal equipment.
In this embodiment, after receiving the PC5 unicast link identifier update request message, the target terminal device updates its identifier according to the indication information carried by the request message, and sends a PC5 unicast link update accept message to the initiator terminal device, where the PC5 unicast link update accept message carries the identifier updated by the target terminal device.
Indeed, the PC5 unicast link update request message described above may be replaced by other similar technical terms, such as link identification update request message, unicast link identification update request message, etc
The PC5 unicast link update accept message described above may also be replaced with other similar technical terms, such as a link identification update response message, a PC5 unicast link identification update response message, and so on.
Optionally, in one embodiment, embodiment 100 may further include the steps of: sending a PC5 unicast link release request message; the PC5 unicast link release request message includes a cause value, where the cause value indicates that the target terminal device does not update its own identifier, so as to cause the originating terminal device to trigger a PC5 unicast link release process.
In this embodiment, the target end terminal device may update its own identity after receiving the PC5 unicast link identity update request message, and send a PC5 unicast link update accept message to the originating end terminal device, the PC5 unicast link update accept message may carry the updated identifier of the target terminal device, but may also be the cause of the updated identifier of the target terminal device, such as error, so that the initiating terminal device triggers the PC5 unicast link release process.
Optionally, in one embodiment, the indication information carried in the PC5 unicast link identifier update request message mentioned in the foregoing embodiments is used to indicate an identifier update type, where the identifier update type includes:
1) Privatizing configuration-triggered identifier updating; or (b)
2) The non-privatized configuration triggers an identity update, e.g., layer two Identity (ID) conflict of the originating terminal device, or the originating terminal device receives an identity update indication of the application layer.
Optionally, if the identifier update type indicated by the indication information includes an identifier update triggered by privately configured configuration, the indication information is used to indicate the target terminal device to update the identifier.
Specifically, the updated identifier of the target terminal device includes at least one of the following:
layer two identification;
safety information;
an application layer identification;
IP address or IP prefix.
In one example, the identifier that the target terminal device needs to update includes a layer two identifier and security information, and whether to update the application layer identifier and whether to update the IP address or the IP prefix are both selectable, which may depend on the implementation of the terminal device.
Optionally, if the identification update type indicated by the indication information includes an identification update triggered by a non-privatized configuration, the indication information is used for indicating the target terminal equipment to determine whether to update the identification according to a preset rule. In this example, whether the target end terminal device updates the identity may depend on the terminal device implementation in particular.
Optionally, in an embodiment, the indication information carried in the PC5 unicast link identifier update request message includes security information, that is, the security information carries an indication equivalent to an indication for indicating the target terminal device terminal to update its own identifier information. The security information may be a security algorithm, a security key, etc.
Specifically, the updated identifier of the target terminal device includes at least one of the following:
layer two identification;
safety information;
an application layer identification;
IP address or IP prefix.
In one example, the identifier that the target terminal device needs to update includes a layer two identifier and security information, and whether to update the application layer identifier and whether to update the IP address or the IP prefix are both selectable, which may depend on the implementation of the terminal device.
Optionally, if the PC5 unicast link identification update request message does not include the security information, the PC5 unicast link identification update request message is used to instruct the target terminal device to determine whether to update the identification according to a preset rule. In this example, whether the target end terminal device updates the identity may depend on the terminal device implementation in particular.
Optionally, in an embodiment, the indication information carried in the PC5 unicast link identification update request message includes identification update required information; or identify that no information is needed for the update.
If the indication information is the information needed for updating the identification, the indication information is used for indicating the target terminal equipment to update the identification; or if the indication information is the information which is not needed for updating the identification, the indication information is used for indicating the target terminal equipment to determine whether to update the identification according to a preset rule.
Specifically, the originating terminal device carries an information element of "identifier update need (identifier update required)" in the PC5 unicast link identifier update request message, and if the value of the information element is set to: "identifier update need (identifier update required)", the target terminal device updates its own identifier information.
Specifically, the updated identifier of the target terminal device includes at least one of the following:
layer two identification;
safety information;
an application layer identification;
IP address or IP prefix.
In one example, the identifier that the target terminal device needs to update includes a layer two identifier and security information, and whether to update the application layer identifier and whether to update the IP address or the IP prefix are both selectable, which may depend on the implementation of the terminal device.
In this example, after receiving the PC5 unicast link identification update request message, the target terminal device may further send a PC5 unicast link update accept (PC 5 unicast link Identifier update accept) message, where the PC5 unicast link update accept message may carry the updated identification information.
Optionally, the originating terminal device carries an information element of "identifier update need (identifier update required)" in the PC5 unicast link identifier update request message, and if the value of the information element is set to: "the identification update is not required (identifier update not required)", the target end terminal device may update its own identification information. In this example, whether the target end terminal device updates the identity may depend on the terminal device implementation in particular.
In order to describe the identifier updating method provided in the embodiment of the present invention in detail, the following description will be made with reference to several specific embodiments.
Example 1
In this embodiment, the originating terminal device (originating UE, or referred to as a transmitting UE) carries an indication of the type of the update of the identifier in the PC5 unicast link identifier update request message, and the target terminal device (target UE) determines whether to update the relevant identifier information according to the indication of the type of the update of the identifier.
As shown in fig. 2, this embodiment includes the steps of:
s202: there is an established PC5 unicast communication link between the originating UE and the target UE.
S204: the initiator UE sends a PC5 unicast link identifier update request message carrying an identifier update type indication to the target UE, where the identifier update type indication may include:
1) Privatizing configuration-triggered identifier updating; or (b)
2) The non-privatized configuration triggers an identity update. For example, the layer two ID of the originating UE collides or receives an indication of an application layer update.
In this embodiment, the above described identity update type indication contains a privately configured triggered identity update, i.e. the originating UE triggers the PC5 unicast link identity update procedure because of privateization (privacy) issues.
S206: after receiving the request message for updating the unicast link identification of the PC5, the target end UE updates the identification information of the target end UE.
The type of the identifier update in this embodiment is "privately configured triggered identifier update", and the target UE updates its own identifier information. Specifically, the target UE updates its own layer two ID and security information. Optionally, the target UE updates the application layer identifier. Optionally, the target UE updates the IP address or IP prefix information.
In other embodiments, if the identity update type is "non-privately configured triggered identity update", whether the target UE updates its own identity information depends on the UE implementation, e.g., the target UE determines whether to update its own identity information according to a protocol convention.
S208: the target UE sends a PC5 unicast link identification update accept (PC 5 unicast link Identifier update accept) message.
Alternatively, the updated identification information may be carried in the PC5 unicast link identification update accept message.
Optionally, the updated identification information may not be carried in the PC5 unicast link identification update accept message.
This embodiment assumes that the PC5 unicast link identification update accept message does not carry the updated identification information.
S210: the initiating terminal UE triggers the PC5 unicast link release process.
In this embodiment, the indication of the type of the identifier update carried by the initiating UE in the PC5 unicast link identifier update request message is "privately configured triggered identifier update"; and the PC5 unicast link identification update receiving message does not carry the identification information updated by the target end UE, so that the initiating end UE triggers the PC5 unicast link release process and carries a reason value of 'identification not updated' in the sent PC5 unicast link release request message.
In other embodiments, if the PC5 unicast link identifier update accept message carries the identifier information updated by the target UE, but the identifier information updated by the target UE is wrong, the initiating UE may trigger the PC5 unicast link release process, and the reason value carried in the sent PC5 unicast link release request message is "identifier update error".
Example two
In this embodiment, the initiating UE uses whether the PC5 unicast link identifier update request message carries security information as an option, that is, the security information carries an indication, which is used to indicate that the target UE needs to update its own identifier information. If the PC5 unicast link identification update request message does not carry security information, the target UE determines whether to update its own identification information according to terminal device implementation (UE implementation).
As shown in fig. 3, this embodiment includes the steps of:
s302: there is an established PC5 unicast communication link between the originating UE and the target UE.
S304: the initiating terminal UE sends a PC5 unicast link identification updating request message carrying security information to the target terminal UE.
S306: after receiving the request message for updating the unicast link identification of the PC5, the target end UE updates the identification information of the target end UE.
Specifically, the target UE updates its own layer two ID and security information. Optionally, the target UE updates the application layer identifier. Optionally, the target UE updates the IP address or IP prefix information.
S308: the target UE sends a PC5 unicast link identification update accept (PC 5 unicast link Identifier update accept) message.
Alternatively, the updated identification information may be carried in the PC5 unicast link identification update accept message.
Optionally, the updated identification information may not be carried in the PC5 unicast link identification update accept message.
This embodiment assumes that the PC5 unicast link identification update accept message does not carry the updated identification information.
S310: the initiating terminal UE triggers the PC5 unicast link release process.
In the embodiment, the initiating terminal UE carries security information in a PC5 unicast link identification update request message; and the PC5 unicast link identification update receiving message does not carry the identification information updated by the target end UE, so that the initiating end UE triggers the PC5 unicast link release process and carries a reason value of 'identification not updated' in the sent PC5 unicast link release request message.
In other embodiments, if the PC5 unicast link identifier update accept message carries the identifier information updated by the target UE, but the identifier information updated by the target UE is wrong, the initiating UE may trigger the PC5 unicast link release process, and the reason value carried in the sent PC5 unicast link release request message is "identifier update error".
Example III
In this embodiment, the initiator UE carries an information element of "identifier update need (identifier update required)" in the PC5 unicast link identifier update request message, and the target UE determines whether to update the relevant identifier information according to the identifier update need.
As shown in fig. 4, this embodiment includes the steps of:
s402: there is an established PC5 unicast communication link between the originating UE and the target UE.
S404: the initiator UE sends a PC5 unicast link identifier update request message carrying "identifier update required" to the target UE, where the "identifier update required" may include:
1) "identification update need (identifier update required)"; or (b)
2) "identification update need not (identifier update required)".
S406: after receiving the request message for updating the unicast link identification of the PC5, the target end UE updates the identification information of the target end UE.
This embodiment assumes that the information element of the above-described "identification update need (identifier update required)" is "identification update need (identifier update required)".
Specifically, the target UE updates its own layer two ID and security information. Optionally, the target UE updates the application layer identifier. Optionally, the target UE updates the IP address or IP prefix information.
In other embodiments, if the information element of "identity update required (identifier update required)" is "identity update not required (identifier update required)", whether the target UE updates its own identity information depends on the UE implementation, e.g., the target UE determines whether to update its own identity information according to a protocol convention.
S408: the target UE sends a PC5 unicast link identification update accept (PC 5 unicast link Identifier update accept) message.
Alternatively, the updated identification information may be carried in the PC5 unicast link identification update accept message.
Optionally, the updated identification information may not be carried in the PC5 unicast link identification update accept message.
This embodiment assumes that the PC5 unicast link identification update accept message does not carry the updated identification information.
S410: the initiating terminal UE triggers the PC5 unicast link release process.
In this embodiment, the information element carried by the initiating UE in the PC5 unicast link identifier update request message is "identifier update needed"; and the PC5 unicast link identification update receiving message does not carry the identification information updated by the target end UE, so that the initiating end UE triggers the PC5 unicast link release process and carries a reason value of 'identification not updated' in the sent PC5 unicast link release request message.
In other embodiments, if the PC5 unicast link identifier update accept message carries the identifier information updated by the target UE, but the identifier information updated by the target UE is wrong, the initiating UE may trigger the PC5 unicast link release process, and the reason value carried in the sent PC5 unicast link release request message is "identifier update error".
The method for updating the identification according to the embodiment of the present invention is described in detail above with reference to fig. 1. An identification updating method according to another embodiment of the present invention will be described in detail with reference to fig. 5. It is to be understood that the description from the target end terminal device side is the same as the description of the originating end terminal device side in the method shown in fig. 1, and the related description is omitted as appropriate to avoid repetition.
Figure 5 is a schematic diagram of an implementation flow of an identification updating method according to an embodiment of the present invention, the method can be applied to the side of the target terminal equipment. As shown in fig. 5, the method 500 includes:
s502: and receiving the unicast link identification update request message of the PC 5.
S504: in the case where the indication information is included in the PC5 unicast link identification update request message, it is determined whether to update the identification according to the indication information.
In the embodiment of the invention, the indication information can be carried in the PC5 unicast link identification update request message, and the indication information is used for indicating whether the target terminal equipment updates the identification, so that the problem that communication is interrupted easily due to inconsistent understanding of trigger reasons of the initiating terminal equipment and the target terminal equipment to the PC5 unicast link identification update process is solved, and the communication effectiveness is improved.
Optionally, as an embodiment, the indication information is used to indicate an identification update type, where the identification update type includes:
privatizing configuration-triggered identifier updating; or (b)
The non-privatized configuration triggers an identity update.
Optionally, as an embodiment, the determining whether to update the identifier according to the indication information includes:
if the identification update type indicated by the indication information comprises the identification update triggered by privately configured, determining an update identification; or (b)
And if the identification update type indicated by the indication information comprises the identification update triggered by the non-privatization configuration, determining whether to update the identification according to a preset rule.
Optionally, as an embodiment, the indication information includes security information, and determining whether to update the identifier according to the indication information includes:
and determining an update identification according to the indication information.
Optionally, as an embodiment, the method further includes:
and if the indication information is not included in the unicast link identification updating request message of the PC5, determining whether to update the identification according to a preset rule.
Optionally, as an embodiment, the indication information includes:
identifying information required for updating; or (b)
No information is needed for the identification update.
Optionally, as an embodiment, the determining whether to update the identifier according to the indication information includes:
if the indication information is the information required for the identification update, determining an update identification; or (b)
And if the indication information is the information which is not needed for updating the identification, determining whether to update the identification according to a preset rule.
Optionally, as an embodiment, if the update identifier is determined, the method further includes:
updating at least one of:
layer two identification;
safety information;
an application layer identification;
IP address or IP prefix.
Optionally, as an embodiment, the method further includes:
sending a PC5 unicast link update accept message;
wherein the PC5 unicast link update accept message includes an updated identification.
Optionally, as an embodiment, the method further includes:
receiving a PC5 unicast link release request message;
the PC5 unicast link release request message includes a cause value, where the cause value indicates that the target terminal device does not update its own identifier, so as to cause the originating terminal device to trigger a PC5 unicast link release process.
The identification updating method according to the embodiment of the present invention is described in detail above with reference to fig. 1 to 5. The terminal device according to an embodiment of the present invention will be described in detail below with reference to fig. 6.
Fig. 6 is a schematic structural diagram of a terminal device according to an embodiment of the present invention. The terminal device corresponds to the transmitting-end terminal device in the embodiment shown in fig. 1 to 4, and as shown in fig. 6, the terminal device 600 includes:
a sending module 602, configured to send a PC5 unicast link identifier update request message;
and under the condition that the PC5 unicast link identification updating request message comprises indication information, the indication information is used for indicating whether the target terminal equipment updates the identification.
In the embodiment of the invention, the indication information can be carried in the PC5 unicast link identification update request message, and the indication information is used for indicating whether the target terminal equipment updates the identification, so that the problem that communication is interrupted easily due to inconsistent understanding of trigger reasons of the initiating terminal equipment and the target terminal equipment to the PC5 unicast link identification update process is solved, and the communication effectiveness is improved.
Optionally, as an embodiment, the indication information is used to indicate an identification update type, where the identification update type includes:
privatizing configuration-triggered identifier updating; or (b)
The non-privatized configuration triggers an identity update.
Alternatively, the first and second modules may, as one embodiment,
If the identification update type indicated by the indication information comprises the identification update triggered by the privateization configuration, the indication information is used for indicating the target terminal equipment to update the identification; or (b)
If the identification update type indicated by the indication information comprises the identification update triggered by the non-privatization configuration, the indication information is used for indicating the target terminal equipment to determine whether to update the identification according to a preset rule.
Optionally, as an embodiment, the indication information includes security information, where the security information is used to indicate the update identifier of the target end terminal device.
Optionally, as an embodiment, if the indication information is not included in the PC5 unicast link identification update request message, the PC5 unicast link identification update request message is used to instruct the target terminal device to determine whether to update the identification according to a preset rule.
Optionally, as an embodiment, the indication information includes:
identifying information required for updating; or (b)
No information is needed for the identification update.
Alternatively, the first and second modules may, as one embodiment,
if the indication information is the information needed for updating the identification, the indication information is used for indicating the target terminal equipment to update the identification; or (b)
And if the indication information is the information which is not needed for updating the identification, the indication information is used for indicating the target terminal equipment to determine whether to update the identification according to a preset rule.
Optionally, as an embodiment, the updated identifier of the target end terminal device includes at least one of:
layer two identification;
safety information;
an application layer identification;
IP address or IP prefix.
Optionally, as an embodiment, the terminal device further includes a receiving module, which may be configured to:
receiving a PC5 unicast link update accept message;
the PC5 unicast link update accept message includes an updated identifier of the target terminal device.
Optionally, as an embodiment, the sending module 602 may be further configured to:
sending a PC5 unicast link release request message;
the PC5 unicast link release request message includes a cause value, where the cause value indicates that the target terminal device does not update its own identifier, so as to cause the originating terminal device to trigger a PC5 unicast link release process.
The terminal device 600 according to the embodiment of the present invention may refer to the flow of the method 100 corresponding to the embodiment of the present invention, and each unit/module in the terminal device 600 and the other operations and/or functions described above are respectively for implementing the corresponding flow in the method 100, and can achieve the same or equivalent technical effects, which are not described herein for brevity.
Fig. 7 is a schematic structural diagram of a terminal device according to an embodiment of the present invention, which corresponds to the target terminal device in the embodiment shown in fig. 5. As shown in fig. 7, the terminal device 700 includes:
a receiving module 702, configured to receive a PC5 unicast link identification update request message;
the identifier updating module 704 may be configured to determine whether to update the identifier according to the indication information when the indication information is included in the PC5 unicast link identifier update request message.
In the embodiment of the invention, the indication information can be carried in the PC5 unicast link identification update request message, and the indication information is used for indicating whether the target terminal equipment updates the identification, so that the problem that communication is interrupted easily due to inconsistent understanding of trigger reasons of the initiating terminal equipment and the target terminal equipment to the PC5 unicast link identification update process is solved, and the communication effectiveness is improved.
Optionally, as an embodiment, the indication information is used to indicate an identification update type, where the identification update type includes:
privatizing configuration-triggered identifier updating; or (b)
The non-privatized configuration triggers an identity update.
Optionally, as an embodiment, the determining, by the identifier updating module 704, whether updating the identifier is needed according to the indication information includes:
If the identification update type indicated by the indication information comprises the identification update triggered by privately configured, determining an update identification; or (b)
And if the identification update type indicated by the indication information comprises the identification update triggered by the non-privatization configuration, determining whether to update the identification according to a preset rule.
Optionally, as an embodiment, the indication information includes security information, and the determining, by the identifier updating module 704, whether to update the identifier according to the indication information includes:
and determining an update identification according to the indication information.
Optionally, as an embodiment, the identifier updating module 704 is configured to:
and if the indication information is not included in the unicast link identification updating request message of the PC5, determining whether to update the identification according to a preset rule.
Optionally, as an embodiment, the indication information includes:
identifying information required for updating; or (b)
No information is needed for the identification update.
Optionally, as an embodiment, the determining, by the identifier updating module 704, whether to update the identifier according to the indication information includes:
if the indication information is the information required for the identification update, determining an update identification; or (b)
And if the indication information is the information which is not needed for updating the identification, determining whether to update the identification according to a preset rule.
Optionally, as an embodiment, if an update identifier is determined, the identifier update module 704 is configured to update at least one of:
layer two identification;
safety information;
an application layer identification;
IP address or IP prefix.
Optionally, as an embodiment, the terminal device further includes a sending module, which may be used to:
sending a PC5 unicast link update accept message;
wherein the PC5 unicast link update accept message includes an updated identification.
Optionally, as an embodiment, the receiving module 702 may be further configured to:
receiving a PC5 unicast link release request message;
the PC5 unicast link release request message includes a cause value, where the cause value indicates that the target terminal device does not update its own identifier, so as to cause the originating terminal device to trigger a PC5 unicast link release process.
The terminal device 700 according to the embodiment of the present invention may refer to the flow of the method 500 corresponding to the embodiment of the present invention, and each unit/module in the terminal device 700 and the other operations and/or functions described above are respectively for implementing the corresponding flow in the method 500, and can achieve the same or equivalent technical effects, which are not described herein for brevity.
Various embodiments in this specification are described in an incremental manner, and each embodiment is generally described with emphasis on differences from the other embodiments, so that identical and similar parts of the various embodiments are referred to each other. For the device embodiments, the description is relatively simple, as it is substantially similar to the method embodiments, with reference to the partial description of the method embodiments being relevant.
Fig. 8 is a block diagram of a terminal device according to another embodiment of the present invention. The terminal device 800 shown in fig. 8 includes: at least one processor 801, memory 802, at least one network interface 804, and a user interface 803. The various components in terminal device 800 are coupled together by a bus system 805. It is appreciated that the bus system 805 is used to enable connected communications between these components. The bus system 805 includes a power bus, a control bus, and a status signal bus in addition to the data bus. But for clarity of illustration, the various buses are labeled as bus system 805 in fig. 8.
The user interface 803 may include, among other things, a display, a keyboard, a pointing device (e.g., a mouse, a trackball), a touch pad, or a touch screen, etc.
It will be appreciated that the memory 802 in embodiments of the invention can be either volatile memory or nonvolatile memory, or can include both volatile and nonvolatile memory. The nonvolatile Memory may be a Read-Only Memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an Electrically Erasable EPROM (EEPROM), or a flash Memory. The volatile memory may be random access memory (Random Access Memory, RAM) which acts as an external cache. By way of example, and not limitation, many forms of RAM are available, such as Static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double Data Rate SDRAM (Double Data Rate SDRAM), enhanced SDRAM (ESDRAM), synchronous DRAM (SLDRAM), and Direct RAM (DRRAM). The memory 802 of the systems and methods described in embodiments of the present invention is intended to comprise, without being limited to, these and any other suitable types of memory.
In some implementations, the memory 802 stores the following elements, executable modules or data structures, or a subset thereof, or an extended set thereof: an operating system 8021 and application programs 8022.
The operating system 8021 includes various system programs, such as a framework layer, a core library layer, a driver layer, and the like, for implementing various basic services and processing hardware-based tasks. The application 8022 includes various application programs such as a Media Player (Media Player), a Browser (Browser), and the like for realizing various application services. The program for implementing the method of the embodiment of the present invention may be contained in the application program 8022.
In the embodiment of the present invention, the terminal device 800 further includes: a computer program stored on the memory 802 and executable on the processor 801, which when executed by the processor 801 performs the steps of any one of the method embodiments 100 to 500 as follows.
The method disclosed in the above embodiment of the present invention may be applied to the processor 801 or implemented by the processor 801. The processor 801 may be an integrated circuit chip with signal processing capabilities. In implementation, the steps of the above method may be performed by integrated logic circuitry in hardware in the processor 801 or by instructions in software. The processor 801 described above may be a general purpose processor, digital signal processor (Digital Signal Processor, DSP), application specific integrated circuit (Application Specific Integrated Circuit, ASIC), field programmable gate array (Field Programmable Gate Array, FPGA) or other programmable logic device, discrete gate or transistor logic device, discrete hardware components. The disclosed methods, steps, and logic blocks in the embodiments of the present invention may be implemented or performed. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like. The steps of the method disclosed in connection with the embodiments of the present invention may be embodied directly in the execution of a hardware decoding processor, or in the execution of a combination of hardware and software modules in a decoding processor. The software modules may be located in a computer readable storage medium well known in the art such as random access memory, flash memory, read only memory, programmable read only memory, or electrically erasable programmable memory, registers, and the like. The computer readable storage medium is located in a memory 802, and the processor 801 reads information in the memory 802 and in combination with its hardware performs the steps of the above method. Specifically, the computer readable storage medium has stored thereon a computer program which, when executed by the processor 801, implements the steps of any one of the method embodiments 100 to 500 described above.
It is to be understood that the embodiments of the invention described herein may be implemented in hardware, software, firmware, middleware, microcode, or a combination thereof. For a hardware implementation, the processing units may be implemented within one or more application specific integrated circuits (Application Specific Integrated Circuits, ASIC), digital signal processors (Digital Signal Processing, DSP), digital signal processing devices (DSP devices, DSPD), programmable logic devices (Programmable Logic Device, PLD), field programmable gate arrays (Field-Programmable Gate Array, FPGA), general purpose processors, controllers, microcontrollers, microprocessors, other electronic units configured to perform the functions described herein, or a combination thereof.
For a software implementation, the techniques described in embodiments of the present invention may be implemented by modules (e.g., procedures, functions, and so on) that perform the functions described in embodiments of the present invention. The software codes may be stored in a memory and executed by a processor. The memory may be implemented within the processor or external to the processor.
The terminal device 800 can implement each process implemented by the terminal device in the foregoing embodiment, and can achieve the same or equivalent technical effects, and for avoiding repetition, a description is omitted herein.
The embodiment of the present invention further provides a computer readable storage medium, on which a computer program is stored, where the computer program when executed by a processor implements each process of any one of the foregoing method embodiments 100 to 500, and the same technical effects can be achieved, and in order to avoid repetition, a detailed description is omitted herein. Wherein the computer readable storage medium is selected from Read-Only Memory (ROM), random access Memory (Random Access Memory, RAM), magnetic disk or optical disk.
It should be noted that, in this document, the terms "comprises," "comprising," or any other variation thereof, are intended to cover a non-exclusive inclusion, such that a process, method, article, or apparatus that comprises a list of elements does not include only those elements but may include other elements not expressly listed or inherent to such process, method, article, or apparatus. Without further limitation, an element defined by the phrase "comprising one … …" does not exclude the presence of other like elements in a process, method, article, or apparatus that comprises the element.
From the above description of the embodiments, it will be clear to those skilled in the art that the above-described embodiment method may be implemented by means of software plus a necessary general hardware platform, but of course may also be implemented by means of hardware, but in many cases the former is a preferred embodiment. Based on such understanding, the technical solution of the present invention may be embodied essentially or in a part contributing to the prior art in the form of a software product stored in a storage medium (e.g. ROM/RAM, magnetic disk, optical disk) comprising instructions for causing a terminal (which may be a mobile phone, a computer, a server, an air conditioner, or a network device, etc.) to perform the method according to the embodiments of the present invention.
The embodiments of the present invention have been described above with reference to the accompanying drawings, but the present invention is not limited to the above-described embodiments, which are merely illustrative and not restrictive, and many forms may be made by those having ordinary skill in the art without departing from the spirit of the present invention and the scope of the claims, which are to be protected by the present invention.
Claims (12)
1. An identity updating method, wherein the method is performed by an originating terminal device, the method comprising:
sending a PC5 unicast link identification update request message;
wherein, when the PC5 unicast link identifier update request message includes indication information, the indication information is used to indicate whether the target terminal device updates the identifier;
the indication information is used for indicating an identification update type, and the identification update type comprises:
privatizing configuration-triggered identifier updating; or (b)
Non-privatized configuration triggered identifier updating;
if the identification update type indicated by the indication information comprises the identification update triggered by the privateization configuration, the indication information is used for indicating the target terminal equipment to update the identification;
if the identification update type indicated by the indication information comprises the identification update triggered by the non-privatization configuration, the indication information is used for indicating the target terminal equipment to determine whether to update the identification according to a preset rule;
or (b)
The indication information comprises safety information, and the safety information is used for indicating the updating identifier of the target terminal equipment;
if the indication information is not included in the PC5 unicast link identification update request message, the PC5 unicast link identification update request message is used for indicating the target terminal device to determine whether to update an identification according to a preset rule;
Or (b)
The indication information includes:
identifying information required for updating; or (b)
Identifying that no information is needed for updating;
if the indication information is the information needed for updating the identification, the indication information is used for indicating the target terminal equipment to update the identification;
if the indication information is identification update unnecessary information, the indication information is used for indicating the target terminal equipment to determine whether to update the identification according to a preset rule.
2. The method of claim 1, wherein the identity of the target end terminal device update comprises at least one of:
layer two identification;
safety information;
an application layer identification;
IP address or IP prefix.
3. The method according to claim 1, wherein the method further comprises:
receiving a PC5 unicast link update accept message;
the PC5 unicast link update accept message includes an updated identifier of the target terminal device.
4. The method according to claim 1, wherein the method further comprises:
sending a PC5 unicast link release request message;
the PC5 unicast link release request message includes a cause value, where the cause value indicates that the target terminal device does not update its own identifier, so as to cause the originating terminal device to trigger a PC5 unicast link release process.
5. An identity updating method, wherein the method is performed by a target end terminal device, the method comprising:
receiving a PC5 unicast link identification update request message;
under the condition that the PC5 unicast link identification updating request message comprises indication information, determining whether to update an identification according to the indication information;
the indication information is used for indicating an identification update type, and the identification update type comprises:
privatizing configuration-triggered identifier updating; or (b)
Non-privatized configuration triggered identifier updating;
the step of determining whether to update the identification according to the indication information comprises the following steps:
if the identification update type indicated by the indication information comprises the identification update triggered by privately configured, determining an update identification;
if the identification update type indicated by the indication information comprises the identification update triggered by the non-privatization configuration, determining whether to update the identification according to a preset rule;
or (b)
The indication information comprises safety information, and the determining whether to update the identification according to the indication information comprises the following steps:
determining an update identifier according to the indication information;
if the indication information is not included in the PC5 unicast link identification updating request message, determining whether to update the identification according to a preset rule;
Or (b)
The indication information includes:
identifying information required for updating; or (b)
Identifying that no information is needed for updating;
the step of determining whether to update the identification according to the indication information comprises the following steps:
if the indication information is the information required for the identification update, determining an update identification;
and if the indication information is the information which is not needed for updating the identification, determining whether to update the identification according to a preset rule.
6. The method of claim 5, wherein if an update identification is determined, the method further comprises:
updating at least one of:
layer two identification;
safety information;
an application layer identification;
IP address or IP prefix.
7. The method of claim 5, wherein the method further comprises:
sending a PC5 unicast link update accept message;
wherein the PC5 unicast link update accept message includes an updated identification.
8. The method of claim 5, wherein the method further comprises:
receiving a PC5 unicast link release request message;
the PC5 unicast link release request message includes a cause value, where the cause value indicates that the target terminal device does not update its own identifier, so as to cause the originating terminal device to trigger a PC5 unicast link release process.
9. A terminal device, comprising:
the sending module is used for sending a PC5 unicast link identification update request message;
wherein, when the PC5 unicast link identifier update request message includes indication information, the indication information is used to indicate whether the target terminal device updates the identifier;
the indication information is used for indicating an identification update type, and the identification update type comprises:
privatizing configuration-triggered identifier updating; or (b)
Non-privatized configuration triggered identifier updating;
if the identification update type indicated by the indication information comprises the identification update triggered by the privateization configuration, the indication information is used for indicating the target terminal equipment to update the identification;
if the identification update type indicated by the indication information comprises the identification update triggered by the non-privatization configuration, the indication information is used for indicating the target terminal equipment to determine whether to update the identification according to a preset rule;
or (b)
The indication information comprises safety information, and the safety information is used for indicating the updating identifier of the target terminal equipment;
if the indication information is not included in the PC5 unicast link identification update request message, the PC5 unicast link identification update request message is used for indicating the target terminal device to determine whether to update an identification according to a preset rule;
Or (b)
The indication information includes:
identifying information required for updating; or (b)
Identifying that no information is needed for updating;
if the indication information is the information needed for updating the identification, the indication information is used for indicating the target terminal equipment to update the identification;
and if the indication information is the information which is not needed for updating the identification, the indication information is used for indicating the target terminal equipment to determine whether to update the identification according to a preset rule.
10. A terminal device, comprising:
the receiving module is used for receiving the update request message of the PC5 unicast link identification;
the identification updating module is used for determining whether to update the identification according to the indication information when the indication information is included in the PC5 unicast link identification updating request message;
the indication information is used for indicating an identification update type, and the identification update type comprises:
privatizing configuration-triggered identifier updating; or (b)
Non-privatized configuration triggered identifier updating;
the step of determining whether to update the identification according to the indication information comprises the following steps:
if the identification update type indicated by the indication information comprises the identification update triggered by privately configured, determining an update identification;
If the identification update type indicated by the indication information comprises the identification update triggered by the non-privatization configuration, determining whether to update the identification according to a preset rule;
or (b)
The indication information comprises safety information, and the determining whether to update the identification according to the indication information comprises the following steps:
determining an update identifier according to the indication information;
if the indication information is not included in the PC5 unicast link identification updating request message, determining whether to update the identification according to a preset rule;
or (b)
The indication information includes:
identifying information required for updating; or (b)
Identifying that no information is needed for updating;
the step of determining whether to update the identification according to the indication information comprises the following steps:
if the indication information is the information required for the identification update, determining an update identification;
and if the indication information is the information which is not needed for updating the identification, determining whether to update the identification according to a preset rule.
11. A terminal device, comprising: memory, a processor and a computer program stored on the memory and executable on the processor, which when executed by the processor implements the identification updating method according to any of claims 1 to 8.
12. A computer readable storage medium, characterized in that the computer readable storage medium has stored thereon a computer program which, when executed by a processor, implements the identification updating method according to any of claims 1 to 8.
Priority Applications (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010188363.8A CN113411911B (en) | 2020-03-17 | 2020-03-17 | Identification updating method and equipment |
Applications Claiming Priority (1)
| Application Number | Priority Date | Filing Date | Title |
|---|---|---|---|
| CN202010188363.8A CN113411911B (en) | 2020-03-17 | 2020-03-17 | Identification updating method and equipment |
Publications (2)
| Publication Number | Publication Date |
|---|---|
| CN113411911A CN113411911A (en) | 2021-09-17 |
| CN113411911B true CN113411911B (en) | 2023-07-07 |
Family
ID=77677182
Family Applications (1)
| Application Number | Title | Priority Date | Filing Date |
|---|---|---|---|
| CN202010188363.8A Active CN113411911B (en) | 2020-03-17 | 2020-03-17 | Identification updating method and equipment |
Country Status (1)
| Country | Link |
|---|---|
| CN (1) | CN113411911B (en) |
Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107615817A (en) * | 2015-05-29 | 2018-01-19 | 华为技术有限公司 | The closely communication path switch method of business, apparatus and system |
Family Cites Families (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| US20170295531A1 (en) * | 2016-04-12 | 2017-10-12 | Industrial Technology Research Institute | Device to device mobility management method, user equipment and network entity using the same |
-
2020
- 2020-03-17 CN CN202010188363.8A patent/CN113411911B/en active Active
Patent Citations (1)
| Publication number | Priority date | Publication date | Assignee | Title |
|---|---|---|---|---|
| CN107615817A (en) * | 2015-05-29 | 2018-01-19 | 华为技术有限公司 | The closely communication path switch method of business, apparatus and system |
Non-Patent Citations (2)
| Title |
|---|
| 3rd Generation Partnership Project Technical Specification Group Core Network and Terminals Vehicle-to-Everything (V2X) services in 5G System (5GS) Stage 3(Release 16);3GPP;《TS24.587 V2.0.0》;20200306;正文的第6节 * |
| PC5 unicast link identifier update procedure;vivo;《3GPP TSG-CT WG1 Meeting #122-e C1-200826》;20191104;全文 * |
Also Published As
| Publication number | Publication date |
|---|---|
| CN113411911A (en) | 2021-09-17 |
Similar Documents
| Publication | Publication Date | Title |
|---|---|---|
| US10165437B2 (en) | Embedded subscriber identity module capable of managing communication profiles | |
| CN109845360B (en) | Communication method and device | |
| US11641679B2 (en) | Sidelink data indication method and terminal equipment | |
| CN110149370A (en) | A kind of upgrade file method for down loading and device | |
| US20110077051A1 (en) | UICC Control Over Devices Used to Obtain Service | |
| CN102209321A (en) | Switching processing method, communication system and associated equipment | |
| CN109803252B (en) | Secondary eSIM card logout method, eSIM server, terminal and system | |
| CN110167000B (en) | Emergency service indication method, terminal equipment and network equipment | |
| CN110351683B (en) | Parameter transmission method and device | |
| CN114915407A (en) | PC5 root key processing method and device, AUSF and remote terminal | |
| WO2020147818A1 (en) | Wireless communication method and device | |
| CN102111754B (en) | Multi-mode equipment and method for upgrading software thereof | |
| EP3879897A1 (en) | Wireless communication method, and device | |
| CN104754544A (en) | International network registration method, device and system | |
| CN113411911B (en) | Identification updating method and equipment | |
| CN112787750A (en) | DCI size alignment processing method, terminal equipment and network equipment | |
| CN111107655B (en) | SR and configuration information transmission method and device | |
| CN113497694B (en) | Method and terminal device for measuring reference signal | |
| CN112867001B (en) | Authentication method, terminal equipment and network equipment | |
| CN111600689B (en) | SRS transmission method and equipment | |
| EP3873169B1 (en) | Method and apparatus for acquiring vehicle to everything communication policy | |
| AU2019444187B2 (en) | Method and Device for Configuring Terminal Policy, Terminal, Base Station and Storage Medium | |
| CN113453379B (en) | Method, terminal and network equipment for updating identification information | |
| CN113254805A (en) | Method and network equipment for inquiring group position | |
| CN111800789B (en) | Method for configuring PC5 connection, terminal equipment and network equipment |
Legal Events
| Date | Code | Title | Description |
|---|---|---|---|
| PB01 | Publication | ||
| PB01 | Publication | ||
| SE01 | Entry into force of request for substantive examination | ||
| SE01 | Entry into force of request for substantive examination | ||
| GR01 | Patent grant | ||
| GR01 | Patent grant |