U.S. patent application number 14/736112 was filed with the patent office on 2015-10-01 for connection establishment method and user equipment.
The applicant listed for this patent is Huawei Technologies Co., Ltd.. Invention is credited to Li CHAI, Bo LIN.
Application Number | 20150282236 14/736112 |
Document ID | / |
Family ID | 48469118 |
Filed Date | 2015-10-01 |
United States Patent
Application |
20150282236 |
Kind Code |
A1 |
CHAI; Li ; et al. |
October 1, 2015 |
CONNECTION ESTABLISHMENT METHOD AND USER EQUIPMENT
Abstract
The present invention provides a connection establishment method
and a user equipment. The connection establishment method includes:
acquiring, by a second user equipment supporting a device to device
(D2D) function, first user equipment information of a first user
equipment supporting the D2D function; and initiating, by the
second user equipment, a connection establishment process with a
network-side device after the second user equipment determines that
a connection with the first user equipment is established according
to the first user equipment information, and sending the first user
equipment information to the network-side device in the connection
establishment process, so that a connection is established between
the network-side device and the first user equipment. The present
invention can realize establishment of a DPS bearer between the
user equipments supporting the D2D function, realize communication
between the user equipments supporting the D2D function and further
realize resource controllability of a network.
Inventors: |
CHAI; Li; (Beijing, CN)
; LIN; Bo; (Beijing, CN) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
Huawei Technologies Co., Ltd. |
Shenzhen |
|
CN |
|
|
Family ID: |
48469118 |
Appl. No.: |
14/736112 |
Filed: |
June 10, 2015 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
14281487 |
May 19, 2014 |
9084222 |
|
|
14736112 |
|
|
|
|
PCT/CN2012/085016 |
Nov 22, 2012 |
|
|
|
14281487 |
|
|
|
|
Current U.S.
Class: |
370/329 |
Current CPC
Class: |
H04W 72/04 20130101;
H04W 88/02 20130101; H04W 76/14 20180201 |
International
Class: |
H04W 76/02 20060101
H04W076/02; H04W 72/04 20060101 H04W072/04 |
Foreign Application Data
Date |
Code |
Application Number |
Nov 22, 2011 |
CN |
201110374011.2 |
Claims
1. A connection establishment method, comprising: acquiring, by a
first user equipment (UE) supporting a device to device (D2D)
function, a resource that is used to send information of the first
UE, wherein the information of the first UE comprises at least one
of an identifier, service information, a service code, and
application layer service information of the first UE; and sending,
by the first UE, the information of the first UE on the resource to
a second UE.
2. The method of claim 1, wherein before acquiring the resource,
the method further comprises: sending, by the first UE, an attach
request message to a base station, wherein the attach request
message comprises a D2D connection type parameter, and the attach
request message is used for indicating the base station to connect
with the first UE; wherein the resource is allocated by the base
station.
3. The method of claim 1, further comprising: sending, by the first
UE, an attach request message to a base station; wherein the attach
request message is used for indicating the base station to send a
initial UE message to a mobility management entity according to the
attach request message, wherein the initial UE message is used for
indicating the mobility management entity to send an initial
context setup request message to the base station according to the
initial UE message, and wherein the initial context setup request
message comprises indication information, the indication
information configured for indicating the base station that the
first UE supports the D2D function.
4. The method of claim 1, wherein a protocol stack of an air
interface between the first UE and the second UE comprises a user
plane protocol stack, wherein the user plane protocol stack
comprises at least one of internet protocol, media access control-d
information, and physical layer information.
5. A user equipment (UE) supporting a device to device (D2D)
function, the UE comprising: a receiver, configured to acquire a
resource used to send information of the UE, wherein the
information of the UE comprises at least one of an identifier,
service information, a service code, and application layer service
information of the UE; and a transmitter, configured to send the
information of the UE on the resource to another UE, wherein the
another UE supports the D2D function.
6. The UE of claim 5, wherein the transmitter is further configured
to send an attach request message to a base station before the
receiver acquires the resource, wherein the attach request message
comprises a D2D connection type parameter, and the attach request
message is used for indicating the base station to connect with the
UE; and wherein the resource is allocated by the base station.
7. The UE of claim 5, wherein the transmitter is further configured
to send an attach request message to a base station, wherein the
attach request message is used for indicating the base station to
send a initial UE message to a mobility management entity according
to the attach request message; wherein the initial UE message is
used for indicating the mobility management entity to send an
initial context setup request message to the base station according
to the initial UE message; and wherein the initial context setup
request message comprises indication information, the indication
information configured for indicating the base station that the UE
supports the D2D function.
8. The UE of claim 5, wherein a protocol stack of an air interface
between the UE and the another UE comprises a user plane protocol
stack, wherein the user plane protocol stack comprises at least one
of internet protocol, media access control-d information, and
physical layer information.
Description
CROSS-REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. patent
application Ser. No. 14/281,487, filed on May 19, 2014, which is a
continuation of International Patent Application No.
PCT/CN2012/085016, filed on Nov. 22, 2012, which claims priority to
Chinese Patent Application No. 201110374011.2, filed on Nov. 22,
2011. The afore-mentioned patent applications are hereby
incorporated by reference in their entireties.
FIELD OF TECHNOLOGY
[0002] The present invention relates to the field of communication
technologies, and particularly, to a connection establishment
method and a user equipment.
BACKGROUND OF THE INVENTION
[0003] A device to device (device to device, D2D for short below)
communication technology may realize services and data applications
of a local ad-hoc network and short-distance communication.
[0004] In order to improve the utilization rate of frequency
spectra, a D2D system and a cellular system share a same resource.
When a D2D terminal in the D2D system is connected to the cellular
system, it should follow time and time slot of the cellular system.
The D2D system may support services such as information sharing,
games, social services, mobile advertising and the like.
[0005] In the prior art, the D2D terminal in the D2D system
independently performs communication matching with other D2D
terminal(s) by using its own perceptive function according to a
perceived result, which does not need control and allocation of an
evolved packet core (Evolved Packet Core, EPC for short
below)/evolved universal mobile telecommunications system
terrestrial radio access network (Evolved Universal Mobile
Telecommunications System Terrestrial Radio Access Network, E-UTRAN
for short below), and is not authenticated and authorized by an
operator network, and thus is not favorable for reasonable
allocation of resources and secure operation of networks.
SUMMARY OF THE INVENTION
[0006] The present invention provides a connection establishment
method and a user equipment, for realizing communication between
user equipments supporting a D2D function and realizing resource
controllability of a network.
[0007] One aspect of the present invention provides a connection
establishment method, including:
[0008] acquiring, by a second user equipment supporting a device to
device (D2D) function, first user equipment information broadcasted
by a first user equipment supporting the D2D function; and
[0009] initiating, by the second user equipment, a connection
establishment process with a network-side device after the second
user equipment determines that a connection with the first user
equipment is established according to the first user equipment
information, and sending the first user equipment information to
the network-side device in the connection establishment process, so
as a connection is established between the network-side device and
the first user equipment.
[0010] Another aspect of the present invention provides a user
equipment, wherein the user equipment is a second user equipment
supporting a D2D function, and the user equipment includes:
[0011] an acquiring module, configured to acquire first user
equipment information broadcasted by a first user equipment
supporting the D2D function;
[0012] a determining module, configured to determine that a
connection with the first user equipment is established according
to the first user equipment information acquired by the acquiring
module; and
[0013] an initiating module, configured to initiate a connection
establishment process with a network-side device and send the first
user equipment information to the network-side device in the
connection establishment process, so that a connection is
established between the network-side device and the first user
equipment.
[0014] Through embodiments of the present invention, after the
second user equipment determines that the connection with the first
user equipment is established according to the information
broadcasted by the first user equipment, the second user equipment
initiates the connection establishment process with the
network-side device and sends the first user equipment information
to the network-side device in the connection establishment process,
so that a connection is established between the network-side device
and the first user equipment. Therefore, a D2D evolved packet
system (D2D Evolved Packet System, DPS for short below) bearer can
be established between the user equipments supporting the D2D
function, communication between the user equipment supporting the
D2D function is realized, and resource controllability of the
network can further be realized.
BRIEF DESCRIPTION OF THE DRAWINGS
[0015] To illustrate technical solutions in the embodiments of the
present invention or in the prior art more clearly, a brief
introduction on the accompanying drawings which are needed in the
description of the embodiments or the prior art is given below.
Apparently, the accompanying drawings in the description below are
merely some of the embodiments of the present invention, based on
which other drawings can be obtained by those of ordinary skill in
the art without any creative effort.
[0016] FIG. 1 is a flowchart of an embodiment of a connection
establishment method according to the present invention;
[0017] FIG. 2A and FIG. 2B are flowcharts of another embodiment of
the connection establishment method according to the present
invention;
[0018] FIG. 3 is a flowchart of a further embodiment of the
connection establishment method according to the present
invention;
[0019] FIGS. 4a-4c are schematic diagrams of an embodiment of
bearer mapping according to the present invention;
[0020] FIG. 5A and FIG. 5B are flowcharts of a still further
embodiment of the connection establishment method according to the
present invention;
[0021] FIG. 6 is a flowchart of an embodiment of a dedicated bearer
activation flow according to the present invention;
[0022] FIG. 7 is a flowchart of a still further embodiment of the
connection establishment method according to the present
invention;
[0023] FIG. 8 is a structure schematic diagram of an embodiment of
a user equipment according to the present invention;
[0024] FIG. 9 is a structure schematic diagram of another
embodiment of the user equipment according to the present
invention;
[0025] FIGS. 10a-10b are schematic diagrams of a user plane
protocol stack according to the present invention.
DETAILED DESCRIPTION OF THE EMBODIMENTS
[0026] To make objectives, technical solutions and advantages of
embodiments of the present invention clearer, a clear and complete
description of the technical solutions in the embodiments of the
present invention will be given below, in combination with the
accompanying drawings in the embodiments of the present invention.
Apparently, the embodiments described are merely a part, but not
all, of the embodiments of the present invention. All of other
embodiments, obtained by those of ordinary skill in the art based
on the embodiments of the present invention without any creative
effort, fall into the protection scope of the present
invention.
[0027] FIG. 1 is a flowchart of an embodiment of a connection
establishment method according to the present invention. As shown
in FIG. 1, the connection establishment method may include:
[0028] Step 101, a second user equipment supporting a D2D function
acquires first user equipment information of a first user equipment
supporting the D2D function.
[0029] Step 102, the second user equipment initiates a connection
establishment process with a network-side device after the second
user equipment determines that a connection with the first user
equipment is established according to the first user equipment
information, and sends the first user equipment information to the
network-side device in the connection establishment process, so
that a connection is established between the network-side device
and the first user equipment.
[0030] In this embodiment, the above-mentioned first user equipment
information includes service information of the first user
equipment and an identifier of the first user equipment. Or, the
above-mentioned first user equipment information includes a service
code, wherein the service code is used for indicating the service
information of the first user equipment and the identifier of the
first user equipment.
[0031] In this embodiment, after the second user equipment
initiates the connection establishment process with the
network-side device and the connection is established between the
network-side device and the first user equipment, establishment of
a DPS bearer between the second user equipment and the first user
equipment is completed, and the second user equipment and the first
user equipment start D2D communication.
[0032] Specifically, the step that the second user equipment
initiates the connection establishment process with the
network-side device and sends the first user equipment information
to the network-side device in the connection establishment process,
so that the connection is established between the network-side
device and the first user equipment may be that: the second user
equipment sends a radio resource control connection establishment
request message to a serving base station of a current cell of the
second user equipment; and after receiving a radio resource control
connection establishment response message sent by the
above-mentioned serving base station, the second user equipment
sends a radio resource control connection establishment complete
message to the above-mentioned serving base station, wherein the
above-mentioned radio resource control connection establishment
complete message carries non-access stratum signaling of the second
user equipment, such as service request signaling.
[0033] A value of an establishment cause information element of the
above-mentioned radio resource control connection establishment
request message is a D2D connection; and/or, the above-mentioned
radio resource control connection establishment complete message
carries D2D capability information of the second user equipment,
wherein the D2D capability information of the second user equipment
is used for indicating that the second user equipment supports the
D2D function; one or both of the above-mentioned radio resource
control connection establishment request message and the
above-mentioned radio resource control connection establishment
complete message carry a non-access stratum identifier and an
access stratum identifier of the first user equipment; and one or
both of the above-mentioned radio resource control connection
establishment request message and the above-mentioned radio
resource control connection establishment complete message carry
the service code of the first user equipment.
[0034] Further, the above-mentioned serving base station packages
the above-mentioned non-access stratum signaling into an initial
user equipment message and sends the initial user equipment message
to a mobility management entity, wherein a value of an
establishment cause information element of the initial user
equipment message is a D2D connection, and the initial user
equipment message carries the non-access stratum identifier of the
first user equipment; and/or when the first user equipment is in a
connected state, the above-mentioned initial user equipment message
also carries the access stratum identifier of the first user
equipment. Then, the serving base station receives an initial
context setup request message sent by the mobility management
entity, wherein the initial context setup request message is sent
to the above-mentioned serving base station by the mobility
management entity after the second user equipment passes
authentication, and the initial context setup request message
carries a D2D connection indicator. Next, the serving base station
executes mapping of the second user equipment from a DPS bearer to
a radio bearer, and the above-mentioned serving base station sends
an initial context setup response message to the mobility
management entity after the mapping from the DPS bearer to the
radio bearer is completed, wherein the initial context setup
response message carries an address of the above-mentioned serving
base station, an accepted evolved packet system bearer list, a
rejected evolved packet system bearer list and a tunnel endpoint
identifier of an S1 port; wherein a D2D connection type indicator
is added to an evolved universal terrestrial ratio access bearer
identity in the above-mentioned accepted evolved packet system
bearer list, or a dedicated packet data network connection for
management of the DPS bearer is stipulated in an attach
process.
[0035] In this embodiment, that the connection is established
between the network-side device and the first user equipment may be
as follows: the serving base station receives a first message sent
by the mobility management entity, wherein the first message may be
a paging message or a new message, and the first message carries a
D2D connection type indicator, an identifier of the first user
equipment and an identifier of the second user equipment; then, the
serving base station sends a second message to the first user
equipment, wherein the second message includes a paging message or
a new message, and wherein the second message carries the D2D
connection type indicator and the identifier of the second user
equipment, so that the connection is established between the first
user equipment and the above-mentioned network-side device.
[0036] In this embodiment, IP address allocation and
quality-of-service management of the DPS bearer are completed by an
entity with an internal gateway function. The above-mentioned
entity with the internal gateway function is an independent entity
or is integrated together with the above-mentioned serving base
station.
[0037] Each dedicated DPS bearer corresponds to one traffic flow
template. The second user equipment filters a traffic flow in a
sending direction of the second user equipment to a DPS bearer
corresponding to a TX traffic flow template of the second user
equipment by using the TX traffic flow template of the second user
equipment. The second user equipment acquires and saves a TX
traffic flow template of the first user equipment, uses the TX
traffic flow template of the first user equipment as a RX traffic
flow template of the second user equipment, and determines a
mapping relation between a traffic flow received by the
above-mentioned second user equipment and a DPS bearer
corresponding to the RX traffic flow template of the second user
equipment according to the RX traffic flow template of the second
user equipment. Specifically, that the second user equipment
acquires the TX traffic flow template of the first user equipment
may be as follows: the second user equipment acquires the TX
traffic flow template of the first user equipment informed by the
first user equipment in the above-mentioned DPS bearer
establishment process; or, the second user equipment acquires the
TX traffic flow template of the first user equipment informed by
the first user equipment through a network.
[0038] Similarly, the first user equipment also filters a traffic
flow in a sending direction of the first user equipment to a DPS
bearer corresponding to a TX traffic flow template of the first
user equipment by using the TX traffic flow template of the first
user equipment. The first user equipment acquires and saves a TX
traffic flow template of the second user equipment, uses the TX
traffic flow template of the second user equipment as a RX traffic
flow template of the first user equipment, and determines a mapping
relation between a traffic flow received by the above-mentioned
first user equipment and a DPS bearer corresponding to the RX
traffic flow template of the first user equipment according to the
RX traffic flow template of the first user equipment. Specifically,
that the first user equipment acquires the TX traffic flow template
of the second user equipment may be as follows: the first user
equipment acquires the TX traffic flow template of the second user
equipment informed by the second user equipment in the
above-mentioned DPS bearer establishment process; or, the first
user equipment acquires the TX traffic flow template of the second
user equipment informed by the second user equipment through a
network.
[0039] Further, in this embodiment, after the second user equipment
determines, according to the first user equipment information, that
the connection with the first user equipment is established, if no
DPS bearer is established between the second user equipment and the
above-mentioned serving base station in the attach process, the
second user equipment initiates a request bearer resource
modification flow to trigger establishment of a DPS bearer.
Specifically, that the second user equipment initiates the request
bearer resource modification flow to trigger the establishment of
the DPS bearer may be as follows: the second user equipment sends a
bearer resource modification request message to the mobility
management entity, so that the above-mentioned mobility management
entity sends the above-mentioned bearer resource modification
request message to a gateway; wherein the bearer resource
modification request message sent by the above-mentioned second
user equipment carries an evolved packet system bearer identity and
a linked bearer identity related with the DPS bearer, and wherein a
D2D connection type indicator is added to the bearer resource
modification request message sent by the second user equipment, or
the bearer resource modification request message sent by the second
user equipment has a dedicated packet data network connection for
management of the DPS bearer.
[0040] Next, a packet data gateway receives a bearer resource
modification request message sent after the above-mentioned gateway
receives the bearer resource modification request message sent by
the second user equipment, wherein the bearer resource modification
request message sent by the above-mentioned gateway carries a
linked bearer identity and an evolved packet system bearer identity
related with the DPS bearer, and wherein a D2D connection type
indicator is added to the bearer resource modification request
message sent by the above-mentioned gateway, or the bearer resource
modification request message sent by the above-mentioned gateway
has a dedicated packet data network connection for management of
the DPS bearer. After the bearer resource modification request
message sent by the above-mentioned gateway is received, the packet
data gateway initiates an establishment process for the DPS bearer
of the second user equipment.
[0041] Further, after the packet data gateway initiates the
establishment process for the DPS bearer of the second user
equipment, the above-mentioned serving base station executes
mapping of the second user equipment from the DPS bearer to a radio
bearer; and after the packet data gateway initiates an
establishment process for the DPS bearer of the first user
equipment, the serving base station executes mapping of the first
user equipment from the DPS bearer to a radio bearer.
[0042] Specifically, the establishment process for the DPS bearer
initiated by the packet data gateway may be as follows: a serving
gateway receives a create dedicated bearer request message sent by
the above-mentioned packet data gateway, wherein the create
dedicated bearer request message sent by the above-mentioned packet
data gateway is sent to the above-mentioned serving gateway after
the packet data gateway allocates quality of service of the evolved
packet system bearer by using a local quality-of-service strategy;
the above-mentioned serving gateway sends the create dedicated
bearer request message to the mobility management entity, so that
the above-mentioned mobility management entity constructs a session
management request and sends a bearer establishment request message
carrying the above-mentioned session management request to the
above-mentioned serving gateway; wherein the create dedicated
bearer request message sent by the above-mentioned serving gateway
carries a linked bearer identity, and the above-mentioned session
management request includes an evolved packet system bearer
identity and a linked bearer identity. In this embodiment, a D2D
connection type indicator is added to the above-mentioned linked
bearer identity, or the above-mentioned linked bearer identity has
a dedicated packet data network connection for management of the
DPS bearer.
[0043] Further, in this embodiment, after the connection is
established between the network-side device and the first user
equipment, the second user equipment may also receive a D2D link
establishment request message sent by the first user equipment,
wherein the above-mentioned D2D link establishment request message
carries an identifier of the first user equipment, an identifier of
the second user equipment and channel state information and
resource allocation condition of the first user equipment. After
the above-mentioned D2D link establishment request message is
received, if connection establishment is permitted, the second user
equipment sends a D2D link establishment response message to the
first user equipment, wherein the above-mentioned D2D link
establishment response message carries the identifier of the second
user equipment, the identifier of the first user equipment, channel
state information of the second user equipment and an accepting or
rejecting response of the second user equipment to the resource
allocation condition of the first user equipment. And finally, the
second user equipment receives a D2D link establishment complete
message sent by the first user equipment.
[0044] In this embodiment, a protocol stack of an air interface
between the first user equipment and the second user equipment
includes a user plane protocol stack.
[0045] In an implementation of this embodiment, the above-mentioned
user plane protocol stack may be a simplified protocol stack, and
the user plane protocol stack is configured with information of one
or a combination of Internet protocol (Internet protocol, IP for
short below), media access control-d (Media Access Control-d, MAC-d
for short below) and a physical (Physical, PHY for short below)
layer.
[0046] In another implementation of this embodiment, the
above-mentioned user plane protocol stack may be configured with
information of one or a combination of IP, packet data convergence
protocol (Packet Data Convergence protocol, PDCP for short below),
a radio link control (Radio Link Control, RLC for short below)
layer, a media access control (Media Access Control, MAC for short
below) layer and a physical (PHY for short below) layer.
[0047] In this embodiment, establishment of the DPS bearer between
the second user equipment and the first user equipment and mapping
from the DPS bearer to the radio bearer are controlled by the
network-side device.
[0048] In the above-mentioned embodiment, after the second user
equipment determines that the connection with the first user
equipment is established according to the information broadcasted
by the first user equipment, the second user equipment initiates
the connection establishment process with the network-side device,
and sends the first user equipment information to the network-side
device in the connection establishment process, so that the
connection is established between the network-side device and the
first user equipment. Therefore, the DPS bearer may be established
between the user equipments supporting the D2D function,
communication between the user equipments supporting the D2D
function is realized, and thus resource controllability of a
network may further be realized.
[0049] It should be noted that, in an embodiment of the present
invention, the DPS bearer is a D2D bearer, and the DPS bearer and
the D2D bearer have the same meaning.
[0050] FIG. 2 is a flowchart of another embodiment of the
connection establishment method of the present invention. As shown
in FIG. 2, the connection establishment method may include:
[0051] Step 201, user equipment 1 (User Equipment 1, UE1 for short
below) supporting a D2D function acquires a resource for
broadcasting information of the UE1, wherein the information of the
UE1 includes one or a combination of an identifier, service
information, a service code and application layer service
information of the UE1.
[0052] The above-mentioned identifier may be one or a combination
of a physical identifier, a non-access stratum identifier
(Non-Access Stratum Identifier, NAS ID for short below) and an
access stratum identifier (Access Stratum Identifier, AS ID for
short below). For example, the physical identifier may be a
specific code sequence such as an international mobile subscriber
identification (International Mobile Subscriber Identification,
IMSI for short below) and the like; the NAS ID may be a serving
temporary mobile subscriber identifier (Serving Temporary Mobile
Subscriber Identifier, s-TMSI for short below) or a global unique
temporary identifier (Global Unique Temporary Identifier, GUTI for
short below), wherein if the UE1 is in an idle state, an old s-TMSI
or old GUTI saved last time may be used, and wherein if the UE1 is
in a connected state, a current s-TMSI or current GUTI may be used;
the AS ID may be a cell radio network temporary identifier (Cell
Radio Network Temporary Identifier, C-RNTI for short below) or a
D-RNTI (i.e., radio network temporary identifier (RNTI for short
below) for D2D).
[0053] The above-mentioned application layer service information
includes user-readable service information, and the user-readable
service information includes service type(s) and/or service
content(s). For example, the service content(s) may be advertising
information, videos of a certain movie, games or the like.
[0054] The above-mentioned service code may be a character, a
character string or a digital sequence, and may represent the
application layer service information; or the above-mentioned
service code may indicate an identifier of the UE1 and one of the
above-mentioned application layer service information and the
above-mentioned service information.
[0055] The above-mentioned service information may be information
of a non-access stratum (Non-Access Stratum, NAS for short below)
required for constructing the connection establishment request
message of a service by the user equipment, and may include quality
of service (QoS for short below) information and the like.
[0056] Specifically, when the UE1 supporting the D2D function is
started in a cell or is reselected to a new cell, the UE1 needs to
acquire the resource for broadcasting the information of the
UE1.
[0057] In an implementation of this embodiment, that the UE1
supporting the D2D function acquires the resource for broadcasting
the information of the UE1 may be as follows: the UE1 acquires
resource(s) which is previously allocated for user equipment(s)
supporting the D2D function in the cell by a serving base station
of the current cell of the above-mentioned UE1 and is used for
broadcasting the above-mentioned information of the user
equipment(s), wherein this resource is broadcasted by the serving
base station through a broadcast message; and then, the UE1 selects
a resource, the interference level of which is lower than a
predefined threshold, from the resource(s) previously allocated by
the above-mentioned serving base station through automatic search
or measurement. Alternatively, the allocation mode of the serving
base station is semi-static.
[0058] In another implementation of this embodiment, that the UE1
supporting the D2D function acquires the resource for broadcasting
the information of the UE1 may be as follows: the UE1 selects a
sub-resource, the interference level of which is lower than a
predefined threshold, from sub-resource(s) broadcasted by the
serving base station according to the interference level(s) of the
sub-resource(s) broadcasted by the serving base station of the
current cell of the above-mentioned UE1 and the position
information of the above-mentioned sub-resource(s); wherein the
above-mentioned sub-resource(s) is(are) acquired in a mode that the
serving base station divides a resource which is previously
allocated for the user equipment(s) supporting the D2D function in
the above-mentioned cell by the serving base station and is used
for broadcasting the above-mentioned information of the user
equipment(s).
[0059] In a further implementation of this embodiment, that the UE1
supporting the D2D function acquires the resource for broadcasting
the information of the UE1 may be as follows: the UE1 establishes a
connection with the serving base station of the current cell of the
above-mentioned UE1 to trigger the serving base station to allocate
the resource for broadcasting the information of the UE1 for the
UE1, no matter whether a real service of the UE1 exists. After the
UE1 establishes the connection with the serving base station of the
UE1, the UE1 may maintain a long discontinuous receive mode (long
Discontinuous Receive mode, long DRX mode for short below) in a
connected state or a common connected state. When the UE1 exits the
current cell, the UE1 notifies the above-mentioned serving base
station of withdrawing the resource allocated for the UE1 and used
for broadcasting the information of the UE1.
[0060] Specifically, in this implementation, that the UE1
establishes the connection with the serving base station of the
current cell of the above-mentioned UE1 may be as follows: the UE1
sends an Attach Request message to the above-mentioned serving base
station, wherein the Attach Request message carries an IMSI or an
old GUTI of the UE1, a last visited tracking area identifier (last
visited tracking area identifier, last visited TAI for short below)
of the UE1 (if any), a core network capability of the UE1, a packet
data network type (Packet Data Network type, PDN type for short
below), protocol configuration options, a ciphered options transfer
flag, an attach type, a KSIASME (for identifying a root key,
KASME), a non-access stratum sequence number (Non-Access Stratum
sequence number, NAS sequence number for short below), a non-access
stratum media access control (Non-Access Stratum Media Access
Control, NAS-MAC for short below) address, an additional GUTI, a
packet temporary mobile subscriber identifier signature (Packet
Temporary Mobile Subscriber Identifier signature, P-TMSI signature
for short below) message and a radio resource control (Radio
Resource Control, RRC for short below) parameter and specific DRX
parameters of the UE1, and is added with a "D2D connection" type
parameter.
[0061] Then the above-mentioned serving base station packages the
Attach Request message sent by the above-mentioned UE1 to generate
an initial UE message, and sends the initial UE message to a
mobility management entity (Mobility Management Entity, MME for
short below); next, the MME packages an attach accept message to be
sent to the UE1 into an S1 MME control message such as an initial
context setup request message, and sends the initial context setup
request message to the above-mentioned serving base station; and
finally, the above-mentioned serving base station sends the initial
context setup request message to the UE1, and the UE1 analyzes the
initial context setup request message to acquire the
above-mentioned Attach Accept message.
[0062] The above-mentioned Attach Accept message carries
information such as an access point name (Access Point Name, APN
for short below), a GUTI, a PDN Type, a packet data network address
(Packet Data Network Address, PDN Address for short below), a TAI
list, an evolved packet system bearer identity (Evolved Packet
System Bearer Identity, EPS Bearer Identity for short below), a
session management request, Protocol Configuration Options, a
KSIASME, a NAS sequence number, NAS-MAC and the like. The
above-mentioned Attach Accept message may also carry related
information of a bearer for D2D connection in a profile of the UE1,
and D2D bearer type information is added behind the EPS Bearer
Identity, or a specific PDN is bound with the D2D connection.
Further, the Attach Accept message may also include access stratum
security context (Access Stratum security context, AS security
context for short below) information, a handover restriction list,
evolved packet system bearer quality of service (Evolved Packet
System Bearer Quality of Service, EPS Bearer QoS for short below),
an EPS Bearer Identity (alternatively, the EPS bearer includes a
bearer for D2D connection), a tunnel endpoint identifier (Tunnel
Endpoint Identifier, TEID for short below) for a serving gateway of
a user plane and an address of the serving gateway, and aggregate
maximum bit rate (Aggregate Maximum Bit Rate, AMBR for short below)
of the UE1.
[0063] Further, after the Attach Accept message is received, the
UE1 sets the "GUTI" into a temp identity used in next update (Temp
Identity used in Next Update, TIN for short below).
[0064] Alternatively, the above-mentioned added "D2D connection"
type parameter may also be put in an S1 application protocol (S1
Application Protocol, S1-AP for short below) message, such as an
Initial Context Setup Request message, for transmitting an NAS
Attach Accept message, and at the same time, indication information
"supporting the D2D function" may be added to a UE radio capability
information element of the Initial Context Setup Request
message.
[0065] A format of the above-mentioned Attach Request message may
be as shown in table 1, a format of the above-mentioned Initial UE
Message may be as shown in table 2, a format of the above-mentioned
Initial Context Setup Request message may be as shown in table 3,
and a format of the above-mentioned Attach Accept message may be as
shown in table 4.
TABLE-US-00001 TABLE 1 IEI Information Element Type/Reference
Presence Format Length Protocol discriminator Protocol
discriminator M V 1/2 9.2 Security header type Security header type
M V 1/2 9.3.1 Attach request message Message type M V 1 identity
9.8 EPS attach type EPS attach type M V 1/2 9.9.3.11 DPS bearer
indication O NAS key set identifier NAS key set identifier M V 1/2
9.9.3.21 EPS mobile identity EPS mobile identity M LV 5-12 9.9.3.12
UE network capability UE network capability M LV 3-14 additional
D2D capability ESM message container ESM message container M LV-E
5-n 9.9.3.15 19 Old P-TMSI signature P-TMSI signature O TV 4
10.5.5.8 50 Additional GUTI EPS mobile identity O TLV 13 9.9.3.12
52 Last visited registered Tracking area identity O TV 6 TAI
9.9.3.32 5C DRX parameter DRX parameter O TV 3 9.9.3.8 31 MS
network capability MS network capability O TLV 4-10 13 Old location
area Location area O TV 6 identification identification 9.9.2.2 9-
TMSI status TMSI status O TV 1 9.9.3.31 11 Mobile station classmark
Mobile station classmark 2 O TLV 5 2 9.9.2.4 20 Mobile station
classmark Mobile station classmark 3 O TLV 2-34 3 9.9.2.5 40
Supported Codecs Supported Codec List O TLV 5-n 9.9.2.10 F-
Additional update type Additional update type O TV 1 9.9.3.0B 5D
Voice domain preference Voice domain preference O TLV 3 and UE's
usage setting and UE's usage setting 9.9.3.44 D- Device properties
Device properties O TV 1 9.9.2.0A E- Old GUTI type GUTI type O TV 1
9.9.3.45
TABLE-US-00002 TABLE 2 Information Element (IE for short IE type
below)/Group and Semantics Assigned Name Presence Range reference
description Criticality Criticality Message Type M 9.2.1.1 YES
ignore eNB UE S1AP M 9.2.3.4 YES reject ID NAS-PDU M 9.2.3.5 ATTACH
YES reject REQUEST message, see below TAI M 9.2.3.16 YES reject
E-UTRAN CGI M 9.2.1.38 YES ignore RRC M 9.2.1.3a YES Ignore
Establishment cause S-TMSI O 9.2.3.6 YES reject GUMMEI O 9.2.3.9
YES reject Cell Access O 9.2.1.74 YES reject Mode GW Transport O
Transport Indicating GW needed in ignore Layer Address Layer
Transport the Address Layer Address embodiment 9.2.2.1 if the GW is
shown in collocated with FIG. 3 of the eNB present invention
TABLE-US-00003 TABLE 3 Information Element (IE for short IE type
below)/Group and Semantics Assigned Name Presence Range reference
description Criticality Criticality Message Type M 9.2.1.1 YES
reject MME UE S1AP M 9.2.3.3 YES reject ID eNB UE S1AP M 9.2.3.4
YES reject ID eNB P-UE O 9.2.3.4 If target YES reject S1AP ID (new)
(paired) UE in connected mode; This is for service request
procedure, not attach accept procedure. UE Aggregate M 9.2.1.20 YES
reject Maximum Bit Rate E-RAB to Be 1 YES reject Setup List
>E-RAB to Be EACH reject Setup Item IEs >>E-RAB ID M
9.2.1.2 -- >> M 9.2.1.3a YES Ignore D2D-connection indication
(new) >>E-RAB Level M 9.2.1.15 -- QoS Parameters
>>Transport M 9.2.2.1 -- Layer Address >>GTP-TEID M
9.2.2.2 -- >>NAS-PDU O 9.2.3.5 ATTACH -- ACCEPT, see below
table >>Correlation O 9.2.2.80 YES ignore ID UE Security M
9.2.1.40 YES reject Capabilities Security Key M 9.2.1.41 YES reject
Trace Activation O 9.2.1.4 YES ignore Handover O 9.2.1.22 YES
ignore Restriction List UE Radio O 9.2.1.27 Alternatively, YES
ignore Capability additional D2D capability Subscriber O 9.2.1.39
YES ignore Profile ID for RAT/Frequency priority CS Fallback O
9.2.3.21 YES reject Indicator SRVCC O 9.2.1.58 YES ignore Operation
Possible CSG O 9.2.1.73 YES ignore Membership Status Registered LAI
O 9.2.3.1 YES ignore GUMMEI O 9.2.3.9 YES ignore MME UE S1AP O
9.2.3.3 YES ignore ID 2
TABLE-US-00004 TABLE 4 IEI Information Element Type/Reference
Presence Format Length Protocol discriminator Protocol
discriminator M V 1/2 9.2 Security header type Security header type
M V 1/2 9.3.1 Attach accept message Message type M V 1 identity 9.8
EPS attach result EPS attach result M V 1/2 9.9.3.10 Spare half
octet Spare half octet M V 1/2 9.9.2.9 T3412 value GPRS timer M V 1
9.9.3.16 TAI list Tracking area identity list M LV 7-97 9.9.3.33
ESM message container ESM message container M LV-E 5-n 9.9.3.15 50
GUTI EPS mobile identity O TLV 13 9.9.3.12 13 Location area
identification Location area identification O TV 6 9.9.2.2 23 MS
identity Mobile identity O TLV 7-10 9.9.2.3 53 EMM cause EMM cause
O TV 2 9.9.3.9 17 T3402 value GPRS timer O TV 2 9.9.3.16 59 T3423
value GPRS timer O TV 2 9.9.3.16 4A Equivalent PLMNs PLMN list O
TLV 5-47 9.9.2.8 34 Emergency number list Emergency number list O
TLV 5-50 9.9.3.37 64 EPS network feature EPS network feature
support O TLV 3 support 9.9.3.12A F- Additional update result
Additional update result O TV 1 9.9.3.0A 5E T3412 extended value
GPRS timer 3 O TLV 3 9.9.3.16B
[0066] Step 202, the UE1 broadcasts the information of the UE1 on
the acquired resource.
[0067] Specifically, the UE supporting the D2D function has the
characteristics of discontinuous receive (Discontinuous Receive,
DRX for short below) and discontinuous transmission (Discontinuous
Transmission, DTX for short below).
[0068] Therefore, in this embodiment, the mode that the UE1
broadcasts the information of the UE1 may be a DTX mode, and the
information of the UE1 is broadcasted on the acquired resource in a
DTX-Cycle.
[0069] Step 203, when UE2 supporting the D2D function knows the
presence of the probably paired UE1 through a perceptive technology
or search and measurement on other UE(s) supporting the D2D
function, the UE2 sends an RRC connection establishment request
message to the above-mentioned serving base station.
[0070] In this embodiment, before the step 203, the UE2 acquires a
resource for broadcasting information of the UE2 likewise and
broadcasts the information of the UE2 on the acquired resource,
wherein the implementation is the same as the modes described in
step 201 and step 202 and will not be repeated redundantly herein.
A description is given in this embodiment, taking the same serving
base station of the current cells of the UE2 and the UE1 as an
example.
[0071] Alternatively, in this embodiment, a value of an
establishment cause information element of the above-mentioned RRC
connection establishment request message is a D2D connection;
further, the above-mentioned RRC connection establishment request
message may also carry an NAS ID (such as old GUTI or s-TMSI) and
an AS ID of the UE1; or, alternatively, the above-mentioned RRC
connection establishment request message may also carry a service
code of the UE1. In this way, the above-mentioned serving base
station may know that a D2D connection establishment process is
initiated by the UE2 and may acquire an identifier of a destination
UE or paired UE. In this embodiment, the above-mentioned
destination UE or paired UE is UE1.
[0072] Specifically, the UE2 may search for information broadcasted
by UE(s) supporting the D2D function except the UE2 on some
specific resources by adopting a DRX mode in a DRX-Cycle, and the
UE2 receives the UE1 information broadcasted by the UE1 after the
presence of the probably paired UE1 is known. Or, the UE2 may also
receive the UE1 information broadcasted by the UE1 in an event
trigger mode; for example, when a user has some specific demands, a
receive action is triggered through a human-machine interface; or a
receive action is triggered by an application layer according to a
demand profile previously customized by the user. Of course, the
UE2 may also receive the UE1 information broadcasted by the UE1 in
combination with the DRX mode and the event trigger mode.
[0073] Then, the UE2 discovers matching of the information of the
UE1 and the demands of the UE2, and then the UE2 initiates
establishment of a direct D2D connection with the UE1. Firstly, the
UE2 sends the RRC connection establishment request message to the
above-mentioned serving base station.
[0074] Step 204, the UE2 receives an RRC connection establishment
response message sent by the above-mentioned serving base
station.
[0075] Step 205, the UE2 sends an RRC connection establishment
complete message to the above-mentioned serving base station.
[0076] In this embodiment, the above-mentioned RRC connection
establishment complete message carries D2D capability information
of the UE2 and service request signaling of the UE2, wherein the
D2D capability information of the above-mentioned UE2 is used for
indicating that the UE2 supports the D2D function. Further, the
above-mentioned RRC connection establishment complete message may
also carry an NAS ID (such as old GUTI or s-TMSI) and an AS ID of
the UE1; or the above-mentioned RRC connection establishment
complete message may also carry a service code of the UE1. In this
way, the above-mentioned serving base station may know that the D2D
connection establishment process is initiated by the UE2 and may
acquire the identifier of the connected object (namely UE1).
[0077] In step 203-step 205, one or both of items that the RRC
connection establishment complete message carries the D2D
capability information of the UE2 and the value of the
establishment cause information element of the RRC connection
establishment request message is the D2D connection may occur. That
is to say, if the value of the establishment cause information
element of the RRC connection establishment request message is the
D2D connection in step 203, the RRC connection establishment
complete message may or may not carry the D2D capability
information of the UE2 in step 205; or, if the value of the
establishment cause information element of the RRC connection
establishment request message is not the D2D connection in step
203, the RRC connection establishment complete message must carry
the D2D capability information of the UE2 in step 205.
[0078] In addition, one or both of the above-mentioned RRC
connection establishment complete message and the above-mentioned
RRC connection establishment request message carry the NAS ID (such
as old GUTI or s-TMSI) and the AS ID of the UE1; or, one or both of
the above-mentioned RRC connection establishment complete message
and the above-mentioned RRC connection establishment request
message carry the service code of the UE1.
[0079] Step 206, the serving base station forwards the
above-mentioned service request signaling to a mobility management
entity (Mobility Management Entity, MME for short below).
[0080] In this embodiment, alternatively, before the serving base
station forwards the service request signaling of a non-access
stratum to the MME, the serving base station may perform accept
judgment control. Further, the above-mentioned serving base station
may transmit measurement configuration of a link from the UE2 to
the UE1 and/or a link from the UE2 to the serving base station to
the UE2, and decides, according to a measurement result reported
after the UE2 performs measurement according to the above-mentioned
measurement configuration, whether a bearer and communication of
D2D type are established.
[0081] In this embodiment, the above-mentioned serving base station
packages the above-mentioned service request signaling into an
Initial UE Message of an S1-AP port. Moreover, a "D2D connection"
type is added to the Initial UE Message, so as to simplify a
following paging process for D2D communication. Further, the
Initial UE Message may include an NAS ID of the UE1, such as
s-TMSI; and if the UE1 is in a connected state, the serving base
station may map the AS ID of the UE1 into an eNB T-UE S1AP ID, and
the eNB T-UE S1AP ID is carried in the Initial UE Message and sent
to core network device, such as the MME.
[0082] A format of the above-mentioned Initial UE Message may be as
shown in table 5.
TABLE-US-00005 TABLE 5 IE type IE/Group and Semantics Assigned Name
Presence Range reference description Criticality Criticality
Message M 9.2.1.1 YES ignore Type eNB UE M 9.2.3.4 YES reject S1AP
ID eNB T-UE O 9.2.3.4 If the destination YES reject S1AP ID
(paired) UE is in a connected state NAS-PDU M 9.2.3.5 YES reject
TAI M 9.2.3.16 YES reject E-UTRAN M 9.2.1.38 YES ignore CGI RRC M
9.2.1.3a Adding "D2D YES Ignore Establishment connection" type
cause S-TMSI O 9.2.3.6 YES reject S-TMSI O 9.2.3.6 If the
destination YES reject (paired) UE is in a connected state or in an
idle state CSG Id O 9.2.1.62 YES reject GUMMEI O 9.2.3.9 YES reject
Cell O 9.2.1.74 YES reject Access Mode GW O 9.2.2.1 YES ignore
Transport Layer Address Relay O 9.2.1.79 Indicating a relay YES
reject Node node Indicator
[0083] Step 207, after receiving the above-mentioned service
request signaling, the MME performs an authentication process.
[0084] If authentication is passed, the MME initiates a context
setup process, so as to trigger a bearer establishment process.
[0085] Specifically, a packet data network gateway (Packet Data
Network Gateway, PGW for short below) may complete mapping from a
DPS bearer to a radio bearer according to the current LTE
technology. For example, the PGW completes bearer management
functions such as allocation of the Internet protocol (Internet
protocol, IP for short below) address of the DPS bearer, management
of quality of service (Quality of Service, QoS for short below) and
the like.
[0086] Step 208, the MME sends an initial context setup request
message to the serving base station, to activate a radio bearer and
an S1 bearer of all EPS bearers.
[0087] The above-mentioned initial context setup request message
includes a serving gateway address, an uplink S1-TEID (S1-TEID(s)),
EPS Bearer QoS(s), Security Context, an MME Signaling Connection ID
and a Handover Restriction List. Moreover, a D2D connection
indication information element is added to the above-mentioned
Initial Context Setup Request message in this embodiment.
[0088] After the above-mentioned Initial Context Setup Request
message is received, the above-mentioned serving base station saves
the Security Context, the MME Signaling Connection Id, the EPS
Bearer QoS(s) and S1-TEID(s) in a Radio Access Network context
(Radio Access Network context, RAN context for short below) of the
serving base station.
[0089] A format of the above-mentioned Initial Context Setup
Request message may be as shown in table 6.
TABLE-US-00006 TABLE 6 IE type and Semantics Assigned IE/Group Name
Presence Range reference description Criticality Criticality
Message Type M 9.2.1.1 YES reject MME UE S1AP M 9.2.3.3 YES reject
ID eNB UE S1AP M 9.2.3.4 YES reject ID eNB T-UE S1AP O 9.2.3.4 If
the YES reject ID destination (paired) UE is in a connected state;
probably the IE is not necessary in the message UE Aggregate M
9.2.1.20 YES reject Maximum Bit Rate E-RAB to Be 1 YES reject Setup
List >E-RAB to Be EACH reject Setup Item IEs >>E-RAB ID M
9.2.1.2 -- >> O 9.2.1.3a YES Ignore D2D-connection
findication >>E-RAB M 9.2.1.15 -- Level QoS Parameters
>>Transport M 9.2.2.1 -- Layer Address >>GTP-TEID M
9.2.2.2 -- >>NAS-PDU O 9.2.3.5 -- >>Correlation O
9.2.2.80 YES ignore ID UE Security M 9.2.1.40 YES reject
Capabilities Security Key M 9.2.1.41 YES reject Trace Activation O
9.2.1.4 YES ignore Handover O 9.2.1.22 YES ignore Restriction List
UE Radio O 9.2.1.27 YES ignore Capability Subscriber O 9.2.1.39 YES
ignore Profile ID for RAT/Frequency priority CS Fallback O 9.2.3.21
YES reject Indicator SRVCC O 9.2.1.58 YES ignore Operation Possible
CSG O 9.2.1.73 YES ignore Membership Status Registered LAI O
9.2.3.1 YES ignore GUMMEI O 9.2.3.9 YES ignore MME UE S1AP O
9.2.3.3 YES ignore ID 2
[0090] Step 209, the serving base station executes mapping from a
DPS bearer to a radio bearer.
[0091] One radio bearer is used for transmitting a data packet of
one DPS bearer between two UEs. If one radio bearer exists, a
one-to-one mapping relation exists between one DPS bearer and one
radio bearer. Between two UEs, one DPS bearer uniquely identifies a
traffic flow group with common QoS characteristics. A packet filter
rule is associated with a unique packet filter identifier in each
connection and is transmitted in signaling of a similar NAS
process. One DPS bearer is a set of all packet filter rules in this
bearer.
[0092] The traffic flow groups with a same QoS characteristics are
mapped to a same DPS bearer. For example, the above-mentioned QoS
characteristics may include a scheduling strategy, a queuing
management strategy, a speed reshaping strategy, radio link control
(Radio Link Control, RLC for short below) management and the
like.
[0093] Step 210, the serving base station sends an initial context
setup complete/response message to the MME.
[0094] Specifically, after the mapping from the DPS bearer to the
radio bearer is completed, the serving base station sends an RRC
reconfiguration request message to the UE2, and receives an RRC
reconfiguration complete message sent by the UE2. After the serving
base station receives the RRC reconfiguration complete message sent
by the UE2, the mapping from the DPS bearer to the radio bearer is
completed. Then, the serving base station sends a reply message to
the MME, such as the initial context setup complete/response
message, wherein the initial context setup complete/response
message carries an address of the serving base station, an accepted
EPS bearer list, a rejected EPS bearer list and TEID(s) (downlink)
of an S1 port. Moreover, a "D2D connection" type indicator is added
to "evolved universal terrestrial radio access network radio access
bearer identity (Evolved Universal Terrestrial Radio Access Network
Radio Access Bearer Identifier, E-RAB ID for short below)"
information in the "accepted EPS bearer list", or a dedicated PDN
connection for management of the DPS bearer is stipulated in the
Attach process.
[0095] In this embodiment, a format of the initial context setup
complete/response message may be as shown in table 7.
TABLE-US-00007 TABLE 7 Information Element (IE for short IE type
below)/Group and Semantics Assigned Name Presence Range reference
description Criticality Criticality Message Type M 9.2.1.1 YES
reject MME UE M 9.2.3.3 YES ignore S1AP ID eNB UE S1AP M 9.2.3.4
YES ignore ID E-RAB Setup 1 YES ignore List > E-RAB 1 to EACH
ignore Setup Item Ies <maxnoofE- RABs> >>E-RAB ID M
9.2.1.2 1: in the -- attach process, it has been bound with a D2D
bearer; 2: attach a D2D communication type >> O alternatively
D2D-connection indication (new) >>Transport M 9.2.2.1 --
Layer Address >>GTP-TEID M 9.2.2.2 -- E-RAB Failed O E-RAB a
value for YES ignore to Setup List List E-RAB ID 9.2.1.36 shall
only be present once in E-RAB Setup List IE + E-RAB Failed to Setup
List IE Criticality O 9.2.1.21 YES ignore Diagnostics
[0096] Step 211, the MME sends an update bearer request message to
a gateway (Gateway, GW for short below).
[0097] Step 212, the MME receives an update bearer response message
sent by the GW.
[0098] Step 213, the MME sends a first message to the
above-mentioned serving base station.
[0099] In this embodiment, the above-mentioned first message is
used for triggering the serving base station to send a message to
the UE1, so that a connection is established between the UE1 and
the network-side device. The above-mentioned first message may be a
paging message or a new message, and the above-mentioned first
message carries a "D2D connection" type, an identity of a UE (UE2
in this embodiment) for triggering current D2D communication and an
identity of a UE (UE1 in this embodiment) needing connection
establishment.
[0100] In this embodiment, after the MME receives the reply message
of the above-mentioned serving base station, such as the initial
context setup complete/response message, the MME sends the first
message to the above-mentioned serving base station to trigger the
serving base station to send a second message to the UE1, so that
the connection is established between the UE1 and the network-side
device.
[0101] Taking the above-mentioned first message which is the paging
message as an example, a "D2D connection" type and an identifier of
the UE for triggering the current D2D communication are added to
the existing paging message sent from the MME to the serving base
station in this embodiment. In this embodiment, the UE for
triggering the current D2D communication is the UE2, and the
identifier of the UE for triggering the current D2D communication
herein is the one capable of being identified by the
above-mentioned serving base station.
[0102] In this embodiment, a format of the paging message sent from
the MME to the serving base station may be as shown in table 8.
TABLE-US-00008 TABLE 8 Information Element (IE for short IE type
below)/Group and Semantics Assigned Name Presence Range reference
description Criticality Criticality Message Type M 9.2.1.1 YES
ignore UE Identity M 9.2.3.10 YES ignore Index value UE Paging M
9.2.3.13 YES ignore Identity T-UE Paging O 9.2.3.13 Identity D2D
Communication indication Paging DRX O 9.2.1.16 YES ignore CN Domain
M 9.2.3.22 YES ignore List of TAIs 1 YES ignore >TAI List 1 to
<maxnoofTAIs> EACH ignore Item >>TAI M 9.2.3.16 -- CSG
Id List 0 . . . 1 GLOBAL ignore >CSG Id 1 to
<maxnoofCSGId> 9.2.1.62 -- Paging O 9.2.1.78 YES ignore
Priority
[0103] Step 214, the above-mentioned serving base station sends a
second message to the UE1.
[0104] In this embodiment, the above-mentioned second message is
used for triggering the UE1 to establish a connection with the
network-side device. The above-mentioned second message may be a
paging message or in a newly designed message format, and may carry
a "D2D connection" type and an identity of a UE (UE2 in this
embodiment) for triggering current D2D communication.
[0105] Taking the above-mentioned second message which is the
paging message as an example, the "D2D connection" type indicator
and the identifier of the UE for triggering the current D2D
communication are added to the existing paging message sent from
the serving base station to the UE in this embodiment. In this
embodiment, the UE for triggering the current D2D communication is
UE2, and the identifier of the UE for triggering the current D2D
communication herein is the one capable of being identified by the
above-mentioned serving base station. The above-mentioned "D2D
connection" type indicator may be an explicit indicator or an
implicit indicator according to an additional information
element.
[0106] Step 215, the UE1 initiates a connection establishment
process with the network-side device.
[0107] After the UE1 receives the second message sent by the
above-mentioned serving base station, the UE1 initiates a
connection establishment process with the network-side device. In
this process, the process of establishing the DPS bearer of the UE1
by a network is similar to the process of establishing the DPS
bearer of the UE2 by the network, and this process is described as
step 207 to step 210 and will not be repeated redundantly herein.
Alternatively, the UE1 performs accept control of this connection
establishment process first.
[0108] Alternatively, a default bearer is established between the
UE1 and the serving base station.
[0109] Alternatively, the serving base station may also directly
send scheduling information to the UE1; and then, the scheduling
information of the UE1 is updated according to feedback of the UE1
about measurement of a link of D2D connection.
[0110] Alternatively, the serving base station may pre-configure a
resource of the UE1 from a longer time perspective, such as a
semi-static resource used for sending/receiving of UE1.
Specifically, the serving base station configures offset of the
semi-static resource, cycle of the semi-static resource, the number
of hybrid automatic repeat request (Hybrid Automatic Repeat
Request, HARQ for short below) processes of semi-static scheduling
and a resource for sending acknowledgement (Acknowledgement, ACK
for short below)/negative-acknowledgement (Negative-Acknowledgment,
NACK for short below).
[0111] Step 216, the UE1 initiates connection establishment with
the UE2. Alternatively, after the UE1 completes connection
establishment with the serving base station, the UE1 initiates the
connection establishment with the UE2.
[0112] Specifically, the UE1 sends a D2D link establishment request
message to the UE2 first. The D2D link establishment request
message carries: an identifier (D-RNTI or physical identifier of
the UE1) of the UE1 and an identifier (D-RNTI or physical
identifier of the UE2) of the UE2; channel state information
(Channel State Information, CSI for short below) of the UE1, such
as a modulation and coding scheme (Modulation and Coding Scheme,
MCS for short below), a code rate and/or precoding matrix indexes
(Precoding Matrix Indexes, PMI for short below) and the like; and
configuration information of resource allocation condition (if the
serving base station does not transmit similar time division
duplexing (Time Division Duplexing, TDD for short below))
proportion.
[0113] Further, after the UE2 receives the above-mentioned D2D link
establishment request message, access control is alternatively
performed. If connection establishment is permitted, the UE2
replies a D2D link establishment response message to the UE1. The
D2D link establishment response message carries the identifier
(D-RNTI or physical identifier of the UE2) of the UE2, the
identifier (D-RNTI or physical identifier of the UE1) of the UE1,
the CSI of the UE2 such as the MCS, the code rate, and/or PMIs and
the like, and resource allocation accept or reject. The resource
allocation accept or reject indicates that the UE2 accepts or
rejects a resource allocation condition of the UE1, and
alternatively carries a cause value or a recommended resource
allocation mode.
[0114] Finally, after the UE1 receives the D2D link establishment
response message sent by the UE2, the UE1 sends a D2D link
establishment complete message to the UE2.
[0115] Step 217, establishment of the DPS bearer between the UE1
and the UE2 is completed. The UE1 and the UE2 start D2D
communication.
[0116] In this embodiment, if the serving base station does not
send dynamic scheduling information, the UE1 and the UE2 may
perform scheduling consultation or automatic scheduling according
to the condition of measurement of a link of D2D connection
themselves, and update scheduling information of the opposite UE
according to the measurement result later.
[0117] In the above-mentioned embodiment, the above-mentioned
serving base station may be an evolved NodeB (evolved NodeB, eNB
for short below). Of course, the embodiments of the present
invention are not limited to this, and the embodiments of the
present invention do not limit the form of the base station.
[0118] The above-mentioned embodiment may realize establishment of
the DPS bearer between the user equipments supporting the D2D
function, realize communication between the user equipments
supporting the D2D function and further realize resource
controllability of the network.
[0119] FIG. 3 is a flowchart of a further embodiment of the
connection establishment method of the present invention. As shown
in FIG. 3, the connection establishment method may include:
[0120] Step 301 to step 306, which are the same as step 201 to step
206.
[0121] Step 307, after the MME receives the above-mentioned service
request signaling, the MME performs an authentication process.
[0122] If authentication is passed, the MME initiates a context
setup process, so as to trigger a bearer establishment process.
[0123] Step 308, the MME sends a context setup request message to
the serving base station, to trigger a bearer establishment process
and a mapping process from a DPS bearer to a radio bearer.
[0124] In this embodiment, bearer management functions such as
allocation of IP address, management of QoS of the DPS and the like
may be completed by an entity with an internal gateway function.
The above-mentioned entity with the internal gateway function may
be an independent entity or be integrated together with the
above-mentioned serving base station.
[0125] In this implementation, one DPS bearer has the following
characteristic:
[0126] Each dedicated DPS bearer is associated with one TFT.
[0127] A TX traffic flow template (TX Traffic Flow Template, TX TFT
for short below) is a set of sent packet filter rules in one TFT.
The UE2 filters a traffic flow in a sending direction to a
corresponding DPS bearer by using the TX TFT, and the UE1 filters a
traffic flow in a sending direction to a corresponding DPS bearer
by using the TX TFT likewise. Meanwhile, the two UEs save the TX
TFT of the opposite party as an RX traffic flow template (RX
Traffic Flow Template, RX TFT for short below), and determine a
mapping relation between a received traffic flow and a
corresponding DPS bearer according to the RX TFT. The RX TFT is
acquired in a mode that the UE1 and the UE2 which support the D2D
function inform each other or inform the opposite party through a
network in the connection establishment process. In this way, the
UE1 and the UE2 may determine association between Bearer(s) and
Application(s) by using the TX TFT and RX TFT: determine which
Application the data from the Bearer belong to according to the
TFT, namely receive (RX); and determine which Bearer the data from
the Application are mapped to according to the TFT, namely
transmission (TX).
[0128] One radio bearer is used for transmitting a data packet of
one DPS bearer between two UEs. If one radio bearer exists, a
one-to-one mapping relation exists between one DPS bearer and one
radio bearer. Between two UEs, one DPS bearer uniquely identifies a
traffic flow group with common QoS characteristics. A packet filter
rule is associated with a unique packet filter identifier in each
connection and is transmitted in signaling of a similar NAS
process. One DPS bearer is a set of all packet filter rules in this
bearer.
[0129] The traffic flow groups with a same QoS characteristics are
mapped to a same DPS bearer. For example, the above-mentioned QoS
characteristics may include a scheduling strategy, a queuing
management strategy, a speed reshaping strategy, RLC management and
the like.
[0130] In this embodiment, diagrams of mapping from radio bearers
to DPS bearers may be as shown in FIG. 4a to FIG. 4c, and FIG. 4a
to FIG. 4c are schematic diagrams of an embodiment of bearer
mapping of the present invention.
[0131] Step 309, the serving base station sends an initial context
setup complete/response message to the MME.
[0132] Specifically, after mapping from the DPS bearer to the radio
bearer is completed, the serving base station sends an RRC
reconfiguration request message to the UE2, and receives an RRC
reconfiguration complete message sent by the UE2. After the serving
base station receives the RRC reconfiguration complete message sent
by the UE2, the mapping from the DPS bearer to the radio bearer is
completed. Then, the serving base station sends a reply message to
the MME, such as the initial context setup complete/response
message, wherein the initial context setup complete/response
message carries an address of the serving base station, an accepted
EPS bearer list, a rejected EPS bearer list and TEID(s) (downlink)
of an S1 port. Moreover, a "D2D connection" type indicator is added
to "E-RAB ID" information in the "accepted EPS bearer list", or a
dedicated PDN connection for management of the DPS bearer is
stipulated in the Attach process.
[0133] In this embodiment, a format of the initial context setup
complete/response message may be as shown in table 7.
[0134] Step 310 to step 314 are the same as step 213 to step
217.
[0135] In this embodiment, if the serving base station does not
send dynamic scheduling information, the UE1 and the UE2 may
perform scheduling consultation or automatic scheduling according
to the condition of measurement of a link of D2D connection
themselves, and update scheduling information of the opposite UE
according to the measurement result later.
[0136] In the above-mentioned embodiment, the above-mentioned
serving base station may be an eNB. Of course, the embodiment of
the present invention is not limited to this, and the embodiment of
the present invention does not limit the form of the base
station.
[0137] The above-mentioned embodiment may realize establishment of
the DPS bearer between the user equipments supporting the D2D
function, realize communication between the user equipments
supporting the D2D function and further realize resource
controllability of the network.
[0138] FIG. 5 is a flowchart of a still further embodiment of the
connection establishment method of the present invention. In this
embodiment, establishment of a DPS bearer still adopts the
principle that management and resource allocation of the DPS bearer
are performed by a PGW in LTE. In this embodiment, the initial
state of UE1 and that of UE2 are idle states.
[0139] As shown in FIG. 5, the connection establishment method may
include:
[0140] Step 501, UE1 supporting a D2D function acquires a resource
for broadcasting information of the UE1, wherein the information of
the UE1 includes one or a combination of an identifier, service
information, a service code and application layer service
information of the UE1.
[0141] Specifically, the mode that the UE1 acquires the resource
for broadcasting the information of the UE1 is the same as the mode
described in step 301 of the embodiment shown in FIG. 3 of the
present invention, and will not be repeated redundantly herein.
[0142] Step 502, the UE1 broadcasts the information of the UE1 on
the acquired resource.
[0143] Specifically, the mode that the UE1 broadcasts the
information of the UE1 is the same as the mode described in step
302 of the embodiment shown in FIG. 3 of the present invention, and
will not be repeated redundantly herein.
[0144] Step 503, when UE2 supporting the D2D function knows the
presence of the probably paired UE1 through a perceptive technology
or search and measurement aiming at other UE(s) supporting the D2D
function, the UE2 sends an RRC connection establishment request
message to a serving base station of a current cell of the UE1.
[0145] In this embodiment, before the step 503, the UE2 acquires a
resource for broadcasting information of the UE2 likewise and
broadcasts the information of the UE2 on the acquired resource,
wherein the implementation is the same as the modes described in
step 501 and step 502 and will not be repeated redundantly herein.
A description is given in this embodiment, taking the same serving
base station of the current cells of the UE2 and the UE1 as an
example.
[0146] In this embodiment, a value of an establishment cause
information element of the above-mentioned RRC connection
establishment request message is a D2D connection. Further, the
above-mentioned RRC connection establishment request message may
also carry an NAS ID (such as old GUTI or s-TMSI) and an AS ID of
the UE1; or, the above-mentioned RRC connection establishment
request message may also carry a service code of the UE1. In this
way, the above-mentioned serving base station may know that a D2D
connection establishment process is initiated by the UE2 and may
acquire the identifier of a destination UE or paired UE. In this
embodiment, the above-mentioned destination UE or paired UE is
UE1.
[0147] Specifically, the UE2 may search for information broadcasted
by UE(s) supporting the D2D function except the UE2 on some
specific resources by adopting a DRX mode in a DRX-Cycle, and the
UE2 receives the UE1 information broadcasted by the UE1 after the
presence of the probably paired UE1 is known. Or, the UE2 may also
receive the UE1 information broadcasted by the UE1 in an event
trigger mode. For example, when a user has some specific demands, a
receive action is triggered through a human-machine interface; or a
receive action is triggered by an application layer according to a
demand profile previously customized by the user. Of course, the
UE2 may also receive the UE1 information broadcasted by the UE1 in
combination with the DRX mode and the event trigger mode.
[0148] Then, the UE2 discovers matching of the information of the
UE1 and the demands of the UE2, and the UE2 initiates establishment
of a direct D2D connection with the UE1. Firstly, the UE2 sends the
RRC connection establishment request message to the above-mentioned
serving base station.
[0149] Step 504, the UE2 receives an RRC connection establishment
response message sent by the above-mentioned serving base
station.
[0150] Step 505, the UE2 sends an RRC connection establishment
complete message to the above-mentioned serving base station.
[0151] In this embodiment, the above-mentioned RRC connection
establishment complete message carries D2D capability information
and service request signaling of the UE2. Further, the
above-mentioned RRC connection establishment request message may
also carry an NAS ID (such as old GUTI or s-TMSI) and an AS ID of
the UE1; or the above-mentioned RRC connection establishment
complete message may also carry a service code of the UE1. In this
way, the above-mentioned serving base station may know that the D2D
connection establishment process is initiated by the UE2 and may
acquire the identifier of the connected object (namely UE1).
[0152] In step 503-step 505, one or both of items that the RRC
connection establishment complete message carries the D2D
capability information of the UE2 and the value of the
establishment cause information element of the RRC connection
establishment request message is the D2D connection may occur. That
is to say, if the value of the establishment cause information
element of the RRC connection establishment request message is the
D2D connection in step 503, the RRC connection establishment
complete message may or may not carry the D2D capability
information of the UE2 in step 505; or, if the value of the
establishment cause information element of the RRC connection
establishment request message is not the D2D connection in step
503, the RRC connection establishment complete message must carry
the D2D capability information of the UE2 in step 505.
[0153] In addition, one or both of the above-mentioned RRC
connection establishment complete message and the above-mentioned
RRC connection establishment request message carry the NAS ID (such
as old GUTI or s-TMSI) and the AS ID of the UE1; or, one or both of
the above-mentioned RRC connection establishment complete message
and the above-mentioned RRC connection establishment request
message carry the service code of the UE1.
[0154] Step 506, the serving base station forwards the
above-mentioned service request signaling to an MME.
[0155] Step 507, after the MME receives the above-mentioned service
request signaling, the MME performs an authentication process.
[0156] If authentication is passed, the MME initiates a context
setup process, so as to trigger a bearer establishment process.
[0157] Step 508, the MME sends an initial context setup request
message to the serving base station, to activate a radio bearer and
an S1 bearer of all EPS bearers.
[0158] Specifically, for the format of the above-mentioned initial
context setup request message, reference may be made to the
description in step 208 of the embodiment shown in FIG. 2 of the
present invention, which will not be repeated redundantly
herein.
[0159] Step 509, the serving base station executes mapping from a
DPS bearer to a radio bearer.
[0160] Specifically, the above-mentioned serving base station
executes a radio bearer establishment process. The security
function of a user plane is established in this step. After bearer
establishment of the user plane is completed, the Service Request
process is completed, and the DPS bearer is synchronized on the UE
and the network side at the same time.
[0161] In this embodiment, configuration and management of the DPS
bearer may be completed by a PGW or an MME in an EPC according to
the existing LTE technology.
[0162] Step 510, the serving base station sends an initial context
setup complete/response message to the MME.
[0163] Specifically, after mapping from the DPS bearer to the radio
bearer is completed, the serving base station sends an RRC
reconfiguration request message to the UE2, and receives an RRC
reconfiguration complete message sent by the UE2. After the serving
base station receives the RRC reconfiguration complete message sent
by the UE2, the mapping from the DPS bearer to the radio bearer is
completed. Then, the serving base station sends a reply message to
the MME, such as the initial context setup complete/response
message, wherein the initial context setup complete/response
message carries the address of the serving base station, an
accepted EPS bearer list, a rejected EPS bearer list and TEID(s)
(downlink) of an S1 port. Moreover, a "D2D connection" type
indicator is added to "E-RAB ID" information in the "accepted EPS
bearer list", or a dedicated PDN connection for management of the
DPS bearer is stipulated in the Attach process.
[0164] A format of the above-mentioned initial context setup
complete/response message may be as shown in table 7, and will not
be repeated redundantly herein.
[0165] Step 511, the MME sends an update bearer request message to
a GW.
[0166] Step 512, the MME receives an update bearer response message
sent by the GW.
[0167] Step 513, the UE2 sends a bearer resource modification
request message to the above-mentioned serving base station.
[0168] In this embodiment, if no DPS bearer is established in an
Attach process, the UE2 may initiate a request bearer resource
modification process to trigger establishment of the DPS
bearer.
[0169] Specifically, the UE2 may send the bearer resource
modification request message to the above-mentioned serving base
station first, wherein the bearer resource modification request
message carries a linked EPS bearer ID (Linked EPS Bear ID, LBI for
short below), a payload type indicator (Payload Type Indicator, PTI
for short below), an EPS bearer identity, QoS, traffic aggregate
description (Traffic Aggregate Description, TAD for short below)
and protocol configuration options, and the bearer resource
modification request message is added with a "D2D connection" type
indicator, or has a dedicated packet data network (PDN for short
below) connection for management of the DPS bearer. The
above-mentioned LBI is related with the D2D bearer, and the EPS
bearer identity may also be used as the identity of the D2D
bearer.
[0170] The above-mentioned TAD is used for indicating that the
bearer resource modification request message adds, modifies or
deletes packet filter rule(s). When a traffic flow is increased,
the TAD includes a group of packet filter rules, but does not have
a packet filter identifier. A UE (such as UE2) will also send QoS
class identifier (QoS Class Identifier, QCI for short below)
information and guaranteed bit rate (Guaranteed Bit Rate, GBR for
short below) of the traffic flow to be increased. After this
process is ended, the TAD is released.
[0171] Only when the UE (such as UE2) requests for a bearer adding
operation, the UE sends the LBI to indicate which PDN connection is
associated with an added bearer resource.
[0172] The EPS Bearer Identity is sent merely in the operations of
modifying and deleting a bearer.
[0173] A format of the bearer resource modification request message
sent by the UE may be as shown in table 9.
TABLE-US-00009 TABLE 9 IEI Information Element Type/Reference
Presence Format Length Protocol Protocol discriminator M V 1/2
discriminator 9.2 EPS bearer identity EPS bearer identity M V 1/2
1: in the attach process, it has been bound with a D2D bearer; 2:
attach a D2D communication type Procedure Procedure transaction
identity M V 1 transaction identity 9.4 Bearer resource Message
type M V 1 modification 9.8 request message identity EPS bearer
identity Linked EPS bearer identity M V 1/2 for packet filter 1:
add a "D2D connection" type indicator, 2: or have a dedicated PDN
connection for management of the DPS bearer. Spare half octet Spare
half octet M V 1/2 9.9.2.9 Traffic flow Traffic flow aggregate M LV
2-256 aggregate description 9.9.4.15 5B Required traffic EPS
quality of service O TLV 3-11 flow QoS 9.9.4.3 58 ESM cause ESM
cause O TV 2 9.9.4.4 27 Protocol Protocol configuration options O
TLV 3-253 configuration 9.9.4.11 options C- Device properties
Device properties O TV 1 9.9.2.0A
[0174] Step 514, the above-mentioned serving base station sends a
bearer resource modification request message to the MME.
[0175] The above-mentioned bearer resource modification request
message carries an IMSI, a LBI, a PTI, an EPS Bearer Identity, QoS,
TAD and Protocol Configuration Options. The MME verifies this
request by using the LBI. For the EPS bearer(s) corresponding to
the LBI, the MME uses the same SGW address. The bearer resource
modification request message is added with a "D2D connection" type
indicator, or has a dedicated PDN connection for management of the
DPS bearer.
[0176] Step 515, the MME sends a bearer resource modification
request message to a selected serving gateway (Serving Gateway, SGW
for short below), wherein the bearer resource modification request
message carries an IMSI, a LBI, a PTI, an EPS Bearer Identity, QoS,
TAD and Protocol Configuration Options. The MME verifies this
request by using the LBI. For the EPS bearer(s) corresponding to
the LBI, the MME uses the same SGW address. The bearer resource
modification request message is added with a "D2D connection" type
indicator, or has a dedicated PDN connection for management of the
DPS bearer.
[0177] Step 516, the SGW sends a bearer resource modification
request message to a PGW, wherein the bearer resource modification
request message carries an IMSI, a LBI, a PTI, an EPS Bearer
Identity, QoS, TAD and Protocol Configuration Options. The SGW
sends the EPS bearer(s) corresponding to the LBI to the same PDN.
The bearer resource modification request message is added with a
"D2D connection" type indicator, or has a dedicated PDN connection
for management of the DPS bearer.
[0178] If the above-mentioned bearer resource modification request
message is accepted, a Dedicated Bearer Activation flow or a
Dedicated Bearer Modification flow for management of the DPS bearer
is initiated. The PTI allocated by the UE2 associates the Dedicated
Bearer Activation flow initiated by the UE2 with the Bearer
Resource Modification flow initiated by the UE2, and the PTI
provides a necessary connection between a new traffic flow
combination and an EPS bearer for the new traffic flow combination.
When one new packet filter rule is added to one TFT, the PGW
allocates a unique new packet filter identifier in this TFT. The
PGW maintains a corresponding relation between the packet filter
identifier(s) in a service data flow (SDF for short below) and the
packet filter identifier(s) in the TFT.
[0179] Step 517 to step 521 are the same as step 213 to step
217.
[0180] In the above-mentioned embodiment, the above-mentioned
serving base station may be an eNB. Of course, the embodiment of
the present invention is not limited to this, and the embodiment of
the present invention does not limit the form of the base
station.
[0181] The above-mentioned embodiment may realize establishment of
the DPS bearer between the user equipments supporting the D2D
function, realize communication between the user equipments
supporting the D2D function and further realize resource
controllability of the network.
[0182] In the embodiment shown in FIG. 5 of the present invention,
the dedicated bearer activation flow in step 515 may be as shown in
FIG. 6, and FIG. 6 is a flowchart of an embodiment of a dedicated
bearer activation flow of the present invention.
[0183] Step 601, a PGW applies a local QoS strategy.
[0184] Step 602, the PGW allocates EPS bearer QoS, such as a QoS
parameter of an EPS bearer, by using the local QoS strategy,
wherein the QoS parameter of the EPS bearer includes an QCI,
address resolution protocol (Address Resolution Protocol, ARP for
short below), GBR and maximum bit rate (Maximum Bit Rate, MBR for
short below); and the PGW sends a create dedicated bearer request
message to an SGW, wherein the create dedicated bearer request
message includes an IMSI, a PTI, EPS Bearer QoS, a TFT, an S5/S8
tunnel endpoint identifier (S5/S8 TEID for short below), a LBI and
protocol configuration options.
[0185] Step 603, the SGW sends a create dedicated bearer request
message to the MME, wherein the create dedicated bearer request
message includes an IMSI, a PTI, EPS Bearer QoS, a TFT, an S1-TEID,
a LBI and protocol configuration options.
[0186] The LBI is added with a "D2D connection" type indicator, or
has a dedicated PDN connection for management of the DPS
bearer.
[0187] Step 604, the MME selects one EPS Bearer ID, and constructs
a session management request, wherein the session management
request includes a PTI, an TFT, an EPS Bearer QoS parameter,
Protocol Configuration Options, an EPS Bearer Identity
(alternatively, added "D2D connection" type indicator) and a LBI;
and the MME sends a bearer setup request message to an eNB, wherein
the bearer setup request message includes an EPS Bearer Identity,
EPS Bearer QoS, Session Management Request and S1-TEID.
[0188] Step 605, the eNB maps the EPS Bearer QoS to QoS of a radio
bearer, and sends an RRC connection reconfiguration message to the
UE, wherein the RRC connection reconfiguration message includes
Radio Bearer QoS, Session Management Request and an EPS Bearer
Identity.
[0189] The UE in this embodiment may be UE2 or UE1.
[0190] After the above-mentioned RRC connection reconfiguration
message is received, the UE NAS saves the EPS Bearer Identity and
an association relation, which is established through the LBI,
between a dedicated bearer and a default bearer. The UE decides
mapping from the traffic flow to the radio bearer by using a TX TFT
(UL TFT).
[0191] Step 606, the UE sends an RRC connection reconfiguration
complete message to the eNB to respond to radio bearer
activation.
[0192] Step 607, the eNB sends a bearer setup response message to
the MME to acknowledge the bearer activation.
[0193] The above-mentioned bearer setup response message carries an
EPS Bearer Identity and an S1-TEID.
[0194] Step 608, a UE NAS layer generates a session management
response, and sends the above-mentioned session management response
to the eNB through a direct transfer message.
[0195] The above-mentioned direct transfer message includes the EPS
Bearer Identity.
[0196] Step 609, the eNB sends an uplink NAS transport message to
the MME.
[0197] The above-mentioned uplink NAS transport message carries the
session management response.
[0198] In this embodiment, a format of the above-mentioned Uplink
NAS Transport message may be as shown in table 10.
TABLE-US-00010 TABLE 10 Information Element (IE for short
below)/Group IE type and Semantics Assigned Name Presence Range
reference description Criticality Criticality Message Type M
9.2.1.1 YES ignore MME UE M 9.2.3.3 YES reject S1AP ID MME T-UE O
9.2.3.3 If YES reject S1AP ID(new) target(paired) UE in connected
mode eNB UE M 9.2.3.4 YES reject S1AP ID eNB T-UE O 9.2.3.4 If YES
reject S1AP ID target(paired) (new) UE in connected mode NAS-PDU M
9.2.3.5 Request YES reject Bearer Resource Modification
D2D-connection O alternative indication (new) E-UTRAN M 9.2.1.38
YES ignore CGI TAI M 9.2.3.16 YES ignore GW Transport O Transport
Indicating YES ignore Layer Address Layer GW Address Transport
9.2.2.1 Layer Address if the GW is collocated with eNB
[0199] Step 610, after the bearer setup response message in step
607 and the session management response in step 609 are received,
the MME sends a create dedicated bearer response message to the SGW
to acknowledge that the bearer activation succeeds.
[0200] The above-mentioned create dedicated bearer response message
carries the EPS Bearer Identity and the S1-TEID.
[0201] Step 611, the SGW sends a create dedicated bearer response
message to the PGW.
[0202] FIG. 7 is a flowchart of a still further embodiment of the
connection establishment method of the present invention. In this
embodiment, establishment of a DPS bearer still adopts the
principle that management and resource allocation of the DPS bearer
are performed by a PGW in LTE. In this embodiment, the initial
states of UE1 and UE2 are Active states.
[0203] Step 701, UE1 supporting a D2D function acquires a resource
for broadcasting information of the UE1, wherein the information of
the UE1 includes one or a combination of an identifier, service
information, a service code and application layer service
information of the UE1.
[0204] Specifically, the mode that the UE1 acquires the resource
for broadcasting the information of the UE1 is the same as the mode
described in step 201 of the embodiment shown in FIG. 2 of the
present invention, and will not be repeated redundantly herein.
[0205] Step 702, the UE1 broadcasts the information of the UE1 on
the acquired resource.
[0206] Specifically, the mode that the UE1 broadcasts the
information of the UE1 is the same as the mode described in step
202 of the embodiment shown in FIG. 2 of the present invention, and
will not be repeated redundantly herein.
[0207] Step 703, UE2 supporting the D2D function knows the presence
of the probably paired UE1 through a perceptive technology or
search and measurement on other UE(s) supporting the D2D
function.
[0208] Alternatively, the UE2 sends an approach indicator to a
serving base station, which carries the information of the UE1.
[0209] In this embodiment, before the step 703, the UE2 acquires a
resource for broadcasting information of the UE2 likewise and
broadcasts the information of the UE2 on the acquired resource, and
the implementation is the same as the modes described in step 701
and step 702 and will not be repeated redundantly herein. A
description is given in this embodiment, taking the same serving
base station of the current cells of the UE2 and the UE1 as an
example.
[0210] Step 704, the UE2 sends a bearer resource modification
request message to the serving base station of the current cell of
the UE1.
[0211] In this embodiment, if no D2D bearer is established in an
Attach process, the UE2 may initiate a request bearer resource
modification process to trigger establishment of the D2D
bearer.
[0212] Specifically, the UE2 may send the bearer resource
modification request message to the above-mentioned serving base
station first, wherein the bearer resource modification request
message carries a LBI, a PTI, an EPS Bearer Identity, QoS, TAD and
protocol configuration options; and the bearer resource
modification request message is added with a "D2D connection" type
indicator, or has a dedicated PDN connection for management of the
DPS bearer. The above-mentioned LBI is related with the D2D bearer,
and the EPS Bearer Identity may also be used as the identity of the
D2D bearer.
[0213] The above-mentioned TAD is used for indicating that the
bearer resource modification request message adds, modifies or
deletes packet filter rule(s). When a traffic flow is increased,
the TAD includes a group of packet filter rules, but does not have
a packet filter identifier. The UE (such as UE2) will also send QCI
information and GBR of the traffic flow to be increased. After this
process is ended, the TAD is released.
[0214] Only when the UE (such as UE2) requests for a bearer adding
operation, the UE sends the LBI to indicate which PDN connection is
associated with the added bearer resource(s).
[0215] The EPS Bearer Identity is sent merely in the operations of
modifying and deleting the bearer.
[0216] A format of the bearer resource modification request message
sent by the UE may be as shown in table 9.
[0217] Step 705, the above-mentioned serving base station sends a
bearer resource modification request message to the MME.
[0218] The above-mentioned bearer resource modification request
message carries an IMSI, a LBI, a PTI, an EPS Bearer Identity, QoS,
TAD and Protocol Configuration Options. The MME verifies this
request by using the LBI. For the EPS bearer(s) corresponding to
the LBI, the MME uses a same SGW address. The bearer resource
modification request message is added with a "D2D connection" type
indicator, or has a dedicated PDN connection for management of the
DPS bearer.
[0219] Step 706, the MME sends a bearer resource modification
request message to a selected SGW, wherein the bearer resource
modification request message carries an IMSI, a LBI, a PTI, an EPS
Bearer Identity, QoS, TAD and Protocol Configuration Options. The
MME verifies this request by using the LBI. For the EPS bearer(s)
corresponding to the LBI, the MME uses a same SGW address. The
bearer resource modification request message is added with a "D2D
connection" type indicator, or has a dedicated PDN connection for
management of the DPS bearer.
[0220] Step 707, the SGW sends a bearer resource modification
request message to a PGW, wherein the bearer resource modification
request message carries an IMSI, a LBI, a PTI, an EPS Bearer
Identity, QoS, TAD and Protocol Configuration Options. The SGW
sends the EPS bearer(s) corresponding to the LBI to a same PDN. The
bearer resource modification request message is added with a "D2D
connection" type indicator, or has a dedicated PDN connection for
management of the DPS bearer.
[0221] If the above-mentioned bearer resource modification request
message is accepted, a Dedicated Bearer Activation flow or a
Dedicated Bearer Modification flow for management of the DPS bearer
is initiated. The PTI allocated by the UE2 associates the Dedicated
Bearer Activation flow initiated by the UE2 with the Bearer
Resource Modification flow initiated by the UE2, and the PTI
provides a necessary connection between a new traffic flow
combination and an EPS bearer for the new traffic flow combination.
When one new packet filter rule is added to one TFT, the PGW
allocates a unique new packet filter identifier in this TFT. The
PGW maintains a corresponding relation between the packet filter
identifier(s) in an SDF and the packet filter identifier(s) in the
TFT.
[0222] The above-mentioned dedicated bearer activation flow may be
as shown in FIG. 6, and will not be repeated redundantly
herein.
[0223] Step 708, the serving base station executes mapping from the
DPS bearer to a radio bearer according to the information of the
DPS bearer.
[0224] Specifically, the above-mentioned serving base station
executes a radio bearer establishment process. The security
function of a user plane is established in this step. After bearer
establishment of the user plane is completed, the Service Request
process is completed, and the DPS bearer is synchronized on the UE
and the network side at the same time.
[0225] In this embodiment, configuration and management of the DPS
bearer may be completed by a PGW or an MME in an EPC according to
the existing LTE technology.
[0226] Step 709, the PGW initiates an establishment process of a
D2D bearer of a destination UE.
[0227] In this embodiment, the above-mentioned destination UE is
UE1.
[0228] Firstly, the PGW initiates a dedicated bearer activation
flow to the UE1 according to the identifier of the UE1 acquired
from the MME. The above-mentioned dedicated bearer activation flow
may be as shown in FIG. 6, and will not be repeated redundantly
herein.
[0229] Then, the above-mentioned serving base station executes
mapping from the DPS bearer to the radio bearer.
[0230] In this embodiment, configuration and management of the DPS
bearer may be completed by the PGW or the MME in the EPC according
to the existing LTE technology.
[0231] Step 710, the UE1 initiates connection establishment with
the UE2.
[0232] This step is an alternative step. Specifically, for the
process that the UE1 initiates the connection establishment with
the UE2, reference may be made to the description in step 216 of
the embodiment shown in FIG. 2 of the present invention, which will
not be repeated redundantly herein.
[0233] Step 711, establishment of the DPS bearer between the UE1
and the UE2 is completed. The UE1 and the UE2 start D2D
communication.
[0234] The above-mentioned embodiment may realize establishment of
the DPS bearer between the user equipments supporting the D2D
function, realize communication between the user equipments
supporting the D2D function and further realize resource
controllability of the network.
[0235] In the embodiments shown in FIG. 2 to FIG. 7, the protocol
stack of an air interface (namely a Ud port) between the UE1 and
the UE2, merely has a user plane protocol stack, and does not have
a control plane protocol stack or a simplified control plane
protocol stack.
[0236] The user plane protocol stack of the above-mentioned Ud port
may still adopt the protocol stack of the current LTE, as shown in
FIG. 10a, and at this moment, the above-mentioned user plane
protocol stack may be configured with information of one or a
combination of IP, PDCP, RLC, MAC and PHY; or the user plane
protocol stack of the above-mentioned Ud port may be the simplified
protocol stack, as shown in FIG. 10b, and at this moment, the
above-mentioned user plane protocol stack may be configured with
information of one or a combination of IP, MAC-d and PHY. FIG. 10a
to FIG. 10b are schematic diagrams of the user plane protocol stack
of the present invention.
[0237] In the embodiments shown in FIG. 2 to FIG. 7 of the present
invention, configuration of a Ud link is controlled by a network
side, namely that the Ud port is configured and controlled through
signaling of the Uu port, including establishment of the DPS bearer
between the UE1 and the UE2 and mapping from the DPS bearer to the
radio bearer.
[0238] Alternatively, if a resource is shared, the user plane
protocol stack of the above-mentioned Ud port may also be
configured with one or a combination of configuration information
of similar TDD proportion(s) (not limited to several proportions
stipulated in the current LTE), security information (encryption,
integrity protection parameter and algorithm) and measurement
configuration information. The measurement configuration
information may include one or a combination of radio resource
management (Radio Link Management, RRM for short below), radio link
management (Radio Link Management, RLM for short below) and CSI.
According to different pieces of reference signaling, configuration
of the above-mentioned measurement configuration information is
different. For example, if an uplink resource is shared, the eNB
may configure the above-mentioned measurement configuration
information by using a sounding reference signal (Sounding
Reference Signal, SRS for short below) or a new reference signal
(New Reference Signal, NRS for short below) as a measurement
object; and if a downlink resource is shared, the eNB may configure
the above-mentioned measurement configuration information by using
cell-specific reference signals (Cell-specific Reference Signals,
CRS for short below) or an NRS as a measurement object.
[0239] According to the user plane protocol stack of the
above-mentioned Ud port, the eNB may send resource scheduling
information, and the resource scheduling information includes one
or a combination of a physical resource of a PHY layer, a
modulation and coding scheme (Modulation and Coding Scheme, MCS for
short below), a code rate and precoding matrix indexes (Precoding
Matrix Indexes, PMI for short below) informed to be used by the UE1
and/or the UE2 and the like.
[0240] It should be appreciated by those of ordinary skill in the
art that all or a part of the steps in the embodiments of the
above-mentioned method may be implemented by a hardware related
with program instructions. The program may be stored in a computer
readable storage medium. When the program is executed, the steps of
the embodiments of the above-mentioned method may be executed. The
storage medium includes various media capable of storing program
codes, such as a read-only memory (ROM), a random access memory
(RAM), a magnetic disk, an optical disk or the like.
[0241] FIG. 8 is a structure schematic diagram of an embodiment of
a user equipment of the present invention. The user equipment in
this embodiment is a second user equipment supporting a D2D
function, and can implement the flow of the embodiment shown in
FIG. 1 of the present invention. As shown in FIG. 8, the user
equipment may include an acquiring module 81, a determining module
82 and an initiating module 83;
[0242] the acquiring module 81 is configured to acquire first user
equipment information broadcasted by a first user equipment
supporting a D2D function;
[0243] the determining module 82 is configured to determine that a
connection with the first user equipment is established according
to the first user equipment information acquired by the acquiring
module 81;
[0244] the initiating module 83 is configured to initiate a
connection establishment process with a network-side device and to
send the first user equipment information to the network-side
device in the connection establishment process, so that a
connection is established between the network-side device and the
first user equipment.
[0245] The above-mentioned user equipment may realize establishment
of a DPS bearer between the user equipments supporting the D2D
function, realize communication between the user equipments
supporting the D2D function and further realize resource
controllability of a network.
[0246] FIG. 9 is a structure schematic diagram of another
embodiment of the user equipment of the present invention. Compared
with the user equipment shown in FIG. 8, what is the difference is,
in the user equipment shown in FIG. 9, the initiating module 83 may
include a sending sub-module 831 and a receiving sub-module
832;
[0247] the sending sub-module 831 is configured to send a radio
resource control connection establishment request message to a
serving base station of a current cell of second user equipment and
send a radio resource control connection establishment complete
message to the above-mentioned serving base station after the
receiving sub-module 832 receives a radio resource control
connection establishment response message sent by the
above-mentioned serving base station, wherein the above-mentioned
radio resource control connection establishment complete message
carries non-access stratum signaling of the second user equipment,
such as service request signaling;
[0248] the receiving sub-module 832 is configured to receive the
radio resource control connection establishment response message
sent by the above-mentioned serving base station;
[0249] wherein, a value of an establishment cause information
element of the above-mentioned radio resource control connection
establishment request message is a D2D connection; and/or, the
above-mentioned radio resource control connection establishment
complete message carries D2D capability information of the second
user equipment, and the D2D capability information of the second
user equipment is used for indicating that the second user
equipment supports the D2D function;
[0250] one or both of the above-mentioned radio resource control
connection establishment request message and the above-mentioned
radio resource control connection establishment complete message
carry a non-access stratum identifier and an access stratum
identifier of the first user equipment;
[0251] one or both of the above-mentioned radio resource control
connection establishment request message and the above-mentioned
radio resource control connection establishment complete message
carry a service code of the first user equipment.
[0252] Further, in this embodiment, the initiating module 83 may
also initiate a request bearer resource modification flow to
trigger establishment of the above-mentioned DPS bearer, when no
DPS bearer is established between the second user equipment and the
serving base station in an attach process.
[0253] Specifically, the initiating module 83 may send a bearer
resource modification request message to a mobility management
entity, so that the mobility management entity sends the bearer
resource modification request message to a gateway;
[0254] the above-mentioned bearer resource modification request
message carries a linked bearer identity and an evolved packet
system bearer identity related with the above-mentioned DPS bearer,
and the above-mentioned bearer resource modification request
message is added with a D2D connection type indicator or has a
dedicated packet data network connection for management of the DPS
bearer.
[0255] Further, the user equipment in this embodiment may also
include a message receiving module 84 and a message sending module
85;
[0256] wherein, the message receiving module 84 is configured to
receive a D2D link establishment request message sent by the first
user equipment; wherein the D2D link establishment request message
carries an identifier of the first user equipment, an identifier of
the second user equipment and channel state information and
resource allocation condition of the first user equipment, and
receive a D2D link establishment complete message sent after the
first user equipment receives a D2D link establishment response
message sent by the message sending module 85;
[0257] the message sending module 85 is configured to send a D2D
link establishment response message to the first user equipment
after the message receiving module 84 receives the D2D link
establishment request message and if connection establishment is
permitted, wherein the D2D link establishment response message
carries the identifier of the second user equipment, the identifier
of the first user equipment, channel state information of the
second user equipment and an accepting or rejecting response of the
second user equipment to the resource allocation condition of the
first user equipment.
[0258] The above-mentioned user equipment may realize establishment
of the DPS bearer with a user equipment supporting the D2D
function, realize communication with the user equipment supporting
the D2D function and further realize resource controllability of a
network.
[0259] It should be understood by those skilled in the art that,
each accompanying drawing is merely a schematic diagram of one
preferred embodiment, and modules or flows in the accompanying
drawings are not definitely necessary for implementing the present
invention.
[0260] It should be understood by those skilled in the art that,
modules in the device of the embodiments may be distributed in the
device of the embodiments according to the description of the
embodiments or located in one or more devices different from these
embodiments through corresponding variation. The modules of the
above-mentioned embodiments may be combined into one module or
further split into multiple sub-modules.
[0261] In the end, it should be noted that the preceding
embodiments are only used to illustrate the technical solutions of
the present invention rather than limiting the present invention;
though the present invention is illustrated in detail by referring
to the preceding embodiments, it should be understood by those of
ordinary skill in the art that modifications may still be made on
the technical solutions recorded in the preceding respective
embodiments, or equivalent alterations may be made to a part of
technical characteristics thereof; and these modifications or
alterations do not make the nature of corresponding technical
solutions depart from the scope of the technical solutions of the
respective embodiments of the present invention.
* * * * *