WO2014146473A1

WO2014146473A1 - Equipment identification allocation method and system

Info

Publication number: WO2014146473A1
Application number: PCT/CN2013/091088
Authority: WO
Inventors: 黄莹; 陈琳; 谢峰; 鲁照华; 罗宇民; 马书宇; 刘玉兰
Original assignee: 中兴通讯股份有限公司
Priority date: 2013-03-21
Filing date: 2013-12-31
Publication date: 2014-09-25
Also published as: CN104066078A

Abstract

Disclosed are an equipment identification allocation method and system. The method comprises: an equipment identification management entity allocating an equipment identification for a user equipment (UE); and the equipment identification management entity sending information to the UE, wherein the information contains the equipment identification. In the system, an equipment identification allocation unit is configured to allocate the equipment identification for the UE; and an equipment identification sending unit is used for sending information to the UE, wherein the information contains the equipment identification. By adopting the present invention, a network side can allocate an identification for a UE in a device-to-device scenario.

Description

Method and system for allocating equipment identification

The present invention relates to an identity distribution technology in the field of wireless communication technologies, and in particular, to a method and system for allocating device identification. Background technique

With the development of wireless multimedia services, the demand for high data rates and user experiences is increasing, which places high demands on the system capacity and coverage of traditional cellular networks. The popularity of applications such as social networking, near-field data sharing, and local advertising has led to an increasing demand for people who are interested in and communicating with nearby people. In the context of existing cell-based cells, device-to-device (D2D) technology, which represents a new direction for the development of future communication technologies, has emerged. The application of D2D technology can reduce the burden on the cellular network, reduce the battery power consumption of the user equipment, increase the data rate, and improve the robustness of the network infrastructure, which satisfies the requirements of the above high data rate services and proximity services.

D2D technology can work in licensed or unlicensed frequency bands, allowing multiple D2D-enabled user equipments, namely D2D User Equipment (D2D User Equipment) to perform direct discovery without network infrastructure or network infrastructure. / Direct communication. There are three main types of D2D applications:

1) User equipment (UE) 1 and UE2 perform data interaction under the coverage of the cellular network, and the user plane data does not pass through the network infrastructure, as shown in mode 1 of FIG.

2) UE relay transmission in the weak/uncovered area, as shown in mode 2 in FIG. 1, the UE 4 that allows poor signal quality communicates with the network through the UE3 with network coverage nearby, which can help the operator to expand coverage, Increase capacity. 3) In the event of an earthquake or emergency, if the cellular network is not working properly, direct communication between devices is allowed. As shown in mode 3 in Figure 1, the control plane and user plane between UE5, UE6 and UE7 do not pass through the network foundation. One-hop or multi-hop data communication for the facility.

D2D technology usually includes D2D discovery technology and D2D communication technology:

1) D2D discovery technology refers to determining/determining the proximity between two or more D2D user equipments (for example, within a range in which D2D direct communication is possible) or for determining/determining that a first user equipment is adjacent to a second user Equipment technology.

2) D2D communication technology refers to a technology in which some or all of the communication data between D2D user equipments can communicate directly without going through the network infrastructure.

Generally, D2D user equipment can discover each other by sending or receiving discovery signals/information. Under the coverage of cellular network, the network can assist D2D user equipment to perform D2D discovery and realize management and control of D2D discovery. The discovery signal/information may include device identification information identifying the user equipment that sent the discovery signal, and may also be referred to as a discovery ID. The discovery ID is usually assigned by the network and is used to uniquely identify the D2D user equipment in the air interface in a specific area.

Since the discovery ID can uniquely identify the UE in its effective area and can be multiplexed in different spaces, if the UE moves out of the effective area of the discovery ID, if the original discovery ID is also used, it is likely If the discovery ID of the other UEs conflicts with each other, the network cannot uniquely identify the UE by using the discovery ID, which will result in the D2D discovery being unsuccessful. Therefore, the discovery ID has regional validity and time validity. Once the specific area or specific time is exceeded, it is found. The ID is invalid. In the D2D scenario, the network side needs to have an allocation mechanism for recovering the discovery ID and re-allocating the discovery ID for the UE. However, in the existing standard, the LTE system does not support the discovery ID allocation mechanism in the D2D scenario. Summary of the invention

In view of this, the main purpose of the embodiments of the present invention is to provide a method and system for allocating device identifiers. In the D2D scenario, the network side can assign an identifier to the UE. To achieve the above objective, the technical solution of the embodiment of the present invention is implemented as follows: A method for allocating device identifiers, the method includes:

The device identity management entity allocates a device identifier to the user equipment UE;

The device identity management entity sends information to the UE, and the information includes the device identifier. The device identifier management entity allocates a device identifier to the UE, and the device identifier management entity allocates a device identifier to the UE in the process of attaching the UE; or the device identifier management entity is in the tracking area of the UE. Assigning a device identifier to the UE during the update process;

Or the device identifier management entity allocates a device identifier to the UE in a service request process of the UE;

Or the device identifier management entity allocates a device identifier to the UE in a handover process of the UE;

Or the device identifier management entity allocates a device identifier to the UE in a device identifier allocation process of the UE.

The device identifier management entity allocates a device identifier to the UE in the handover process of the UE, and further includes:

The first device identifier management entity indicates that the second device identifier management entity needs to allocate a new device identifier in an explicit or implicit manner; the first device identifier management entity is a source device identifier management entity of the UE; The second device identity management entity is a target device identity management entity of the UE.

The device identifier management entity allocates a device identifier to the UE, and further includes:

The device identifiers used by the UE in different RRC states are allocated by different device identity management entities;

Alternatively, the device identifiers used by the UE in different RRC states are allocated by the same device identity management entity. The device identifiers used by the UE in different RRC states are allocated by different device identifier management entities, and the method further includes:

The device identifier used by the UE in the connected state is allocated by the base station, and the device identifier used by the UE in the idle state is allocated by the mobility management entity.

The device identifier management entity allocates a device identifier to the UE, and further includes: the device identifiers allocated by the device identifier management entity for use by the UE in different RRC states are different in length.

The device identifier management entity allocates a device identifier to the UE, and further includes: the device identifier management entity allocates a device identifier to the UE according to the subscription level of the UE.

The device identifier management entity allocates a device identifier to the UE according to the subscription level of the UE, and further includes:

The device identification management entity allocates different device identification lengths for UEs of different subscription levels;

Alternatively, the device identity management entity allocates device identifiers for UEs of different subscription levels from different device identity sets.

The device identifier management entity sends information to the UE, where the information includes the device identifier, and further includes:

In the case that the device identifier used by the UE in different RRC states is allocated by a different device identity management entity, the information further includes the UE state corresponding to the device identifier; the UE state includes: an idle state and a connected state.

The information also includes a valid time range of the device identification.

The device identity management entity is in the device identity allocation process of the UE. The UE allocates the device identifier, and further includes:

When the information received by the UE from the device identity management entity includes the valid time range of the device identifier, after the device identifier exceeds the valid time range, the UE requests the device identity management entity to allocate a new device identifier.

Or, if the UE detects a cell identity change of the currently camped cell broadcast, the UE requests the device identity management entity to allocate a new device identifier;

Or, if the UE detects that the tracking area code of the currently camped cell broadcast changes, the UE requests the device identity management entity to allocate a new device identifier;

Or, if the UE detects that the discovery area identifier of the currently camped cell broadcast changes, the UE requests the device identity management entity to allocate a new device identifier;

Or the UE requests the device identity management entity to allocate a device identifier according to an event-triggered manner;

Or the UE allocates a device identifier to the device identity management entity request according to an event-triggered periodic manner;

Or the UE periodically requests the device identity management entity to allocate a device identifier. After the device identifier management entity allocates the device identifier to the UE, the method further includes: the device identifier management entity determining whether the allocated device identifier needs to be released, and if the device identifier needs to be released, releasing the allocated device Logo.

The device identifier management entity determines whether it is necessary to release the allocated device identifier, and further includes:

The device identifier management entity determines, according to the device identifier release indication information of the UE, whether the allocated device identifier needs to be released;

Or the device identifier management entity determines, according to the device identifier release indication information of the device identifier management entity that currently allocates the device identifier to the UE, whether the required device label needs to be released. Or the device identifier management entity determines, according to the device identifier release indication information of other network elements, whether the allocated device identifier needs to be released.

The device identifier management entity determines whether it is necessary to release the allocated device identifier according to the device identifier release indication information of the UE, and further includes:

And if the UE determines that the device identifier is not required to be used, the sending device identifier release indication information indicates that the device identifier management entity releases the device identifier allocated for the UE.

The device identifier management entity determines whether the device identifier needs to be released according to the device identifier release indication information of the device identifier management entity that is currently assigned the device identifier of the UE, and further includes:

The device identifier management entity that currently allocates the device identifier to the UE indicates, according to the identifier information of the device identifier management entity that is configured to allocate the device identifier to the UE, and the identifier information of the UE that is sent by the UE. The device identity management entity that describes the UE assignment device identity releases the device identity that has been assigned to the UE.

If the information sent by the device identity management entity to the UE indicates the valid time range of the device identifier, after the valid time range is exceeded, the device identity management entity determines that the allocated device identifier needs to be released, and the The assigned device ID is released.

The device identifier allocated by the device management entity to the UE is composed of any one or more of the following:

Identification information for device-to-device use;

Temporary mobile subscriber identity TMSI of the UE;

The UE's International Mobile Subscriber Identity (IMSSI);

The cell radio network of the UE temporarily identifies a C-RNTI;

The IP address of the UE; The tracking area TA where the UE is located identifies information.

A device identification distribution system, the system includes: a device identification allocation unit and a device identification sending unit located on a device identity management entity side;

The device identifier allocation unit is configured to allocate a device identifier to the UE;

The device identifier sending unit is configured to send information to the UE, where the information includes the device identifier.

The device identifier allocation unit and the device identifier sending unit may use a central processing unit (CPU), a digital signal processor (DSP), or a programmable signal array when performing processing. ¹ J (FPGA, Field - Programmable Gate Array) implementation.

The device identifier allocation unit is further configured to allocate a device identifier to the UE in an attaching process of the UE;

Or, the device identifier is allocated to the UE in the tracking area update process of the UE; or, the UE identifier is allocated to the UE in a service request process of the UE;

Or, the device identifier is allocated to the UE in a handover process of the UE;

Or, the device identifier is allocated to the UE in a device identity allocation process of the UE.

The device identifier allocation unit is further configured to allocate the device identifiers used by the UE in different RRC states by different device identifier management entities; or the device identifiers used by the UE in different RRC states are identified by the same device identifier. Manage entity assignments.

The device identifier allocation unit is further configured to allocate, to the UE, the lengths of the device identifiers used by the UEs in different RRC states to be different.

The device identifier allocation unit is further configured to allocate a device identifier to the UE according to the subscription level of the UE.

The device identifier allocation unit is further configured to allocate different device identifier lengths to UEs of different subscription levels; Or, assigning device identifiers to UEs of different subscription levels from different device identifier sets. The device identifier sending unit is further configured to: if the device identifier used by the UE in different RRC states is allocated by different device identifier management entities, the information sent by the UE further includes the UE status corresponding to the device identifier. The UE status includes: an idle state and a connected state.

The device identifier sending unit is further configured to include the valid time range of the device identifier in the information that is sent.

The device identifier allocation unit is further configured to: when the device identifier is allocated to the UE in the device identifier allocation process of the UE, after the device identifier exceeds the valid time range, the device identifier is received from the UE. a request to assign a new device ID;

Or, when the UE detects that the cell identity of the currently camped cell is changed, the UE receives a request for allocating a new device identifier from the UE;

Or, when the UE detects that the tracking area code of the currently camped cell broadcast changes, receiving a request for allocating a new device identifier from the UE;

Or, when the UE detects that the discovery area identifier of the currently camped cell broadcast changes, receiving a request for allocating a new device identifier from the UE;

Or receiving a request for assigning a device identifier from an event triggering manner of the UE;

Or receiving, by the UE, an event-triggered periodic manner of the allocation of the device identifier;

Alternatively, a request for periodic allocation of device identification from the UE is received.

The system further includes: a device identifier release unit located on the device identifier management entity side, configured to release the allocated device identifier when the device identifier is required to be released, and then the device identifier is released.

The device identifier release unit is further configured to determine, according to the device identifier release indication information of the UE, whether the allocated device identifier needs to be released; Or determining, according to the device identifier release indication information of the device identifier management entity that currently allocates the device identifier to the UE, whether the allocated device identifier needs to be released;

Or, according to the device identifier release indication information of other network elements, it is determined whether the allocated device identifier needs to be released.

The device identifier release unit is further configured to: when the information sent includes the valid time range of the device identifier, after the valid time range is exceeded, it is determined that the allocated device identifier needs to be released, and The assigned device ID is released.

In the embodiment of the present invention, the device identifier management entity allocates a device identifier to the UE; the device identifier management entity sends information to the UE, where the information includes the device identifier. In the embodiment of the present invention, the network side allocates an identifier to the UE in the D2D scenario. DRAWINGS

FIG. 1 is a schematic diagram of an application mode in which D2D technology is applied;

2 is a schematic diagram of an implementation process of a method according to an embodiment of the present invention;

3 is a schematic flowchart of an implementation process of Embodiment 1 of the method of the present invention;

4 is a schematic diagram of an implementation process of a second embodiment of a method according to the present invention;

FIG. 5 is a schematic flowchart of an implementation process of a third embodiment of a method according to the present invention; FIG.

6 is a schematic flowchart of an implementation process of Embodiment 4 of the method of the present invention;

7 is a schematic flowchart of an implementation process of Embodiment 5 of the method according to the present invention;

8 is a schematic flowchart of an implementation process of Embodiment 6 of the method according to the present invention;

9 is a schematic diagram of an implementation process of Embodiment 7 of the method according to the present invention;

10 is a schematic flowchart of an implementation process of Embodiment 8 of the method according to the present invention;

FIG. 11 is a schematic flowchart of an implementation process of Embodiment 9 of the method of the present invention. detailed description

In the embodiment of the present invention, the device identity management entity allocates a device identifier to the UE; the device identifier The management entity sends information to the UE, and the information includes the device identifier.

A method for allocating device identification, the method mainly includes the following contents:

The device identity management entity allocates a device identifier to the UE;

The device identity management entity sends information to the UE, the information including the device identity assigned to the UE, the device identity being used to identify the UE in device-to-device discovery and/or device-to-device communication.

Preferably, the device identifier management entity allocates the device identifier to the UE, and the method further includes: the device identifier management entity assigning the device identifier to the UE in the attaching process of the UE;

Or the device identifier management entity allocates a device identifier to the UE in a tracking area update process of the UE;

Alternatively, the device identity management entity allocates a device identity to the UE in a device identity allocation process of the UE.

Preferably, the device identifier management entity allocates the device identifier to the UE in the handover process of the UE, and further includes:

Preferably, the device identifier management entity allocates a device identifier to the UE, and further includes:

The device identifier used by the UE in different RRC states is managed by a different device identifier. Assignment

Alternatively, the device identifiers used by the UE in different RRC states are allocated by the same device identity management entity.

Preferably, the device identifiers used by the UE in different RRC states are allocated by different device identifier management entities, and the method further includes:

Preferably, the device identifier management entity allocates the device identifier to the UE, and further includes: the device identifiers allocated by the device identifier management entity for use by the UE in different RRC states are different in length.

Preferably, the device identifiers used by the device identifier management entity for the UEs to be used in different RRC states are different in length, and the method further includes:

The device identifier used by the UE in the idle state is longer than the device identifier used in the connected state.

Preferably, the device identifier management entity allocates the device identifier to the UE, and the method further includes: the device identifier management entity assigning the device identifier to the UE according to the subscription level of the UE.

Preferably, the device identifier management entity allocates the device identifier to the UE according to the subscription level of the UE, and further includes:

Preferably, the device identifier management entity sends information to the UE, where the information includes the device identifier, and further includes: The information includes one or more device identifiers. Further, the information may further include an effective time range of the device identifier.

Preferably, the device identifier management entity sends information to the UE, where the information includes the device identifier, and further includes:

In the case that the device identifiers used by the UEs in different RRC states are allocated by different device identifier management entities, the information also indicates the UE status corresponding to the device identifiers. The UE status includes: an idle state and a connected state.

Preferably, the device identifier management entity allocates the device identifier to the UE in the device identifier allocation process of the UE, and further includes:

The UE requests the device identification management entity to allocate a new device identifier, after the information received by the device identifier management entity indicates the valid time range of the device identifier, and the device identifier exceeds the valid time range;

Or the UE periodically requests the device identity management entity to allocate a device identifier. Preferably, after the device identifier management entity allocates the device identifier to the UE in the device identifier allocation process of the UE, the method further includes: The device sent by the UE when the UE detects that the cell identifier and/or the tracking area code and/or the discovery area identifier of the currently camped cell are changed, and the device identification management entity requests to allocate a new device identifier. The identifier allocation request includes the identifier information of the device identity management entity that last assigned the device identifier to the UE and the identifier information of the UE.

Preferably, the identifier information of the UE includes, but is not limited to: a device identifier that was last allocated to the UE.

Preferably, after the device identity management entity sends the information to the UE, the method further includes: the UE storing the information, and using the information in device-to-device discovery and/or device-to-device communication.

Preferably, the UE stores the information, and uses the information in device-to-device discovery and/or device-to-device communication, and further includes:

In the case that the device identifiers used by the UEs in different RRC states are allocated by different device identity management entities, the UEs respectively store information corresponding to different RRC states, and device-to-device discovery and/or device-to-device The corresponding information is used in the communication process according to the current RRC state.

Preferably, after the device identifier management entity allocates the device identifier to the UE, the method further includes: the device identifier management entity determining whether the allocated device identifier needs to be released, and releasing the allocated device identifier if necessary.

It should be noted that, in the embodiment of the present invention, in addition to the mechanism for supporting the device identifier allocation in the D2D scenario, the mechanism for releasing the device identifier allocated in the D2D scenario can also be supported. Compared with the prior art, when the UE does not need to use the device identifier (also referred to as the discovery ID) or the UE has moved out of the original device identifier effective area, the network element that allocates the original device identifier needs to release the original device identifier, otherwise The device identifier is invalidated. However, in the majority of cases, the network side does not know when the UE does not need to use the device identifier (for example, the UE turns off the D2D module or closes an application), or moves out of the original device. Identify a valid area (for example, device ID) In the case of being allocated by the base station, the IDLE state UE moves out of the cell under the base station), thereby reducing the number of device identifiers that can be allocated in the cell under the base station, thereby reducing the effective utilization of the device identifier, and using the embodiment of the present invention, The device ID release mechanism allocated in the D2D scenario can improve the effective utilization of device IDs.

Preferably, the device identifier management entity determines whether it is necessary to release the allocated device identifier, and further includes:

Or the device identifier management entity determines, according to the device identifier release indication information of the device identifier management entity that currently allocates the device identifier to the UE, whether the allocated device identifier needs to be released;

Or the device identifier management entity determines, according to the device identifier release indication information of other network elements, whether the allocated device identifier needs to be released.

Preferably, the device identifier management entity determines whether it is necessary to release the allocated device identifier according to the device identifier release indication information of the UE, and further includes:

Preferably, the device identifier management entity determines, according to the device identifier release indication information of the device identifier management entity that is currently assigned the device identifier of the UE, whether to release the allocated device identifier, and further includes:

The device identity management entity that currently allocates the device identifier to the UE indicates the device identity management entity according to the identifier information of the device identity management entity that is configured to allocate the device identifier to the UE and the identifier information of the UE that is sent by the UE. Release the device identification that has been assigned to the UE.

Preferably, the device identity management entity determines whether it is necessary to release the allocated device identifier. Also includes:

It should be noted that the device identity management entity may be an independent network entity, or located in an existing network entity or a newly added network entity. The existing network entity includes but is not limited to: a base station, a mobility management entity, A contracting server (HSS); the new network entity includes but is not limited to: a server that can be used for D2D purposes.

Preferably, the device management entity allocates a device identifier to the UE by one or more of the following:

Identification information for D2D use;

Temporary Mobile Subscriber Identity (TMSI) of the UE;

The International Mobile Subscriber Identity (IMSI) of the UE;

a cell radio network temporary identifier (C-RNTI) of the UE;

The IP address of the UE;

The tracking area (TA) where the UE is located identifies information.

In summary, the embodiment of the present invention solves the problem of device device redistribution and release in device-to-device discovery, and the device identifier can be effectively solved under the signaling message that needs to be introduced in the embodiment of the present invention. The problem of allocation, and can solve the problem of resource release of device identification, avoiding invalidation of device identification and improving the effective utilization of device identification.

The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings.

FIG. 2 is a schematic diagram of an implementation process of a method according to an embodiment of the present invention, including the following steps: Step 101: A device identity management entity allocates a device identifier to a UE.

Step 102: The device identity management entity sends information to the UE, where the information includes a device identifier allocated to the UE. Here, the device identifier is used to identify the UE in device-to-device discovery and/or device-to-device communication.

Method embodiment one:

This embodiment describes a method for a device identity management entity to allocate a device identifier to a UE during an attach procedure of a UE. In this embodiment, the device identity management entity is located in the base station and / or MME. As shown in FIG. 3, this embodiment includes the following steps:

Step 201: The UE initiates an attach process after being powered on. After establishing an RRC connection with the base station, the UE sends a NAS message attach request to the base station in the air interface RRC message, and the base station transparently transmits the attach request message to the MME.

Step 202: The MME selects a serving serving gateway (S-GW) and a packet data gateway (P-GW) for the UE, and creates a default evolved packet system (EPS) bearer for the UE. The MME sends a create session request message to the S-GW.

Step 203: The S-GW creates a context of the UE, and sends a create session request message to the P-GW selected by the MME for the UE.

Step 204: The P-GW creates a context of the UE, and replies to the S-GW to create a session response message. Step 205. The S-GW replies to the MME with a create session response message.

Step 206. The MME allocates a device identifier to the UE. Optionally, the MME may also specify a valid time range of the device identifier. The device identifier can uniquely identify the UE in a tracking area or a discovery area composed of multiple cells, that is, in the tracking area or the discovery area.

Step 207: The MME sends an S1 interface initial context request message to the base station, where the NAS message attach accept message is included. If the MME allocates a device identifier to the UE, the MME sends the device identifier information including the device identifier to the base station. If the MME allocates the valid time range of the device identifier, the device identifier information further includes a valid time range of the device identifier. Optionally, the MME may also indicate that the allocated device identifier is used by the UE in an idle state.

Step 208: The base station allocates a device identifier to the UE. Optionally, the base station may further specify the device identifier. The effective time range for identification. The device identifier can uniquely identify the UE in the next cell of the base station, that is, it is valid in the cell range.

It should be noted that, based on step 206 and step 208, the possible cases are: only the MME allocates a device identifier to the UE, or only the base station allocates a device identifier to the UE, or both the base station and the MME allocate a device identifier for the UE. In the case that both the base station and the MME allocate the device identifier to the UE, the UE uses the device identifier assigned by the base station or the MME in different RRC states. If the UE uses the device identifier allocated by the MME in the idle state, the UE uses the device identifier allocated by the base station in the connected state. Further, the length of the device identifier used by the UE in different RRC states is different, for example, the device identifier used by the UE in the idle state is longer than the device identifier used in the connected state. In this way, the effective area of the device identifier used by the UE in the idle state is larger than that in the connected state, and the number of times the UE re-acquires after the device identifier fails can be reduced, thereby achieving a greater degree of UE power saving.

Step 209: The base station sends the NAS message attach accept message sent by the MME to the UE by using an air interface RRC message. The base station transmits device identification information to the UE in the message. According to the above description, one or more device identifiers may be included in the device identification information. Optionally, the device identification information may further include a valid time range of the device identifier and/or a corresponding UE status.

Step 210: The UE parses and stores the device identification information after receiving the RRC message, and sends the discovery signal by using the device identifier in the device-to-device discovery process. If the device identification information includes two device identifiers, the UE sends a discovery signal by using the corresponding device identifier according to the current RRC state.

It should be noted that the device identifier may be the user identifier allocated by the base station or the MME for the D2D use, or may be the C-RNTI allocated by the base station for the UE, or the IMSI, or the S-TMSI allocated by the MME, and the IP address allocated by the PGW for the UE. The address, the identification information of the TA where the UE is located, and the like may also be composed of one or more of the above identification information.

Method Embodiment 2: This embodiment describes a method for a device identity management entity to allocate a device identity to a UE during a Tracking Area Update (TAU) process of a UE. In this embodiment, the device identity management entity is located in the base station and/or MME. As shown in FIG. 4, this embodiment includes the following steps:

Step 301. After the UE moves and camps on a new cell in the idle state, and detects that the TAI of the cell is not in the TAI list configured by the MME in the attaching process, the UE initiates a TAU process. The UE first establishes an RRC connection with the base station. Then, the RRC message is sent to the RRC connection establishment completion message to the base station, which includes the NAS message TAU request message. The base station then transparently transmits the NAS message to the target MME through the S1 interface message.

Steps 302-304. The target MME interacts with the source MME to deliver the context of the UE. Steps 305-308. In this embodiment, the SGW of the UE is not replaced, and the MME and the S-GW,

The P-GW interacts to modify the bearer process.

Step 309. The target MME sends a location update message to the HSS to update the location information of the UE on the HSS.

Steps 310-311. The HSS sends a location cancel message to the source MME to inform the source MME that the UE has moved out of its area. The source MME replies to the HSS with a location cancellation confirmation message.

Step 312. The source MME releases the device identifier assigned to the UE. Step 312 here can be performed before or after step 311.

Step 313. The HSS replies to the target MME with a location update confirmation message.

Step 314. The MME allocates a device identifier to the UE. Optionally, the MME may also specify a valid time range of the device identifier. The device identifier can uniquely identify the UE in a tracking area or a discovery area composed of multiple cells, that is, in the tracking area or the discovery area.

Step 315. The MME sends an S1 interface initial context request message to the base station, where the NAS message TAU accept message is included. If the MME allocates the device identifier to the UE, the MME sends the device identifier information including the device identifier to the base station. If the MME is configured with the valid time range of the device identifier, the device identifier information also includes the valid time range of the device identifier. Optionally, The MME may also indicate that the assigned device identity is used by the UE in an idle state.

Step 316. The base station allocates a device identifier to the UE. Optionally, the base station may further specify a valid time range for the device identifier. The device identifier can uniquely identify the UE in the next cell of the base station, that is, it is valid in the cell range.

It should be noted that, based on step 314 and step 316, the possible cases are: only the MME allocates a device identifier to the UE, or only the base station allocates a device identifier to the UE, or both the base station and the MME allocate a device identifier for the UE. In the case that both the base station and the MME allocate the device identifier to the UE, the UE uses the device identifier assigned by the base station or the MME in different RRC states. If the UE uses the device identifier allocated by the MME in the idle state, the UE uses the device identifier allocated by the base station in the connected state. Further, the length of the device identifier used by the UE in different RRC states is different, for example, the device identifier used by the UE in the idle state is longer than the device identifier used in the connected state. In this way, the effective area of the device identifier used by the UE in the idle state is larger than that in the connected state, and the number of times the UE re-acquires after the device identifier fails can be reduced, thereby achieving a greater degree of UE power saving.

Step 317: The base station sends the NAS message attach accept message sent by the MME to the UE by using an air interface RRC message. The base station transmits device identification information to the UE in the message. According to the above description, one or more device identifiers may be included in the device identification information. Optionally, the device identification information may further include a valid time range of the device identifier and/or a corresponding UE status.

Step 318. After receiving the RRC message, the UE parses and stores the device identification information therein, and uses the device identifier to send the discovery signal in the device-to-device discovery process. If the device identification information includes two device identifiers, the UE sends a discovery signal by using the corresponding device identifier according to the current RRC state.

Method embodiment three:

This embodiment describes a method for a device identity management entity to allocate a device identifier to a UE in a service request (SR) initiated by a UE. In this embodiment, the device identity management entity is located at the base In the station and / or MME. As shown in FIG. 5, this embodiment includes the following steps:

Step 401. Idle state The UE has the service data to be sent, first establishes an RRC connection with the base station, and then carries the NAS message service request message to the base station in the RRC message RRC connection setup complete message. After receiving the base station, the NAS message is transparently transmitted to the MME.

Step 402: The MME allocates a device identifier to the UE; or the MME determines whether the TAI or the discovery area identifier of the UE is the same as the TAI or the discovery area identifier of the current location when the device identifier is allocated to the UE, and if not, the UE is allocated. New device identification. Optionally, the MME may also specify a valid time range of the device identifier.

Step 403. The MME sends an initial context setup request message to the base station to establish an E-RAB bearer for the UE. If the MME allocates a device identifier to the UE, the message carries the device identifier information including the device identifier. If the MME is configured with the valid time range of the device identifier, the device identifier information further includes a valid time range of the device identifier. Optionally, the MME may also indicate that the allocated device identifier is used by the UE in an idle state.

Step 404: The base station allocates a device identifier for the D2D to the UE. Optionally, the base station may further specify a valid time range of the device identifier. The device identifier can uniquely identify the UE in the next cell of the base station, that is, it is valid within the cell range.

It should be noted that, based on step 402 and step 404, the possible cases are as follows: Only the MME allocates a device identifier to the UE, or only the base station allocates a device identifier to the UE, or both the base station and the MME allocate a device identifier for the UE. In the case that both the base station and the MME allocate the device identifier to the UE, the UE uses the device identifier assigned by the base station or the MME in different RRC states. If the UE uses the device identifier allocated by the MME in the idle state, the UE uses the device identifier allocated by the base station in the connected state. Further, the lengths of the device identifiers used by the UEs in different RRC states are different, for example, the device identifiers used by the UE in the idle state are longer than the device identifiers used in the connected state. In this way, the effective area of the device identifier used by the UE in the idle state is larger than that in the connected state, so that the number of times the UE re-acquires after the device identifier fails can be reduced, thereby achieving a greater degree of UE. Power saving purposes.

Step 405. The base station sends an RRC connection reconfiguration message to the UE, and establishes a corresponding air interface DRB data bearer for the UE. If the base station receives the device identification information from the MME, the message includes device identification information received from the MME. If the base station allocates the device identifier to the UE, the message carries the device identifier information that is allocated by the base station and includes the device identifier. If the base station is configured with the valid time range of the device identifier, the device identifier information further includes a valid time range of the device identifier. Optionally, the base station may further indicate that the allocated device identifier is used by the UE in the connected state. After completing the corresponding air interface configuration, the UE replies to the RRC connection reconfiguration complete message to the base station.

Step 406. After receiving the RRC message, the UE parses and stores the device identification information therein, and uses the device identifier to send the discovery signal in the device-to-device discovery process. If the device identification information indicates that the device identifier corresponds to the RRC connected state of the UE, the UE sends the discovery signal by using the device identifier only when it is in the corresponding RRC state. If the UE receives two device identifiers, the UE sends a discovery signal according to the current RRC state using the corresponding device identifier.

Step 407. The base station sends an initial context setup complete message to the MME.

Step 408-411. The MME performs an modify bearer process to the S-GW and the P-GW according to the accepted EPS bearer replied by the base station to establish S1 and S6 bearers.

Method Embodiment 4:

This embodiment describes a method for a base station to allocate a device identifier to a UE during an X2 handover process of the UE. In this embodiment, the device identity management entity is located in the base station and / or MME. As shown in FIG. 6, the embodiment includes the following steps:

Step 501. The UE detects a strong signal of the neighboring cell, and sends a measurement report to the source base station. Step 502. The source base station performs a handover decision according to the measurement report sent by the UE, and determines to execute the X2 handover procedure. Then the target base station is determined and an X2 handover request message is sent to the target base station. The handover request message may include explicit or implicit indication information indicating that a new device identity needs to be allocated to the UE. For example, the implicit indication may be D2D related capability information of the UE, or the UE is working D2D related applications or behaviors performed.

Step 503: The target base station allocates a device identifier for the D2D to the UE. Optionally, the target base station may further specify a valid time range of the device identifier. The device identifier can uniquely identify the UE in the next cell of the base station, that is, it is valid within the cell range.

Step 504. After the target base station performs resource reservation for the UE, the target base station sends a handover request acknowledgement message to the source base station. If the target base station allocates the device identifier to the UE, the message carries the device identifier information including the device identifier. If the target base station is configured with the valid time range of the device identifier, the device identifier information further includes a valid time range of the device identifier. Optionally, the base station may further indicate that the allocated device identifier is used by the UE in the connected state.

Step 505: The source base station transparently transmits the handover command sent by the target base station to the UE by using an RRC connection reconfiguration message, where the device identifier information sent by the target base station is included.

Step 506. The UE parses and stores the device identification information after receiving the RRC connection reconfiguration message, and sends the discovery signal by using the device identifier in the device-to-device (D2D) discovery process. If the device identification information indicates that the device identifier corresponds to the RRC connected state of the UE, the UE sends the discovery signal by using the device identifier only when it is in the connected state.

Step 507. The source base station sends an SN state transition message to the target base station, where the uplink and downlink PDCP layer states are included to ensure data packet order and lossless handover.

Step 508. The UE disconnects from the source base station, synchronizes with the target base station, establishes an RRC connection, and then sends an RRC connection reconfiguration complete message to the target base station. The message may include explicit or implicit indication information indicating that a new device identity needs to be assigned to the UE. For example, the implicit indication may be D2D related capability information of the UE, or a D2D related application or behavior being performed by the UE.

Step 509. The target base station sends a path transfer request message to the MME of the UE to notify the MME that the UE handover is completed and the S1 control plane path is transferred. The MME then sends a modify bearer message to the S-GW to transfer the S1 user plane path. The path transfer request message may include explicit or implicit indication information indicating that a new device identifier needs to be allocated to the UE. For example, the implicit indication can be UE D2D related capability information, or D2D related applications or behaviors that the UE is conducting.

Step 510. The MME allocates a device identifier to the UE. The MME determines whether the TAI or the discovery area identifier of the UE is the same as the current TAI or the discovery area identifier when the UE allocates the device identifier. If not, the UE allocates a new device. Logo. Optionally, the MME may further specify a valid time range of the device identifier.

It should be noted that, based on the step 503 and the step 510, the possible situation is: only the MME allocates the device identifier to the UE, or only the base station allocates the device identifier to the UE, or the base station and the MME all allocate the device identifier for the UE. In the case that both the base station and the MME allocate the device identifier to the UE, the UE uses the device identifier assigned by the base station or the MME in different RRC states. If the UE uses the device identifier allocated by the MME in the idle state, the UE uses the device identifier allocated by the base station in the connected state. Further, the length of the device identifier used by the UE in different RRC states is different, for example, the device identifier used by the UE in the idle state is longer than the device identifier used in the connected state. In this way, the effective area of the device identifier used by the UE in the idle state is larger than that in the connected state, and the number of times the UE re-acquires after the device identifier fails can be reduced, thereby achieving a greater degree of UE power saving.

Step 511. The MME of the UE replies with a path transfer request acknowledgement message to the target base station. Optionally, the network side identifier information of the UE (for example, IMSI, S-TMSI, etc.) is included. If the MME allocates the device identifier to the UE, the message carries the device identifier information including the device identifier. If the MME allocates the valid time range of the device identifier, the device identifier information further includes a valid time range of the device identifier. Optionally, the MME may also indicate that the allocated device identifier is used by the UE in an idle state.

Step 512. If the path transfer request acknowledgement message received by the target base station includes the device identifier information, the target base station sends an RRC connection reconfiguration to the UE, where the message carries the device identifier information including the device identifier. If the MME simultaneously allocates the valid time range of the device identifier and the RRC state corresponding to the UE, the device identifier information also includes the valid time range and relative of the device identifier. The RRC state should be.

Step 513: The UE parses and stores the device identification information after receiving the RRC connection reconfiguration message, and sends the discovery signal by using the device identifier in the device-to-device discovery process. If the device identification information indicates that the device identifier corresponds to the RRC idle state of the UE, the UE sends the discovery signal by using the device identifier only when in the idle state.

Step 514: The target base station establishes and maintains a mapping relationship between the device identifier of the UE and the network side identifier, and is used for subsequent D2D related purposes.

Step 515. The target base station sends a user context release message to the source base station to notify the source base station that the handover is complete and release the UE related context.

Step 516: After receiving the user context release message, the source base station may release the context of the UE, including releasing the device identifier allocated to the UE.

Method Embodiment 5:

This embodiment describes a method for a base station to allocate a device identifier to a UE in an S1 handover procedure of a UE. In this embodiment, the device identity management entity is located in the base station and / or MME. As shown in Figure 7, this embodiment includes the following steps:

Step 601: The UE detects a strong signal of the neighboring cell, and sends a measurement report to the source base station. Step 602: The source base station performs a handover decision according to the measurement report sent by the UE, and determines to perform the S1 handover procedure. Then, the target base station is determined and an S1 handover request message is sent to the MME of the UE. The handover request message may include explicit or implicit indication information indicating that a new device identity needs to be allocated to the UE. For example, the implicit indication may be D2D related capability information of the UE, or a D2D related application or behavior being performed by the UE.

Step 603: The source base station sends a Forward Relocation Request message to the source MME. The message may include explicit or implicit indication information indicating that a new device identity needs to be assigned to the UE.

Step 604: The target MME sends an S1 interface switch request message to the target base station, where the message may include explicit or implicit indication information for indicating that the UE needs to be assigned a new device identifier. Step 605. The target base station allocates a device identifier for the D2D to the UE. Optionally, the target base station may further specify a valid time range of the device identifier.

Step 606: The target base station sends a handover request acknowledgement message to the target MME. If the target base station allocates the device identifier to the UE, the message carries the device identifier information including the device identifier. If the target base station is configured with the valid time range of the device identifier, the device identifier information further includes a valid time range of the device identifier. Optionally, the target base station may also indicate that the allocated device identifier is used by the UE in the connected state.

Step 607. The target MME allocates a device identifier to the UE. The MME determines whether the TAI or the discovery area identifier of the UE is the same as the current TAI or the discovery area identifier when the UE allocates the device identifier. If not, the UE is allocated a new one. Equipment Identity. Optionally, the MME may further specify a valid time range of the device identifier.

It should be noted that, based on the step 605 and the step 607, the possible situation is: only the MME allocates the device identifier to the UE, or only the base station allocates the device identifier to the UE, or the base station and the MME allocate the device identifier to the UE. In the case that both the base station and the MME allocate the device identifier to the UE, the UE uses the device identifier assigned by the base station or the MME in different RRC states. If the UE uses the device identifier allocated by the MME in the idle state, the UE uses the device identifier allocated by the base station in the connected state. Further, the length of the device identifier used by the UE in different RRC states is different, for example, the device identifier used by the UE in the idle state is longer than the device identifier used in the connected state. In this way, the effective area of the device identifier used by the UE in the idle state is larger than that in the connected state, and the number of times the UE re-acquires after the device identifier fails can be reduced, thereby achieving a greater degree of UE power saving.

Step 608: The target MME sends a forwarding relocation response message to the source MME. If the target MME receives the device identification information from the target base station, the message includes the device identification information received from the target base station. If the target MME allocates the device identifier to the UE, the message carries the device identifier information that is allocated by the target MME and includes the device identifier. If the target MME allocates devices at the same time The effective time range of the identifier, the device identification information further includes a valid time range of the device identifier. Optionally, the target MME may further indicate that the allocated device identifies the RRC state of the corresponding UE.

Step 609-611. After receiving the RRC message, the UE parses and stores the device identification information therein, and sends the discovery signal by using the device identifier in the device-to-device discovery process. If the device identification information indicates that the device identifier corresponds to the RRC connected state of the UE, the UE sends the discovery signal by using the device identifier only when it is in the corresponding RRC state. If the UE receives two device identifiers, the UE sends a discovery signal by using the corresponding device identifier according to the current RRC state.

Method Embodiment 6:

This embodiment describes a method for a base station to allocate a device identifier to a UE in a device identity allocation process of a UE. In this embodiment, the device identity management entity is located in the base station. As shown in FIG. 8, the embodiment includes the following steps:

Step 701. The UE triggers the initiating device identity allocation process based on the following conditions:

Here, the conditions include any one or a combination of the following:

1) The UE in the idle state or the connected state detects that the allocated device identifier exceeds the valid time range;

2) The idle state UE detects that the ECGI of the camped cell changes;

3) Event triggering, for example, the UE opens the D2D module, the UE opens an application, and the UE starts the D2D discovery/discovery function;

4) periodically triggering, for example, the UE periodically performs D2D discovery/discovery based on the application to update the request list of the buddy list to periodically request the device identification assignment;

5) Event-triggered periodicity, for example, the UE starts periodic requesting device identification allocation. Step 702: The UE sends a device identity allocation request message to the base station (if the UE is in an idle state, an RRC connection needs to be established first). Optionally, the message may further include status indication information, configured to indicate a UE status corresponding to the device identifier to be allocated. Optionally, the message contains the device identifier. Assign the cause value, such as the valid time range, ECGI change, etc. Optionally, the message includes the MME identity information of the UE. Optionally, the message includes the base station identification information that is used to allocate the device identifier to the UE and the identifier information of the UE (for example, the C-RNTI of the UE in the last cell, the device identifier that was last allocated to the UE, and the like).

Step 703. The base station allocates a device identifier to the UE. Alternatively, the base station may also specify a valid time range for the device identification. The device identifier can uniquely identify the UE in the next cell of the base station, that is, it is valid within the cell range. Or, if the device identifier allocation request message sent by the UE includes the status indication information, the base station determines, according to the status indication information, whether to allocate the device identifier to the UE. Specifically, if the status indication information indicates that the device identifier to be allocated corresponds to the connected state of the UE, the base station allocates the device identifier to the UE. If the status indication information indicates that the device identifier to be allocated corresponds to the idle state of the UE, the base station may not allocate the device identifier to the UE according to the seventh embodiment, and send the device identifier allocation request message to the MME of the UE.

Step 704: The base station replies to the UE with a device identity assignment response message. The message carries device identification information including the device identifier. If the base station is configured with the valid time range of the device identifier, the device identifier information further includes a valid time range of the device identifier. Optionally, the base station may further indicate that the allocated device identifier is used by the UE in the connected state.

Step 705: The UE parses and stores the device identification information after receiving the device identity allocation response message, and sends the discovery signal by using the device identifier in the device-to-device discovery process. If the device identification information indicates that the device identifier corresponds to the RRC connected state of the UE, the UE sends the discovery signal by using the device identifier only when it is in the connected state.

Step 706. Optionally, if the cause value of the device identity allocation request indication received by the base station is a cell ECGI change (because the idle state UE moves out of the original camping cell), the base station sends the device identity release according to the source base station identity information sent by the UE. The request message is sent to the source base station, where the message includes the identifier information of the UE, for example, the C-RNTI of the UE in the last cell (source cell), the device identifier assigned by the source base station to the UE, and the like. Step 707. The source base station releases the device identifier assigned to the UE. Optionally, the source base station sends a device identity release confirmation message to the base station (target base station) currently serving the UE, to confirm that the device identity release is complete.

Step 708: The base station sends a device identity update message to the MME. Optionally, the message includes a new device identifier allocated by the base station to the UE. Step 708 here can also be performed prior to step 706.

Step 709. If the device identifier update message received by the MME includes a new device identifier allocated by the base station for the UE, the MME updates the device identifier of the UE. The MME sends a device identity update acknowledgement message to the base station, where the message includes network side identification information (eg, IMSI, S-TMSI, etc.) of the UE. After receiving, the base station can establish a mapping relationship between the device identifier of the UE and the network side identifier.

Method Embodiment 7:

This embodiment describes a method for an MME to allocate a device identifier to a UE in a device identity allocation process of a UE. In this embodiment, the device identity management entity is located in the MME. As shown in Figure 9, the following steps are included:

Step 801. The UE triggers the initiating device identity allocation process based on the following conditions.

Here, the conditions include any one or a combination of the following:

2) Idle state The UE detects that the TAI/discovery zone identity of its camping cell has changed. The discovery area is composed of one or more cells, and each cell in a discovery area broadcasts a discovery area identifier that uniquely identifies the discovery area;

5) Event-triggered periodicity, for example, the UE starts periodic requesting device identification allocation. Step 802. The UE sends a device identity allocation request message to the base station (if the UE is in an idle state, an RRC connection needs to be established first). Optionally, the message may further include status indication information, configured to indicate a UE status corresponding to the device identifier to be allocated. Optionally, the message includes a device identifier allocation cause value, such as exceeding a valid time range, a TAI change, a discovery area identifier change, and the like. Optionally, the message includes the MME identity information of the UE. Optionally, the message includes the MME identity information that is used to allocate the device identifier to the UE and the identity information of the UE (eg, the IMSI or S-TMSI of the UE, the device identifier assigned to the UE last time, and the like).

Step 803. The base station sends a device identity allocation request to the MME of the UE. Or, if the device identifier allocation request message sent by the UE includes the status indication information, the base station determines, according to the status indication information, whether to allocate the device identifier to the UE. Specifically, if the status indication information indicates that the device identifier to be allocated corresponds to the idle state of the UE, the base station does not allocate the device identifier to the UE, and sends a device identifier allocation request message to the MME of the UE. Optionally, the message may further include status indication information, which is used to indicate a UE status corresponding to the device identifier to be allocated. Optionally, the message includes a device identifier allocation cause value, such as exceeding a valid time range, a TAI change, a discovery area identifier change, and the like. Optionally, the message includes the MME identity information that last assigned the device identifier to the UE and the identity information of the UE.

Step 804. The MME allocates a device identifier to the UE. Alternatively, the MME may also specify a valid time range for the device identification. The device identifier can uniquely identify the UE in a tracking area or a discovery area composed of multiple cells, that is, in the tracking area or the discovery area. Or, if the device identifier allocation request message received by the MME includes status indication information, the MME determines, according to the status indication information, whether to allocate a device identifier to the UE. Specifically, if the status indication information indicates that the device identifier to be allocated corresponds to the idle state of the UE, the MME allocates the device identifier to the UE.

Step 805. The MME replies to the base station with a device identity assignment response message. The message carries the device identification information including the device identifier. If the MME allocates the valid time range of the device identifier, the device identifier information further includes a valid time range of the device identifier. Optionally, the MME may also Indicates that the assigned device identifier is used by the UE in an idle state.

Step 806. Optionally, if the cause value of the device identity allocation request indication received by the MME is a cell TAI/discovery area identifier change, the MME sends a device identity release request message to the source MME according to the source MME identity information sent by the UE, where the message is sent. The identifier information of the UE is included, for example, the IMSI or S-TMSI of the UE, the device identifier assigned by the source MME to the UE, and the like. Step 606 herein can be performed before or after step 606.

Step 807. The source MME releases the device identifier assigned to the UE. Optionally, the source MME sends a device identifier release confirmation message to the MME (target MME) currently serving the UE, to confirm that the device identifier release is complete.

Step 808: The base station sends the received device identification information to the UE by using the device identifier allocation response message, and carries the original device identifier, requesting to release the original device identifier.

Step 809. The UE parses and stores the device identification information after receiving the device identity allocation response message, and sends the discovery signal by using the device identifier in the device-to-device discovery process. If the device identification information indicates that the device identifier corresponds to the RRC idle state of the UE, the UE sends the discovery signal by using the device identifier only when in the idle state.

Method Embodiment 8:

This embodiment describes a method in which a UE requests a base station to release a device identifier. In this embodiment, the device identity management entity is located in the base station. As shown in FIG. 10, the embodiment includes the following steps: Step 901. The UE determines that the device identifier is not currently used. For example, the UE turns off the D2D module, or turns off the D2D discovery/discovery feature, or closes an application.

Step 902: The UE sends a device identity release request message to the base station (if the UE is in an idle state, an RRC connection needs to be established first). Optionally, the message may further include status indication information, configured to indicate a UE status corresponding to the device identifier that needs to be released. Optionally, the message includes a device identifier release reason value. Optionally, the message includes the MME identity information of the UE. Optionally, the message includes the device identifier to be released. Step 903: The base station releases the device identifier of the UE. Or, if the device identifier allocation request message sent by the UE includes the status indication information, the base station determines, according to the status indication information, whether the device identifier needs to be released. Specifically, if the status indication information indicates that the device identifier to be allocated corresponds to the connected state of the UE, the base station releases the device identifier allocated for the UE.

Step 904. Optionally, the base station sends a device identity release confirmation message to the UE to confirm that the device identifier has been released.

Step 905: The base station sends a device identity release notification message to the MME of the UE to notify the MME that the device identifier has been released. Optionally, the message includes a network side identifier of the UE, or a released device identifier.

Step 906. Optionally, the MME sends a device identity release confirmation message to the base station to confirm that the device identifier has been released.

Method Example 9:

This embodiment describes a method in which a UE requests an MME to release a device identifier. In this embodiment, the device identity management entity is located in the MME. As shown in FIG. 11, the embodiment includes the following steps: Step 1001. The UE determines that the device identifier is not currently used. For example, the UE turns off the D2D module, or turns off the D2D discovery/discovery feature, or closes an application.

Step 1002: The UE sends a device identity release request message to the base station (if the UE is in an idle state, an RRC connection needs to be established first). Optionally, the message may further include status indication information, configured to indicate a UE status corresponding to the device identifier that needs to be released. Optionally, the message contains the device ID release reason value. Optionally, the message includes the MME identity information of the UE. Optionally, the message contains the device ID to be released.

Step 1003: The base station sends a device identity release request message to the MME. Or, if the device identifier allocation request message sent by the UE includes the status indication information, the base station determines, according to the status indication information, whether the device identifier needs to be released. Specifically, if the status indication information indicates that the device identifier to be allocated corresponds to the idle state of the UE, the base station does not perform the release of the device identifier, but A backup identity release request message is sent to the MME. Optionally, the message may further include status indication information, configured to indicate a UE status corresponding to the device identifier that needs to be released. Optionally, the message includes a device identifier release reason value. Optionally, the message includes the device identifier to be released.

Step 1004. The MME releases the device identifier of the UE. Or, if the device identifier allocation request message received by the MME includes status indication information, the MME determines, according to the status indication information, whether the device identifier needs to be released. Specifically, if the status indication information indicates that the device identifier to be allocated corresponds to the idle state of the UE, the MME releases the device identifier allocated for the UE.

Step 1005. Optionally, the MME sends a device identity release response message to the base station to confirm that the device identifier has been released.

Step 1006. Optionally, the base station sends a device identity release response message to the UE to confirm that the device identifier has been released.

A device identification distribution system, the system includes: a device identification allocation unit and a device identification sending unit located on a device identity management entity side; wherein the device identifier allocation unit is configured to allocate a device identifier to the UE; the device identifier sending unit is configured to Sending information to the UE, the information including the device identifier; the device identifier is used to identify the UE in device-to-device discovery and/or device-to-device communication.

Preferably, the device identity allocation unit is further configured to allocate the device identifier to the UE in an attach procedure of the UE;

Preferably, the device identifier allocation unit is further configured to allocate the device identifiers used by the UE in different RRC states by different device identifier management entities; or the device identifiers used by the UE in different RRC states are managed by the same device identifier. Entity allocation. Preferably, the device identifier allocation unit is further configured to allocate to the UE that the lengths of the device identifiers used by the UE in different RRC states are different.

Preferably, the device identifier allocation unit is further configured to allocate a device identifier to the UE according to the subscription level of the UE.

Preferably, the device identifier allocation unit is further configured to allocate different device identifier lengths to UEs of different subscription levels;

Or, assigning device identifiers to UEs of different subscription levels from different device identifier sets. Preferably, the device identifier sending unit is further configured to: if the device identifier used by the UE in different RRC states is allocated by different device identifier management entities, the information sent includes the UE status corresponding to the device identifier. The UE status includes: an idle state and a connected state.

Preferably, the device identifier sending unit further configured to send the information further includes a valid time range of the device identifier.

Preferably, the device identifier allocation unit is further configured to: when the device identifier is allocated to the UE in the device identifier allocation process of the UE, after the device identifier exceeds the valid time range, receive the assignment from the UE a request for a new device identification;

Or receiving a clearing of the allocation device identifier from the event triggering periodic manner of the UE; Alternatively, receiving a request for periodic allocation of device identification from the UE.

Preferably, the system further includes: a device identifier release unit located on the device identifier management entity side, configured to release the allocated device identifier when the device identifier is required to be released, and the allocated device identifier is released.

Preferably, the device identifier release unit is further configured to determine, according to the device identifier release indication information of the UE, whether the allocated device identifier needs to be released;

Or determining, according to the device identifier release indication information of the device identifier management entity that currently allocates the device identifier to the UE, whether the allocated device identifier needs to be released;

Preferably, the device identifier release unit is further configured to: when the information sent includes the valid time range of the device identifier, after the valid time range is exceeded, it is determined that the allocated device identifier needs to be released, and the allocated device identifier is allocated. The device ID is released.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Industrial applicability

In the embodiment of the present invention, the device identification management entity allocates a device identifier to the UE; the device identifier management entity sends information to the UE, where the information includes the device identifier. In the embodiment of the present invention, the network side allocates an identifier to the UE in the D2D scenario.

Claims

claims

1. A method of assigning device identification, the method includes:

The equipment identification management entity allocates equipment identification to the user equipment UE;

The device identity management entity sends information to the UE, where the information includes the device identity.

2. The method according to claim 1, wherein the device identity management entity allocates a device identity to the UE, further comprising:

The device identity management entity allocates a device identity to the UE during the attachment process of the UE; or, the device identity management entity allocates a device identity to the UE during the tracking area update process of the UE;

Alternatively, the device identity management entity allocates a device identity to the UE during the UE's service request process;

Alternatively, the device identity management entity allocates a device identity to the UE during the handover process of the UE;

Alternatively, the device identity management entity allocates a device identity to the UE during the device identity allocation process of the UE.

3. The method according to claim 2, wherein the device identity management entity allocates a device identity to the UE during the handover process of the UE, further comprising:

The first device identity management entity instructs the second device identity management entity explicitly or implicitly that the UE needs to allocate a new device identity; the first device identity management entity is the source device identity management entity of the UE; The second device identity management entity is the target device identity management entity of the UE.

4. The method according to claim 1, wherein the device identity management entity allocates a device identity to the UE, further comprising:

The device identities used by UE in different RRC states are allocated by different device identity management entities; Alternatively, the device identities used by the UE in different RRC states are allocated by the same device identity management entity.

5. The method according to claim 4, wherein the device identities used by the UE in different RRC states are allocated by different device identity management entities, and further includes:

The device identity used by the UE in the connected state is allocated by the base station, and the device identity used by the UE in the idle state is allocated by the mobility management entity.

6. The method according to claim 1, wherein the device identity management entity allocates a device identity to the UE, further comprising:

The lengths of the device identities allocated by the device identity management entity for use by the UE in different RRC states are different.

7. The method according to claim 1, wherein the device identity management entity allocates a device identity to the UE, further comprising:

The device identity management entity allocates a device identity to the UE according to the subscription level of the UE.

8. The method according to claim 7, wherein the device identity management entity allocates a device identity to the UE according to the subscription level of the UE, further comprising:

The device identity management entity allocates different lengths of device identities to UEs of different subscription levels;

Alternatively, the device identity management entity allocates device identities from different device identity sets to UEs of different subscription levels.

9. The method according to claim 1, wherein the device identity management entity sends information to the UE, the information includes the device identity, and further includes:

When the device identifiers used by the UE in different RRC states are allocated by different device identifier management entities, the information also includes the UE state corresponding to the device identifier; the UE state includes: idle state and connected state.

10. The method according to claim 1, wherein the device identity management entity sends information to the UE, the information includes the device identity, and further includes:

The information also includes a valid time range of the device identification.

11. The method according to claim 2, wherein the device identity management entity allocates a device identity to the UE during the device identity allocation process of the UE, further comprising:

If the information received by the UE from the device identity management entity contains the valid time range of the device identity, after the device identity exceeds the valid time range, the UE requests the device identity management entity to allocate a new device identity;

Alternatively, if the UE detects that the cell identity broadcast by the cell where it currently resides changes, the UE requests the device identity management entity to allocate a new device identity;

Alternatively, if the UE detects a change in the tracking area code broadcast by the cell where it currently resides, the UE requests the equipment identification management entity to allocate a new equipment identification;

Or, if the UE detects that the discovery area identity broadcast by the cell where it is currently camped changes, the UE requests the device identity management entity to allocate a new device identity;

Alternatively, the UE requests the device identity management entity to allocate a device identity based on an event-triggered manner;

Alternatively, the UE requests the device identity management entity to allocate a device identity based on an event-triggered periodic manner;

Alternatively, the UE periodically requests the device identity management entity to allocate a device identity.

12. The method according to any one of claims 1 to 11, wherein after the device identity management entity allocates a device identity to the UE, the method further includes:

The device identity management entity determines whether the allocated device identity needs to be released. If the device identity needs to be released, the allocated device identity is released.

13. The method according to claim 12, wherein the device identity management entity determines whether the allocated device identity needs to be released, further comprising: The device identity management entity determines whether the allocated device identity needs to be released based on the device identity release indication information of the UE;

Alternatively, the device identity management entity determines whether the allocated device identity needs to be released based on the device identity release indication information of the device identity management entity that currently allocates a device identity to the UE;

Alternatively, the device identity management entity determines whether the allocated device identity needs to be released based on the device identity release indication information of other network elements.

14. The method according to claim 13, wherein the device identity management entity determines whether the allocated device identity needs to be released based on the device identity release indication information of the UE, and further includes:

If the UE determines that it does not need to use the device identity currently, it sends device identity release indication information to instruct the device identity management entity to release the device identity allocated for the UE.

15. The method according to claim 13, wherein the device identity management entity determines whether the allocated device identity needs to be released based on the device identity release indication information of the device identity management entity that currently allocates a device identity to the UE, and further include:

The device identity management entity that currently allocates a device identity to the UE indicates that the last time it was assigned to the UE is based on the identity information of the device identity management entity that last assigned a device identity to the UE and the identity information of the UE sent by the UE. The device identity management entity that allocates the device identity to the UE releases the device identity that has been allocated to the UE.

16. The method according to claim 12, wherein the device identity management entity determines whether the allocated device identity needs to be released, further comprising:

If the information sent by the device identity management entity to the UE indicates the valid time range of the device identity, after the valid time range is exceeded, the device identity management entity determines that the allocated device identity needs to be released, and the allocated device identity is The assigned device ID is released.

17. The method according to any one of claims 1 to 11, wherein the device management implementation The device identity assigned by the entity to the UE consists of any one or more of the following:

Identification information for device-to-device use;

The temporary mobile subscriber identity TMSI of the UE;

The International Mobile Subscriber Identity IMSI of the UE;

The cell radio network temporary identifier C-RNTI of the UE;

The IP address of the UE;

The tracking area TA identification information where the UE is located.

18. A device identity distribution system, the system includes: a device identity distribution unit and a device identity sending unit located on the device identity management entity side; wherein,

The device identity allocation unit is configured to allocate a device identity to the UE;

The device identification sending unit is configured to send information to the UE, where the information includes the device identification.

19. The system according to claim 18, wherein the device identity allocation unit is further configured to allocate a device identity to the UE during the attachment process of the UE;

Or, allocate a device identity to the UE during the UE's tracking area update process; or allocate a device identity to the UE during the UE's service request process;

Or, assign a device identity to the UE during the handover process of the UE;

Alternatively, the UE is assigned a device identity during the UE's device identity allocation process.

20. The system according to claim 18, wherein the device identity allocation unit is further configured so that the device identities used by the UE in different RRC states are allocated by different device identity management entities; or, the device identities used by the UE in different RRC states are allocated by different device identity management entities. The device identity used in the state is assigned by the same device identity management entity.

21. The system according to claim 18, wherein the device identity allocation unit is further configured to allocate different lengths of device identities to the UE for use by the UE in different RRC states.

22. The system according to claim 18, wherein the device identity allocation unit is further configured to allocate a device identity to the UE according to the subscription level of the UE.

23. The system according to claim 22, wherein the device identity allocation unit is further configured to allocate device identities of different lengths to UEs of different subscription levels;

Alternatively, allocate device identities from different device identity sets to UEs of different subscription levels.

24. The system according to claim 18, wherein the device identity sending unit is further configured to send the information when the device identities used by the UE in different RRC states are allocated by different device identity management entities. also includes the UE state corresponding to the device identifier; the UE state includes: idle state and connected state.

25. The system according to claim 18, wherein the device identification sending unit is further configured so that the information sent also includes a valid time range of the device identification.

26. The system according to claim 19, wherein the device identity allocation unit is further configured to allocate a device identity to the UE during the device identity allocation process of the UE, and the device identity exceeds the valid limit. After the time range, receive a request from the UE to allocate a new device identity;

Or, when the UE detects that the cell identity broadcast by the cell where it currently resides changes, it receives a request from the UE to allocate a new device identity;

Or, when the UE detects that the tracking area code broadcast by the cell where it is currently camped changes, it receives a request from the UE to allocate a new device identity;

Or, when the UE detects that the discovery area identifier broadcast by the cell where it is currently camped changes, it receives a request from the UE to allocate a new device identifier;

Or, receive a request from the UE to allocate a device identity based on an event-triggered manner;

Alternatively, receive a request from the UE to allocate a device identity in a periodic manner based on event triggering; Alternatively, receive a periodic request for allocating a device identity from the UE.

27. The system according to any one of claims 18 to 26, wherein the system further includes: a device identity release unit located on the device identity management entity side, configured to determine that the allocated device identity needs to be released after it has been allocated. When a device ID is issued, the assigned device ID is released.

28. The system according to claim 27, wherein the device identity release unit is further configured to determine whether the allocated device identity needs to be released based on the device identity release indication information of the UE;

Or, determine whether the allocated device identity needs to be released based on the device identity release indication information of the device identity management entity that currently assigns the device identity to the UE;

Or, determine whether the allocated device identity needs to be released based on the device identity release indication information of other network elements.

29. The system according to claim 27, wherein the device identification releasing unit is further configured to determine that when the information sent also contains a valid time range of the device identification, it is determined that the valid time range is exceeded. The allocated device ID needs to be released and the allocated device ID needs to be released.