WO2014146473A1 - Procédé et système d'allocation d'identification d'équipement - Google Patents

Procédé et système d'allocation d'identification d'équipement Download PDF

Info

Publication number
WO2014146473A1
WO2014146473A1 PCT/CN2013/091088 CN2013091088W WO2014146473A1 WO 2014146473 A1 WO2014146473 A1 WO 2014146473A1 CN 2013091088 W CN2013091088 W CN 2013091088W WO 2014146473 A1 WO2014146473 A1 WO 2014146473A1
Authority
WO
WIPO (PCT)
Prior art keywords
device identity
management entity
device identifier
allocated
identity
Prior art date
Legal status (The legal status is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the status listed.)
Ceased
Application number
PCT/CN2013/091088
Other languages
English (en)
Chinese (zh)
Inventor
黄莹
陈琳
谢峰
鲁照华
罗宇民
马书宇
刘玉兰
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
ZTE Corp
Original Assignee
ZTE Corp
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by ZTE Corp filed Critical ZTE Corp
Publication of WO2014146473A1 publication Critical patent/WO2014146473A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support

Definitions

  • 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
  • D2D device-to-device
  • 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.
  • D2D User Equipment D2D User Equipment
  • Direct communication There are three main types of D2D applications:
  • 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.
  • D2D technology usually includes D2D discovery technology and D2D communication technology:
  • 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.
  • 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.
  • D2D user equipment can discover each other by sending or receiving discovery signals/information.
  • 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.
  • 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
  • the main purpose of the embodiments of the present invention is to provide a method and system for allocating device identifiers.
  • the network side can assign an identifier to the UE.
  • 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;
  • the device identifier management entity allocates a device identifier to the UE in a service request process of the UE;
  • the device identifier management entity allocates a device identifier to the UE in a handover process of the UE;
  • 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;
  • 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
  • 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:
  • the information further includes the UE state corresponding to the device identifier; the UE state includes: an idle state and a connected state.
  • the device identifier management entity sends information to the UE, where the information includes the device identifier, and further includes:
  • 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:
  • the UE 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.
  • the UE requests the device identity management entity to allocate a new device identifier
  • the UE requests the device identity management entity to allocate a new device identifier
  • the UE requests the device identity management entity to allocate a new device identifier
  • the UE requests the device identity management entity to allocate a device identifier according to an event-triggered manner
  • the UE allocates a device identifier to the device identity management entity request according to an event-triggered periodic manner
  • the UE periodically requests the device identity management entity to allocate a device identifier.
  • 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;
  • 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:
  • 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.
  • the device identifier management entity determines whether it is necessary to release the allocated device identifier, and further includes:
  • 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:
  • IMSI International Mobile Subscriber Identity
  • the cell radio network of the UE temporarily identifies a C-RNTI
  • the tracking area TA where the UE is located identifies information.
  • a device identification distribution 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.
  • CPU central processing unit
  • DSP digital signal processor
  • programmable signal array when performing processing.
  • 1 J FPGA, Field - Programmable Gate Array
  • the device identifier allocation unit is further configured to allocate a device identifier to the UE in an attaching process of the UE;
  • 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;
  • the device identifier is allocated to the UE in a handover process of the UE;
  • 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;
  • the UE 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;
  • the UE 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;
  • 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.
  • 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;
  • 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.
  • 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.
  • the network side allocates an identifier to the UE in the D2D scenario.
  • FIG. 1 is a schematic diagram of an application mode in which D2D technology is applied
  • FIG. 2 is a schematic diagram of an implementation process of a method according to an embodiment of the present invention.
  • FIG. 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.
  • FIG. 7 is a schematic flowchart of an implementation process of Embodiment 5 of the method according to the present invention.
  • Embodiment 7 of the method according to the present invention.
  • Embodiment 8 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
  • 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 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.
  • 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;
  • the device identifier management entity allocates a device identifier to the UE in a tracking area update process of the UE;
  • the device identifier management entity allocates a device identifier to the UE in a service request process of the UE;
  • the device identifier management entity allocates a device identifier to the UE in a handover process of the UE;
  • the device identity management entity allocates a device identity to the UE in a device identity allocation process of the UE.
  • the device identifier management entity allocates the 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 identifier used by the UE in different RRC states is managed by a different device identifier. Assignment
  • 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 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.
  • 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.
  • 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.
  • the device identifier management entity allocates the 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
  • 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:
  • the information includes one or more device identifiers.
  • the information may further include an effective time range of the device identifier.
  • the device identifier management entity sends information to the UE, where the information includes the device identifier, and further includes:
  • the information also indicates the UE status corresponding to the device identifiers.
  • the UE status includes: an idle state and a connected state.
  • 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;
  • the UE requests the device identity management entity to allocate a new device identifier
  • the UE requests the device identity management entity to allocate a new device identifier
  • the UE requests the device identity management entity to allocate a new device identifier
  • the UE requests the device identity management entity to allocate a device identifier according to an event-triggered manner
  • the UE allocates a device identifier to the device identity management entity request according to an event-triggered periodic manner
  • the UE periodically requests the device identity management entity to allocate a device identifier.
  • 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.
  • the identifier information of the UE includes, but is not limited to: a device identifier that was last allocated 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.
  • the UE stores the information, and uses the information in device-to-device discovery and/or device-to-device communication, and further includes:
  • the UEs 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.
  • 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.
  • the mechanism for releasing the device identifier allocated in the D2D scenario can also be supported.
  • 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.
  • 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.
  • 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.
  • 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;
  • 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;
  • 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:
  • 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, 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.
  • the device identity management entity determines whether it is necessary to release the allocated device identifier. Also includes:
  • 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 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.
  • HSS contracting server
  • the device management entity allocates a device identifier to the UE by one or more of the following:
  • TMSI Temporary Mobile Subscriber Identity
  • C-RNTI cell radio network temporary identifier
  • the tracking area (TA) where the UE is located identifies information.
  • 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.
  • 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.
  • the device identifier is used to identify the UE in device-to-device discovery and/or device-to-device communication.
  • 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.
  • 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.
  • S-GW serving serving gateway
  • P-GW packet data gateway
  • EPS evolved packet system
  • 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.
  • 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.
  • the base station may further specify 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.
  • 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.
  • 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.
  • 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.
  • one or more device identifiers may be included in the device identification information.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • the HSS replies to the target MME with a location update confirmation message.
  • the MME allocates a device identifier to the UE.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • one or more device identifiers may be included in the device identification information.
  • 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.
  • 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.
  • 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.
  • the MME may also specify a valid time range of the device identifier.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • D2D device-to-device
  • 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.
  • 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.
  • 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.
  • the MME may further specify a valid time range of the device identifier.
  • 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.
  • 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.
  • 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.
  • the network side identifier information of the UE for example, IMSI, S-TMSI, etc.
  • the message carries the device identifier information including the device identifier.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the UE 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.
  • 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.
  • 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:
  • the conditions include any one or a combination of the following:
  • the UE in the idle state or the connected state detects that the allocated device identifier exceeds the valid time range
  • the idle state UE detects that the ECGI of the camped cell changes
  • Event triggering for example, the UE opens the D2D module, the UE opens an application, and the UE starts the D2D discovery/discovery function;
  • the UE 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;
  • 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).
  • the message may further include status indication information, configured to indicate a UE status corresponding to the device identifier to be allocated.
  • the message contains the device identifier. Assign the cause value, such as the valid time range, ECGI change, etc.
  • the message includes the MME identity information of the UE.
  • 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).
  • the base station allocates a device identifier to the UE.
  • 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.
  • 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.
  • 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 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • the conditions include any one or a combination of the following:
  • the UE in the idle state or the connected state detects that the allocated device identifier exceeds the valid time range
  • 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;
  • Event triggering for example, the UE opens the D2D module, the UE opens an application, and the UE starts the D2D discovery/discovery function;
  • the UE 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;
  • 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).
  • the message may further include status indication information, configured to indicate a UE status corresponding to the device identifier to be allocated.
  • 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.
  • the message includes the MME identity information of the UE.
  • 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).
  • 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.
  • the base station sends a device identity allocation request to the MME of the UE.
  • 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.
  • the message may further include status indication information, which is used to indicate a UE status corresponding to the device identifier to be allocated.
  • 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.
  • the message includes the MME identity information that last assigned the device identifier to the UE and the identity information of the UE.
  • the MME allocates a device identifier to the UE.
  • 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.
  • 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 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.
  • 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.
  • This embodiment describes a method in which a UE requests a base station to release a device identifier.
  • the device identity management entity is located in the base station.
  • 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).
  • the message may further include status indication information, configured to indicate a UE status corresponding to the device identifier that needs to be released.
  • the message includes a device identifier release reason value.
  • the message includes the MME identity information of the UE.
  • the message includes the device identifier to be released.
  • 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.
  • 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.
  • the message includes a network side identifier of the UE, or a released device identifier.
  • Step 906 the MME sends a device identity release confirmation message to the base station to confirm that the device identifier has been released.
  • This embodiment describes a method in which a UE requests an MME to release a device identifier.
  • the device identity management entity is located in the MME.
  • 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).
  • the message may further include status indication information, configured to indicate a UE status corresponding to the device identifier that needs to be released.
  • the message contains the device ID release reason value.
  • the message includes the MME identity information of the UE.
  • 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.
  • the message may further include status indication information, configured to indicate a UE status corresponding to the device identifier that needs to be released.
  • the message includes a device identifier release reason value.
  • 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. the MME sends a device identity release response message to the base station to confirm that the device identifier has been released.
  • Step 1006 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 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.
  • the device identity allocation unit is further configured to allocate the device identifier to the UE in an attach procedure of the UE;
  • 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;
  • the device identifier is allocated to the UE in a handover process of the UE;
  • 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 managed by the same device identifier. Entity allocation.
  • 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.
  • 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;
  • 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.
  • the device identifier sending unit further configured to send the information further includes a valid time range of the device identifier.
  • 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;
  • the UE 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;
  • the UE 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;
  • receiving a clearing of the allocation device identifier from the event triggering periodic manner of the UE Or receiving a request for periodic allocation of device identification from the UE.
  • 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.
  • 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.
  • 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;
  • 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 allocated device identifier is allocated. The device ID is released.
  • 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.
  • the network side allocates an identifier to the UE in the D2D scenario.

Landscapes

  • Engineering & Computer Science (AREA)
  • Databases & Information Systems (AREA)
  • Computer Networks & Wireless Communication (AREA)
  • Signal Processing (AREA)
  • Mobile Radio Communication Systems (AREA)

Abstract

L'invention concerne un procédé et un système d'allocation d'identification d'équipement. Selon le procédé : une entité de gestion d'identification d'équipement alloue une identification d'équipement à un équipement utilisateur (UE) ; et l'entité de gestion d'identification d'équipement envoie des informations à l'UE, les informations contenant l'identification d'équipement. Dans le système, une unité d'allocation d'identification d'équipement est configurée pour allouer l'identification d'équipement à l'UE ; et une unité d'envoi d'identification d'équipement sert à envoyer des informations à l'UE, les informations contenant l'identification d'équipement. En adoptant la présente invention, un côté de réseau peut allouer une identification à un UE dans un scénario dispositif-dispositif.
PCT/CN2013/091088 2013-03-21 2013-12-31 Procédé et système d'allocation d'identification d'équipement Ceased WO2014146473A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
CN201310092314.4 2013-03-21
CN201310092314.4A CN104066078A (zh) 2013-03-21 2013-03-21 一种设备标识的分配方法及系统

Publications (1)

Publication Number Publication Date
WO2014146473A1 true WO2014146473A1 (fr) 2014-09-25

Family

ID=51553566

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/CN2013/091088 Ceased WO2014146473A1 (fr) 2013-03-21 2013-12-31 Procédé et système d'allocation d'identification d'équipement

Country Status (2)

Country Link
CN (1) CN104066078A (fr)
WO (1) WO2014146473A1 (fr)

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3386265A4 (fr) * 2015-12-04 2019-09-04 LG Electronics Inc. -1- Procédé et appareil pour transmettre une identité d'équipement utilisateur dans un système de communication sans fil
EP3749051A4 (fr) * 2018-01-30 2021-01-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé d'attribution d'identifiant d'ue, dispositif de réseau, ue, et support d'informations d'ordinateur

Families Citing this family (11)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US10873982B2 (en) * 2014-07-31 2020-12-22 Sharp Kabushiki Kaisha Terminal apparatus, control method, and integrated circuit
WO2016112499A1 (fr) * 2015-01-13 2016-07-21 华为技术有限公司 Procédé d'indication de ressource, point d'accès et terminal
CN106162777B (zh) * 2015-04-09 2021-03-26 中兴通讯股份有限公司 中继节点切换方法及系统
CN108028863B (zh) * 2015-09-21 2021-10-22 Lg 电子株式会社 处理针对d2d通信系统的id冲突的方法及其设备
CN108377569A (zh) * 2016-10-17 2018-08-07 华为技术有限公司 分配用户标识的方法和运营商设备
CN108023875A (zh) * 2017-11-16 2018-05-11 广州视源电子科技股份有限公司 一种设备授权方法及系统
CN109963340B (zh) * 2017-12-25 2022-07-01 上海诺基亚贝尔股份有限公司 用于降低信令开销和数据延迟的方法、设备及计算机可读介质
CN112019647B (zh) 2018-02-12 2025-06-03 华为技术有限公司 一种获得设备标识的方法及装置
CN108966185B (zh) * 2018-08-16 2021-10-26 Oppo（重庆）智能科技有限公司 一种资源释放方法、终端及计算机可读存储介质
CN116319678B (zh) * 2023-03-17 2025-08-15 统信软件技术有限公司 节点标识的管理方法、全局标识的生成方法及计算设备
CN119136189A (zh) * 2024-08-15 2024-12-13 中国移动通信有限公司研究院 一种通信设备的身份标识分配方法及网络装置、核心网设备、存储介质、计算机程序产品

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101507348A (zh) * 2006-08-21 2009-08-12 高通股份有限公司 用于在正交多址通信系统中进行随机接入的方法和装置
CN101583155A (zh) * 2008-05-16 2009-11-18 大唐移动通信设备有限公司 移动性管理实体上的负载迁移方法及通信设备
CN102045834A (zh) * 2009-10-14 2011-05-04 大唐移动通信设备有限公司 一种TA List的分配方法及装置
US20130016703A1 (en) * 2011-07-11 2013-01-17 Renesas Mobile Corporation User Identifier Multiplexing By Time Division

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN101507348A (zh) * 2006-08-21 2009-08-12 高通股份有限公司 用于在正交多址通信系统中进行随机接入的方法和装置
CN101583155A (zh) * 2008-05-16 2009-11-18 大唐移动通信设备有限公司 移动性管理实体上的负载迁移方法及通信设备
CN102045834A (zh) * 2009-10-14 2011-05-04 大唐移动通信设备有限公司 一种TA List的分配方法及装置
US20130016703A1 (en) * 2011-07-11 2013-01-17 Renesas Mobile Corporation User Identifier Multiplexing By Time Division

Cited By (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP3386265A4 (fr) * 2015-12-04 2019-09-04 LG Electronics Inc. -1- Procédé et appareil pour transmettre une identité d'équipement utilisateur dans un système de communication sans fil
US10595195B2 (en) 2015-12-04 2020-03-17 Lg Electronics Inc. Method and apparatus for transmitting UE ID in wireless communication system
US10945123B2 (en) 2015-12-04 2021-03-09 Lg Electronics Inc. Method and apparatus for transmitting UE ID in wireless communication system
EP3749051A4 (fr) * 2018-01-30 2021-01-06 Guangdong Oppo Mobile Telecommunications Corp., Ltd. Procédé d'attribution d'identifiant d'ue, dispositif de réseau, ue, et support d'informations d'ordinateur

Also Published As

Publication number Publication date
CN104066078A (zh) 2014-09-24

Similar Documents

Publication Publication Date Title
WO2014146473A1 (fr) Procédé et système d'allocation d'identification d'équipement
EP3399824B1 (fr) Procédé de programmation de données, station de base et système
US10880710B2 (en) Method and apparatus for communication of terminal in mobile communication system
KR102039908B1 (ko) 단말간 통신을 위한 상태 천이 방법 및 장치
US11589208B2 (en) Method for transmitting data in CIoT system and device therefor
US9088967B2 (en) Wireless communication system and connection method between user equipment and a mobility management entity
CN104066070B (zh) 终端注册方法、终端发现方法、终端及装置
JP6031529B2 (ja) モバイル通信システム、モバイル通信ネットワーク、インフラストラクチャ機器、モビリティマネージャ、方法およびコンピュータプログラム
JP6084035B2 (ja) パケットデータ網ゲートウェイ選択方法
CN101400153B (zh) 用户设备通过hnb接入系统直接通信的方法
CN105338513B (zh) 设备到设备业务处理方法及装置
CN107231623B (zh) 一种数据调度方法、基站及系统
JPWO2020032127A1 (ja) 中継装置
JP5484581B2 (ja) 緊急サービスユーザの呼び出し方法及び呼び出しシステム
US20140348081A1 (en) Method for handling proximity-based service discovery and communication in a wireless communications system
EP3496477B1 (fr) Procédé, dispositif et système de radiorecherche, et support lisible par ordinateur associé
WO2015004142A1 (fr) Procédé pour décider de transférer un équipement utilisateur dans un réseau de communication mobile
WO2014166439A1 (fr) Procédé de décision de multidiffusion de partage, terminal de partage, serveur de partage et support de stockage
CN104283602A (zh) 集群中继方法、装置及系统
CN104301954A (zh) 切换方法、装置、基站和系统
CN101626566B (zh) 实现isr场景下终端迁移的方法和设备
KR20130008482A (ko) 인프라 통신을 이용하여 직접 통신을 지원하는 단말 및 그의 직접 통신 방법
CN101925037A (zh) 建立通话的方法及基站
KR101598598B1 (ko) 지능적 서비스를 제공하는 통합 기지국 장치 및 그 방법
KR20160092388A (ko) 이동형 소형셀에서 로컬 서비스 제공을 위한 세션 제어 방법 및 장치

Legal Events

Date Code Title Description
121 Ep: the epo has been informed by wipo that ep was designated in this application

Ref document number: 13879218

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 13879218

Country of ref document: EP

Kind code of ref document: A1