U.S. patent application number 16/246563 was filed with the patent office on 2019-05-16 for method of updating network detection and selection information and traffic routing information.
The applicant listed for this patent is ACER INCORPORATED. Invention is credited to Ching-Wen Cheng, Wei-Chen Pao.
Application Number | 20190150040 16/246563 |
Document ID | / |
Family ID | 52823477 |
Filed Date | 2019-05-16 |
![](/patent/app/20190150040/US20190150040A1-20190516-D00000.png)
![](/patent/app/20190150040/US20190150040A1-20190516-D00001.png)
![](/patent/app/20190150040/US20190150040A1-20190516-D00002.png)
![](/patent/app/20190150040/US20190150040A1-20190516-D00003.png)
![](/patent/app/20190150040/US20190150040A1-20190516-D00004.png)
![](/patent/app/20190150040/US20190150040A1-20190516-D00005.png)
![](/patent/app/20190150040/US20190150040A1-20190516-D00006.png)
![](/patent/app/20190150040/US20190150040A1-20190516-D00007.png)
![](/patent/app/20190150040/US20190150040A1-20190516-D00008.png)
![](/patent/app/20190150040/US20190150040A1-20190516-D00009.png)
![](/patent/app/20190150040/US20190150040A1-20190516-D00010.png)
View All Diagrams
United States Patent
Application |
20190150040 |
Kind Code |
A1 |
Pao; Wei-Chen ; et
al. |
May 16, 2019 |
Method of Updating Network Detection and Selection Information and
Traffic Routing Information
Abstract
A method of updating network detection and selection information
and traffic routing information for a communication device in a
wireless communication system is disclosed. The method comprises
updating network detection and selection information and traffic
routing information during a handover procedure, wherein updating
the network detection and selection information and traffic routing
information during the handover procedure comprises receiving an
access node change command to device message including the network
detection and selection information and traffic routing information
from an access node, wherein the network detection and selection
information and traffic routing information includes parameters of
the RAN assistance information/RAN rules, and updating the
parameters of the RAN assistance information/RAN rules.
Inventors: |
Pao; Wei-Chen; (New Taipei
City, TW) ; Cheng; Ching-Wen; (New Taipei City,
TW) |
|
Applicant: |
Name |
City |
State |
Country |
Type |
ACER INCORPORATED |
New Taipei City |
|
TW |
|
|
Family ID: |
52823477 |
Appl. No.: |
16/246563 |
Filed: |
January 14, 2019 |
Related U.S. Patent Documents
|
|
|
|
|
|
Application
Number |
Filing Date |
Patent Number |
|
|
14669005 |
Mar 26, 2015 |
10237791 |
|
|
16246563 |
|
|
|
|
61970914 |
Mar 27, 2014 |
|
|
|
Current U.S.
Class: |
370/331 |
Current CPC
Class: |
H04W 36/0066 20130101;
H04W 48/18 20130101; H04W 36/0083 20130101; H04W 8/18 20130101;
H04W 48/16 20130101 |
International
Class: |
H04W 36/00 20060101
H04W036/00; H04W 48/16 20060101 H04W048/16 |
Claims
1. A method of updating network detection and selection information
and traffic routing information for a communication device in a
wireless communication system, the method comprising: updating
network detection and selection information and traffic routing
information during a handover procedure; wherein updating the
network detection and selection information and traffic routing
information during the handover procedure comprises: receiving an
access node change command to device message including the network
detection and selection information and traffic routing information
from an access node, wherein the network detection and selection
information and traffic routing information includes parameters of
the RAN assistance information/RAN rules; and updating the
parameters of the RAN assistance information/RAN rules.
2. The method of claim 1, wherein the access node change command to
device message includes parameters of the RAN assistance
information/RAN rules from an anchor node.
3. The method of claim 1, wherein the access node change command to
device message is a radio resource control (RRC) connection
reconfiguration message.
Description
CROSS REFERENCE TO RELATED APPLICATIONS
[0001] This application is a continuation of U.S. application Ser.
No. 14/669,005 filed on 2015 Mar. 26, which claims the benefit of
U.S. Provisional Application No. 61/970,914, filed on Mar. 27,
2014.
BACKGROUND OF THE INVENTION
1. Field of the Invention
[0002] The present invention relates to a method used in a
communication device in a wireless communication system, and more
particularly, to a method of updating network detection and
selection information and traffic routing information.
2. Description of the Prior Art
[0003] 3GPP in Release 11 proposes Access Network Discovery and
Selection Function (ANDSF) Management Object (MO) to manage
Inter-System Mobility Policy (ISMP) and Inter-System. Routing
Policy (ISRP) as well as access network discovery information
stored in a user equipment (UE) supporting provisioning of such
information from an ANDSF, which is a network element providing
access network (e.g. WEAN) discovery and selection assistance data
as per operators' policy. In a word, ANDSF provides information
containing network detection and selection information and traffic
routing information to assist the UE with selecting the access
network or the inter-system mobility policy to control and assist
the UE with performing the inter-system change or to assist the UE
with determining how to route IP traffics or all of the above
mentioned. This information also contains ISMP, which prioritizes
the access network when the UE is not capable to connect to the EPC
through multiple accesses, and ISRP, which indicates how to
distribute traffic among available accesses when the UE is capable
to connect to the EPC through multiple accesses while access
network discovery and selection information provides further
information for the UE to access the access network defined in the
ISMP or in the ISRP or in the access network discovery
information.
[0004] Please refer to FIG. 1, which illustrates ANDSF operation
according to the prior art. The ANDSF of Public Land Mobile Network
(PLMN) sends ANDSF MO indicating a preferred Service Set Identifier
(SSID) for identifying a WLAN or a priority of SSIDs, to the UE.
The UE determines whether to use a WLAN according to the
information (i.e. SSID) obtained from the ANDSF MO kept in the UE.
For example, when the UE moves into the service coverage of a WLAN,
the UE could be aware of the existing of the WLAN by a SSID
broadcasted by the WLAN AP (Access Point). If the broadcasted SSID
is the SSID indicated in the ANDSF MO, the UE selects the WLAN.
Note that, ANDSF rules (including ISRP/ISMP) may be provided to the
UE via the ANDSF MO or pre-configured at the UE.
[0005] Please refer to FIG. 2, which illustrates ANDSF rules
supporting RAN assistance information. The eNB provides RAN
assistance information to the UE, wherein the RAN assistance
information includes parameters and/or values, such as
threshRsrpLow=-90 dBm, threshRsrpHigh=-80 dbm, threshRsrqLow=3 dB,
threshRsrqHigh=4 dB, etc. The UE applies the parameters as well as
the values associated to specific parameters of RAN assistance
information to ANDSF rules (including IARP rule, ISMP rule, ISRP
rule, etc.) obtained via the ANDSF MO or via existing OMA-DM
mechanisms or pre-configured at the UE. In a word, when the UE
receives RAN assistance information, this information is taken into
account for evaluating the provisioned ANDSF rules.
[0006] However, RAN assistance information could be different or
out-of-date when the UE changes serving RAN access node (e.g. a
serving eNB). In addition, RAN rules could be different when the
device changes serving PLMN or serving RAN access node. In detail,
please refer to FIG. 3, which illustrates that the UE supporting
ANDSF operation moves from the source cell to the target cell. In
case the source cell and the target cell belong to different PLMNs,
the mobility of the UE may also bring out the change of PLMN.
Therefore, the applicant notices that a mechanism is needed to
provide and to update RAN rules and RAN assistance information to
the UE.
[0007] In addition, RAN assistance information could be updated
frequently to reflect the RAN condition, or RAN rules should be
update to the UE efficiently for better user experience and load
balancing. However, RAN assistance information or RAN rules update
could be cumbersome so that the delivery of RAN assistance
information or RAN rules could consume a lot of radio resource.
Therefore, the applicant believes a mechanism is needed to provide
reduced amount of data sent from access node to the UE.
SUMMARY OF THE INVENTION
[0008] It is therefore an objective to provide a method of updating
network detection and selection information and traffic routing
information to solve the above problem.
[0009] The present invention discloses a method of updating network
detection and selection information and traffic routing information
for a communication device in a wireless communication system. The
method comprises updating network detection and selection
information and traffic routing information during a handover
procedure, wherein updating the network detection and selection
information and traffic routing information during the handover
procedure comprises receiving an access node change command to
device message including the network detection and selection
information and traffic routing information from an access node,
wherein the network detection and selection information and traffic
routing information includes parameters of the RAN assistance
information/RAN rules, and updating the parameters of the RAN
assistance information/RAN rules.
[0010] These and other objectives of the present invention will no
doubt become obvious to those of ordinary skill in the art after
reading the following detailed description of the preferred
embodiment that is illustrated in the various figures and
drawings.
BRIEF DESCRIPTION OF THE DRAWINGS
[0011] FIG. 1 is a schematic diagram of an ANDSF operation
according to the prior art.
[0012] FIG. 2 is a schematic diagram of ANDSF rules supporting RAN
assistance information.
[0013] FIG. 3 is a schematic diagram of a handover procedure of a
UE supporting an ANDSF operation.
[0014] FIG. 4 is a schematic diagram of a wireless communication
system.
[0015] FIG. 5 is a schematic diagram of an exemplary communication
device.
[0016] FIG. 6 is a schematic diagram of an enhanced ANDSF
operation.
[0017] FIG. 7 is a flowchart of an exemplary process according to
the present disclosure.
[0018] FIGS. 8-12 illustrate a message flow of an access stratum
procedure for RAN info update.
[0019] FIGS. 13-24 illustrate a message flow of a handover
procedure for RAN info update.
[0020] FIGS. 25-26 illustrate a message flow of an area update
procedure for RAN info update.
[0021] FIGS. 27-28 illustrate a message flow of an attach procedure
for RAN info update.
[0022] FIGS. 29-37 illustrate the configurations of RAN info
according to the present disclosure.
[0023] FIGS. 38-40 illustrate RAN info update operation according
to the present disclosure.
[0024] FIGS. 41-42 illustrate an embodiment of RAN info update
according to the present disclosure.
DETAILED DESCRIPTION
[0025] Please refer to FIG. 4, which is a schematic diagram of a
wireless communication system. The wireless communication system is
a LTE system or other mobile communication systems, and is briefly
composed of at least a device (i.e. a UE), an access node (i.e. an
eNB), an anchor node (i.e. a MME) and a server node (i.e. ANDSF/OAM
server) of PLMN. Note that, FIG. 4 is simply utilized for
illustrating the structure of the wireless communication system,
where the number of UEs, eNBs, MMEs and ANDSF servers are not
limited herein. The UEs can be devices such as mobile phones,
computer systems, machine type devices, etc. Besides, the network
node and the UE can be seen as a transmitter or receiver according
to transmission direction, e.g., for uplink (UL), the UE is the
transmitter and the network node is the receiver, and for downlink
(DL), the network node is the transmitter and the UE is the
receiver.
[0026] FIG. 5 illustrates a schematic diagram of an exemplary
communication device 50. The communication device 50 can be the
device or network node shown in FIG. 4. The communication device 50
may include a processing means 500 such as a microprocessor or
Application Specific Integrated Circuit (ASIC), a storage unit 510
and a communication interfacing unit 520. The storage unit 510 may
be any data storage device that can store program code 514, for
access by the processing means 500. Examples of the storage unit
510 include but are not limited to a subscriber identity module
(SIM), read-only memory (ROM), flash memory, random-access memory
(RAM), CD-ROMs, magnetic tape, hard disk, and optical data storage
device. The communication interfacing unit 520 is preferably a
radio transceiver and can exchange wireless signals with a network
node according to processing results of the processing means
500.
[0027] Please refer to FIG. 6, which illustrates an enhanced ANDSF
operation according to the present invention. Compared to the
legacy ANDSF operation of FIG. 1, the enhanced ANDSF (eANDSF)
operation includes RAN (Radio Access Network) assistance
information and/or RAN rules to enhance the efficiency of network
discovery and selection for the UE. RAN assistance information and
RAN rules are information provided by RAN element (e.g. eNB) that
reflects the current RAN situation (i.e. a radio condition,
available bandwidth, etc.). RAN rules are the rules which are given
by RAN element and utilize RAN assistance information.
[0028] Please refer to FIG. 7, which is a flowchart of a process 70
according to an example of the present disclosure. The process 70
is utilized in the UE, eNB, MME or ANDSF server of FIG. 5 for
updating network detection and selection information and traffic
routing information. The process 70 may be compiled into a program
code 514 to be stored in the storage unit 510, and may include the
following steps:
[0029] Step 700: Start.
[0030] Step 710: Update network detection and selection information
and traffic routing information by an access stratum procedure, a
handover procedure, an area update procedure, an attach procedure,
or a cell selection or reselection procedure.
[0031] Step 720: End.
[0032] According to the process 70, the network detection and
selection information and traffic routing information, including
RAN assistance information and RAN rules, hereafter called RAN
info, is updated via signaling/message of access stratum procedure,
handover procedure, area update procedure, attach procedure, or
cell selection or reselection procedure. In addition, RAN info may
be updated when the UE moves into a PLMN serving area, when the UE
moves into the coverage of a cell, when the UE moves into the area
of a cell cluster, or when the UE moves into the area of a
heterogeneous network (HetNet).
[0033] Some examples based on the process 70 are here described.
FIGS. 8-12 illustrate the message flow of an access stratum
procedure for RAN info update. In FIG. 8, the device (i.e. a UE)
queries the access node (i.e. an eNB) to obtain RAN info by sending
a UE RAN info query message to the serving access node to query RAN
info. The access node which receives the UE RAN info query message
from the device should reply to the requiring device a UE RAN info
update message with RAN info.
[0034] The UE RAN info query message may include an indicator of
interworking preference (e.g., offload preference, radio access
type (RAT) preference), indicator of the cause of request (e.g.,
request for RAN assistance information), indicator of the
capability to support RAN rules, indicator of the capability to
support RAN assistance information, capability of supported 3GPP
release, capability of supported RAN rules, capability of supported
RAN assistance information, and/or capability of supported RAN
rules and RAN assistance information sets. The implementation of
the UE RAN info query message could be a new message, or one of the
following messages: UECapabilityInformation, Measurement Report,
RRCConnection Request and RRCConnection Setup Complete.
[0035] The UE RAN info update message may include applied RAN
assistance information (e.g., RAN assistance information set),
applied RAN rules (e.g., rule set), RAN assistance information
(e.g., content of RAN assistance information), RAN rules (e.g.,
content of RAN rules), the configuration of RAN rules sets, the
configuration of RAN assistance information sets, the configuration
of RAN rules and RAN assistance information sets, supported RAN
rule sets of other cells, supported RAN assistance information sets
of other cells, and/or supported RAN rules and RAN assistance
information sets of other cells. The implementation of the UE RAN
info update message could be a new message, or one of the following
messages: RRCConnectionReconfiguration, MeasurementControl.
[0036] In FIG. 9, the device sends a UE RAN info query message to
the serving access node to query RAN info. The access node which
receives from the device a UE RAN info query message then sends an
eNB RAN info query message to the associated server node to query
RAN info. When the server node receives an eNB RAN info query
message from the access node, the server node sends an eNB RAN info
update message with RAN info to the requiring access node. When the
access node receives from the server node an eNB RAN info update
message with RAN info that associates to an eNB RAN info query
message issued by the access node, the access node should then send
a UE RAN info update message with RAN info to the corresponding
requesting device.
[0037] The eNB RAN info query message is used by the access node to
query the latest RAN info from the server node, and may include
indicator of interworking preference (e.g., offload preference, RAT
preference), indicator of the cause of request (e.g., request for
RAN rules), indicator of the capability to support RAN rules,
indicator of the capability to support RAN assistance information,
capability of supported 3GPP release, capability of supported RAN
rules, capability of supported RAN assistance information, and/or
capability of supported RAN rules and RAN assistance information
sets.
[0038] The eNB RAN info update is used by the server node to
deliver RAN info to the access node and may comprise applied RAN
assistance information (e.g., RAN assistance information set),
Applied RAN rules (e.g., rule set), RAN assistance information
(e.g., content of RAN assistance information), RAN rules (e.g.,
content of RAN rules), the configuration of RAN rules sets, the
configuration of RAN assistance information sets, the configuration
of RAN rules and RAN assistance information sets, supported RAN
rule sets of other cells, supported RAN assistance information sets
of other cells and/or supported RAN rules and RAN assistance
information sets of other cells.
[0039] In FIG. 10, when the access node receives a System RAN info
push to access message with RAN info from the associated server
node, the access node sends a UE RAN info push message with RAN
info to the device in the service coverage of the access node.
[0040] The system RAN info push to access message is used by the
server node to deliver the RAN info to one or more access nodes and
may comprise applied RAN assistance information, Applied RAN rules,
RAN assistance information, RAN rules, the configuration of RAN
rules sets, the configuration of RAN assistance information sets,
the configuration of RAN rules and RAN assistance information sets,
supported RAN rule sets of other cells, supported RAN assistance
information sets of other cells, supported RAN rules and RAN
assistance information sets of other cells.
[0041] The UE RAN info push message is used by the access node to
deliver RAN info to one or more devices and comprises applied RAN
assistance information (e.g., RAN assistance information set),
applied RAN rules (e.g., rule set), RAN assistance information
(e.g., content of RAN assistance information), RAN rules (e.g.,
content of RAN rules), the configuration of RAN rules sets, the
configuration of RAN assistance information sets, the configuration
of RAN rules and RAN assistance information sets, supported RAN
rule sets of other cells, supported RAN assistance information sets
of other cells, supported RAN rules and RAN assistance information
sets of other cells. The implementation of the UE RAN info push
message could be a new message, or one of the following messages:
RRCConnection Reconfiguration, MeasurementControl, Paging or SIB
(System Information block).
[0042] In FIG. 11, when the anchor node receives from the
associated server node a System RAN info push to anchor message
with RAN info, the anchor node then sends an eNB RAN info push
message with RAN info to the associated access nodes. When the
access node receives an eNB RAN info push message from an
associated anchor node, the access node then sends a UE RAN info
push message with RAN info to the device in the service coverage of
the access node.
[0043] The system RAN info push to anchor message is used by the
server node to deliver RAN info to one or more anchor node, and may
include applied RAN assistance information, applied RAN rules, RAN
assistance information, RAN rules, the configuration of RAN rules
sets, the configuration of RAN assistance information sets, the
configuration of RAN rules and RAN assistance information sets,
supported RAN rule sets of other cells, supported RAN assistance
information sets of other cells, and/or supported RAN rules and RAN
assistance information sets of other cells.
[0044] The eNB RAN info push message is used by the anchor node to
delivery RAN info to one or more access node and may include
applied RAN assistance information, applied RAN rules, RAN
assistance information, RAN rules, the configuration of RAN rules
sets, the configuration of RAN assistance information sets, the
configuration of RAN rules and RAN assistance information sets,
supported RAN rule sets of other cells, supported RAN assistance
information sets of other cells and/or supported RAN rules and RAN
assistance information sets of other cells.
[0045] In FIG. 12, the access node sends a UE RAN info push message
with RAN info to the device in the service coverage of the access
node.
[0046] FIGS. 13-24 illustrate a message flow of a handover
procedure for RAN info update. In FIG. 13, the device served by the
source access node is moving from the service coverage of the
source access node to the service coverage of the target access
node. The source access node receives an access node change trigger
message from the device and makes decision according to the
information carried in the access node change trigger message. Then
the source access node sends an access node change required message
to the associated anchor node. The anchor node received an access
node change required message makes decision according to the
information carried in the access node change required message. The
anchor node may query the associated server node for RAN info if
necessary. The anchor node sends an access node change request
message with RAN info to the target access node to request for
changing the access node of the device from the source access node
to the target access node. The access node receives from the anchor
node an access node change request message should reply with an
access node change request acknowledgement (ACK) message to the
anchor node. When the anchor node receives from the target access
node an access node change request ACK message which associated
with the access node change request message issued from the anchor
node to the target access node, the anchor node sends an access
node change command message with RAN info to the source access
node. When the source access node receives an access node change
command message with RAN info, and the access node change command
message associated with an access node change required message
which was issued by the source access node to the anchor node, the
source access node sends an access node change command to device
message with RAN info to the device which issued the associated
access node change trigger message. Then the access node change
complete procedure is performed.
[0047] The access node change trigger message may include indicator
of interworking preference (e.g., offload preference, RAT
preference), indicator of the cause of request (e.g., request for
RAN assistance information), indicator of the capability to support
RAN rules, indicator of the capability to support RAN assistance
information, capability of supported 3GPP release (e.g., rel-10,
rel-12), capability of supported RAN rules, capability of supported
RAN assistance information, capability of supported RAN rules and
RAN assistance information sets, and measurement results that may
include measurement result ID, measResultPCell,
measResultNeighCells.
[0048] The access node change required message may include
indicator of interworking preference (e.g., offload preference, RAT
preference), indicator of the cause of request (e.g., request for
RAN assistance information), indicator of the capability to support
RAN rules, indicator of the capability to support RAN assistance
information, capability of supported 3GPP release, capability of
supported RAN rules, capability of supported RAN assistance
information, capability of supported RAN rules and RAN assistance
information sets, Message type, MME UE SIAP ID, eNB UE SlAP ID,
handover type, cause, target ID, source to target transparent
container.
[0049] The access node change request message may include applied
RAN assistance information, applied RAN rules, RAN assistance
information, RAN rules, the configuration of RAN rules sets, the
configuration of RAN assistance information sets, the configuration
of RAN rules and RAN assistance information sets, supported RAN
rule sets of other cells, supported RAN assistance information sets
of other cells, supported RAN rules and RAN assistance information
sets of other cells, Message type, MME UE SIAP ID, Handover type,
cause, E-RABs To Be Setup List, UE Aggregate Maximum Bit Rate,
Source to Target Transparent Container, UE Security Capabilities,
Security Context.
[0050] The Access node change request ACK message may include
applied RAN assistance information, applied RAN rules, RAN
assistance information; RAN rules, the configuration of RAN rules
sets, the configuration of RAN assistance information sets, the
configuration of RAN rules and RAN assistance information sets,
supported RAN rule sets of other cells, supported RAN assistance
information sets of other cells, supported RAN rules and RAN
assistance information sets of other cells, Message type, MME UE
SIAP ID, eNB UE SlAP ID, E-RABs To Be Setup List, Target to Source
Transparent Container, UE Security Capabilities, Security
Context.
[0051] The access node change command message is used by the anchor
node to deliver the RAN info to the source access node, thus the
source access node may include applied RAN assistance information,
Applied RAN rules, RAN assistance information, RAN rules, the
configuration of RAN rules sets, the configuration of RAN
assistance information sets, the configuration of RAN rules and RAN
assistance information sets, supported RAN rule sets of other
cells, supported RAN assistance information sets of other cells,
supported RAN rules and RAN assistance information sets of other
cells, Message type, MME UE SIAP ID, eNB UE SlAP ID, Handover type,
E-RABs To Be Setup List, Target to Source Transparent
Container.
[0052] The access node change command to device message is used by
the source access node to deliver the RAN info of the target access
node to the device, and may include applied RAN assistance
information, applied RAN rules, RAN assistance information, RAN
rules, the configuration of RAN rules sets, the configuration of
RAN assistance information sets, the configuration of RAN rules and
RAN assistance information sets, supported RAN rule sets of other
cells, supported RAN assistance information sets of other cells,
supported RAN rules and RAN assistance information sets of other
cells, Message type, MME UE SIAP ID, eNB UE SlAP ID, Handover type,
E-RABs To Be Setup List, Target to Source Transparent
Container.
[0053] In FIG. 14, the device served by a source access node is
moving from the service coverage of the source access node to the
service coverage of the target access node. The source access node
receives an access node change trigger message from the device and
makes decision according to the information carried in the access
node change trigger message. The source access node sends an access
node peer change request message to the target access node. The
target access node received an access node peer change request
message may query the associated server node for RAN info if
necessary. The target access node sends an access node peer change
request ACK message with RAN info to the source access node. When
the source access node receives an access node peer change request
ACK message with RAN info, and the access node peer change request
ACK message associated with an access node peer change request
message which was issued by the source access node to the target
access node, the source access node sends an access node change
command to device message with RAN info to the device which issued
the associated access node change trigger message. Then the access
node change complete procedure is performed.
[0054] The access node peer change request message may include
applied RAN assistance information, applied RAN rules, RAN
assistance information, RAN rules, the configuration of RAN rules
sets, the configuration of RAN assistance information sets, the
configuration of RAN rules and RAN assistance information sets,
supported RAN rule sets of other cells, supported RAN assistance
information sets of other cells, supported RAN rules and RAN
assistance information sets of other cells, Message type, MME UE
SIAP ID, Handover type, cause, E-RABs To Be Setup List, UE
Aggregate Maximum Bit Rate, Source to Target Transparent Container,
UE Security Capabilities, Security Context.
[0055] The Access node peer change request ACK message may include
applied RAN assistance information, applied RAN rules, RAN
assistance information, RAN rules, the configuration of RAN rules
sets, the configuration of RAN assistance information sets, the
configuration of RAN rules and RAN assistance information sets,
supported RAN rule sets of other cells, supported RAN assistance
information sets of other cells, supported RAN rules and RAN
assistance information sets of other cells, Message type, MME UE
SIAP ID, eNB UE SlAP ID, E-RABs To Be Setup List, Target to Source
Transparent Container, UE Security Capabilities, Security
Context.
[0056] FIG. 15 illustrates a message flow with different sequence
to the FIG. 13. As can be seen, in FIG. 15, a query RAN info step
is arranged between the access node change request and access node
change request ACK. In other words, the target access node requests
RAN info from server node by itself. When the target access node
receives RAN info from the server node, the target access node
sends an access node change request ACK message with RAN info to
the anchor node. Other messages remain the same sequence as in FIG.
13, so the detailed description can be referred from above.
Similarly, FIG. 16 illustrates a different message sequence to the
FIG. 13. The access node change request and access node change
request ACK is arranged before the query RAN info step. When the
anchor node receives the access node change request ACK from the
target access node, the anchor node performs the query RAN info
procedure to obtain the RAN info corresponding to the target access
node for the device which initiated the procedure by sending the
access node change trigger message to the source access node.
[0057] In FIG. 17, the device served by the source access node is
moving from the service coverage of the source access node to the
service coverage of the target access node. The source access node
receives access node change trigger message from the device and
makes decision according to the information carried in the access
node change trigger message. Then the source access node sends an
access node change required message to the associated anchor node.
The anchor node received an access node change required message
makes decision according to the information carried in the message.
Then the anchor node sends an access node change request message to
the target access node to request for changing the access node of
the device from the source access node to the target access node.
The target access node which receives an access node change request
message from an anchor node then sends an access node change
request ACK message to the anchor node. When the anchor node
receives from the target access node an access node change request
ACK message associated with an access node change request message
issued from the anchor node to the target access node, the anchor
node sends an access node change command message to the associated
source access node. When the source access node receives from the
anchor node an access node change command message associated with
an access node change required message which was issued by the
source access node to the anchor node, the source access node may
query the associated server node for RAN info if necessary. The
source access node sends an access node info transfer message with
RAN info to the target access node. The source access node sends an
access node change command to device message with RAN info to the
device which issued the associated access node change trigger
message. Then the access node change complete procedure is
performed.
[0058] The access node info transfer is used by the source access
node to deliver the RAN info to the target access node and may
include applied RAN assistance information, applied RAN rules, RAN
assistance information, RAN rules, the configuration of RAN rules
sets, the configuration of RAN assistance information sets, the
configuration of RAN rules and RAN assistance information sets,
supported RAN rule sets of other cells, supported RAN assistance
information sets of other cells, supported RAN rules and RAN
assistance information sets of other cells.
[0059] In FIG. 18, the device served by the source access node is
moving from the service coverage of the source access node to the
service coverage of the target access node. The source access node
receives an access node change trigger message from the device and
makes decision according to the information carried in the access
node change trigger message. Then the source access node sends an
access node change required message to the associated source anchor
node. The source anchor node received an access node change
required message makes decision according to the information
carried in the message. Then the source anchor node sends an anchor
node relocation request message to the target anchor node. The
target anchor node received an anchor node relocation request may
query the associated server node for RAN info if necessary. The
target anchor node sends an access node change request message with
RAN info to the target access node to request for changing the
access node of the device from the source access node to the target
access node. When the target access node receives an access node
change request message from the target anchor node, the target
access node sends an access node change request ACK message to the
target anchor node. When the target anchor node receives from the
target access node an access node change request ACK message which
associated with an access node change request message issued from
the target anchor node to the target access node, the target anchor
node sends an anchor node relocation response message with RAN info
to the source anchor node. The source anchor node received from the
target anchor node an anchor node relocation response message
associated with an anchor node relocation request message which was
issued by the source anchor node to the target anchor node, the
source anchor node sends an access node change command message with
RAN info to the associated source access node. When the source
access node receives from a source anchor node an access node
change command message with RAN info, and the access node change
command message associated with an access node change required
message which was issued by the source access node to the source
anchor node, the source access node sends an access node change
command to device message with RAN info to the device which issued
the associated access node change trigger message. Then the access
node change complete procedure is performed.
[0060] The anchor node relocation request message may include
indicator of interworking preference (e.g., offload preference, RAT
preference), indicator of the cause of request (e.g., request for
RAN assistance information), indicator of the capability to support
RAN rules, indicator of the capability to support RAN assistance
information, capability of supported 3GPP release, capability of
supported RAN rules, capability of supported RAN assistance
information, capability of supported RAN rules and RAN assistance
information sets, MME UE context, Source to Target transparent
container, RAN Cause, Target eNB Identity, CSG ID; CSG Membership
Indication, Target TAI, MS Info Change Reporting Action, CSG
Information Reporting Action, UE Time Zone, Direct Forwarding Flag,
Serving Network, applied RAN assistance information, applied RAN
rules, RAN assistance information, RAN rules, the configuration of
RAN rules sets, the configuration of RAN assistance information
sets, the configuration of RAN rules and RAN assistance information
sets, supported RAN rule sets of other cells, supported RAN
assistance information sets of other cells, and supported RAN rules
and RAN assistance information sets of other cells.
[0061] The anchor node relocation response message may include
applied RAN assistance information, applied RAN rules, RAN
assistance information, RAN rules, the configuration of RAN rules
sets, the configuration of RAN assistance information sets, the
configuration of RAN rules and RAN assistance information sets,
supported RAN rule sets of other cells, supported RAN assistance
information sets of other cells, supported RAN rules and RAN
assistance information sets of other cells, Cause, Target to Source
transparent container, Serving GW change indication, EPS Bearer
Setup List and Addresses and TEIDs.
[0062] FIG. 19 illustrates a message flow with different sequence
to the FIG. 18. As can be seen, in FIG. 19, the RAN info query step
is arranged before the anchor node relocation request. When the
source anchor node obtains the RAN info, the source anchor node
sends an anchor node relocation request message with RAN info to
the target anchor node. Other messages remain the same sequence as
in FIG. 18, so the detailed description can be referred from
above.
[0063] In FIG. 20, the device served by the source access node is
moving from the service coverage of the source access node to the
service coverage of the target access node. The source access node
receives an access node change trigger message from the device and
makes decision according to the information carried in the access
node change trigger message. Then the source access node sends an
access node change required message to the associated source anchor
node. The source anchor node received an access node change
required message makes decision according to the information
carried in the message. Then the source anchor node sends an anchor
node relocation request message to the target anchor node. The
source anchor node may query the associated server node for RAN
info if necessary. The source anchor node then sends a forward RAN
info configuration message with RAN info to the target anchor node.
The target anchor node sends an access node change request message
with RAN info to the target access node to request for changing the
access node of the device from the source access node to the target
access node. When the target access node receives an access node
change request message from the anchor node, the target access node
sends an access node change request ACK message to the anchor node.
When the target anchor node receives from the target access node an
access node change request ACK message which associated with an
access node change request message issued from the target anchor
node to the target access node, the target anchor node sends an
anchor node relocation response message with RAN info to the source
anchor node. The source anchor node received an anchor node
relocation response message associated with an anchor node
relocation request message which was issued by the source anchor
node, sends an access node change command message with RAN info to
the associated source access node. When the source access node
receives from the anchor node an access node change command message
with RAN info, and the access node change command message
associated with an access node change required message which was
issued by the source access node to the anchor node, the source
access node sends an access node change command to device message
with RAN info to the device which issued the associated access node
change trigger message. Then the access node change complete
procedure is performed.
[0064] The forward RAN info configuration message is used by the
source anchor node to forward the RAN info to the target anchor
node, and may include applied RAN assistance information, applied
RAN rules; RAN assistance information, RAN rules, the configuration
of RAN rules sets, the configuration of RAN assistance information
sets, the configuration of RAN rules and RAN assistance information
sets, supported RAN rule sets of other cells, supported RAN
assistance information sets of other cells and supported RAN rules
and RAN assistance information sets of other cells.
[0065] In FIG. 21, the device served by the source access node is
moving from the service coverage of the source access node to the
service coverage of the target access node. The source access node
receives an access node change trigger message from the device and
makes decision according to the information carried in the access
node change trigger message. Then the source access node sends an
access node change required message to the associated source anchor
node. The source anchor node received an access node change
required message makes decision according to the information
carried in the message. Then the source anchor node sends an anchor
node relocation request message to the target anchor node. The
source anchor node may decide to query the associated server node
for RAN info if necessary. The target anchor node received an
anchor node relocation request message sends an access node change
request message to the target access node to request for changing
the access node of the device from the source access node to the
target access node. The target access node received an access node
change request message from the anchor node sends an access node
change request ACK message to the anchor node. When the target
anchor node receives from the target access node an access node
change request ACK message which associated with an access node
change request message issued from the target anchor node to the
target access node, the target anchor node sends an anchor node
relocation response message to the source anchor node. The source
anchor node received an anchor node relocation response message
associated with an anchor node relocation request message which was
issued by the source anchor node, sends an access node change
command message with RAN info to the associated source access node.
When the source access node receives from the anchor node an access
node change command message with RAN info, and the access node
change command message associated with an access node change
required message which was issued by the source access node to the
anchor node, the source access node sends an access node change
command to device message with RAN info to the device which issued
the associated access node change trigger message. The source
access node sends an access node info transfer message with RAN
info to the target access node. Then the access node change
complete procedure is performed.
[0066] In FIG. 22, the device served by the source access node is
moving from the service coverage of the source access node to the
service coverage of the target access node. The source access node
receives an access node change trigger message from the device and
makes decision according to the information carried in the access
node change trigger message. Then the source access node sends an
access node change required message to the associated source anchor
node. The source anchor node received an access node change
required message makes decision according to the information
carried in the message. Then the source anchor node sends an anchor
node relocation request message to the target anchor node. The
target anchor node received an anchor node relocation request
message sends an access node change request message to the target
access node to request for changing the access node of the device
from the source access node to the target access node. The target
access node received an access node change request message from the
target anchor node may query the associated server node for RAN
info if necessary. The target access node sends an access node
change request ACK message with RAN info to the target anchor node.
When the target anchor node receives from the target access node an
access node change request ACK message with RAN info, and the
access node change request ACK message associated with an access
node change request message issued from the target anchor node to
the target access node, the target anchor node sends an anchor node
relocation response message with RAN info to the source anchor
node. The source anchor node received an anchor node relocation
response message with RAN info, and the anchor node relocation
response message associated with an anchor node relocation request
message which was issued by the source anchor node, the source
anchor node sends an access node change command message with RAN
info to the associated source access node. When the source access
node receives from the anchor node an access node change command
message with RAN info, and the access node change command message
associated with an access node change required message which was
issued by the source access node to the anchor node, the source
access node sends an access node change command to device message
with RAN info to the device which issued the associated access node
change trigger message. Then the access node change complete
procedure is performed.
[0067] In FIG. 23, the device served by the source access node is
moving from the service coverage of the source access node to the
service coverage of the target access node. The source access node
receives an access node change trigger message from the device and
makes decision according to the information carried in the access
node change trigger message. Then the source access node sends an
access node change required message to the associated source anchor
node. The source anchor node received an access node change
required message makes decision according to the information
carried in the message. Then the source anchor node sends an anchor
node relocation request message to the target anchor node. The
target anchor node sends an access node change request message to
the target access node to request for changing the access node of
the device from the source access node to the target access node.
The target access node received an access node change request
message from the target anchor node may query the associated server
node for RAN info if necessary. The target access node sends an
access node change request ACK message to the target anchor node.
When the target anchor node receives from the target access node an
access node change request ACK message which associated with an
access node change request message issued from the target anchor
node to the target access node, the target anchor node sends an
anchor node relocation response message to the source anchor node.
The source anchor node received an anchor node relocation response
message associated with an anchor node relocation request message
which was issued by the source anchor node, sends an access node
change command message to the associated source access node. When
the source access node receives from the anchor node an access node
change command message associated with an access node change
required message which was issued by the source access node to the
anchor node, the source access node may query the associated server
node for RAN info if necessary. The source access node sends an
access node change command to device message with RAN info to the
device which issued the associated access node change trigger
message. Then the access node change complete procedure is
performed.
[0068] In FIG. 24, the device served by the source access node is
moving from the service coverage of the source access node to the
service coverage of the target access node. The source access node
receives an access node change trigger message from the device and
makes decision according to the information carried in the access
node change trigger message. Then the source access node sends an
access node change required message to the associated source anchor
node. The source anchor node received an access node change
required message makes decision according to the information
carried in the message. Then the source anchor node sends an anchor
node relocation request message to the target anchor node. The
target anchor node received an anchor node relocation request
message sends an access node change request message to the target
access node to request for changing the access node of the device
from the source access node to the target access node. The target
access node received an access node change request message from the
target anchor node sends an access node change request ACK message
to the target anchor node. When the target anchor node receives
from the target access node an access node change request ACK
message which associated with an access node change request message
issued from the target anchor node to the target access node, the
target anchor node sends an anchor node relocation response message
to the associated source anchor node. The source anchor node
received an anchor node relocation response message associated with
an anchor node relocation request message which was issued by the
source anchor node, sends an access node change command message to
the associated source access node. When the source access node
receives from the anchor node an access node change command message
associated with an access node change required message which was
issued by the source access node to the anchor node, the source
access node may query the associated server node for RAN info if
necessary. The source access node sends an access node change
command to device message with RAN info to the device which issued
the associated access node change trigger message. The source
access node sends an access node info transfer message with RAN
info to the target access node. Then the access node change
complete procedure is performed.
[0069] FIGS. 25-26 illustrate a message flow of an area update
procedure for RAN info update. In FIG. 25, the device served by the
access node performs service region change procedure to update the
latest service region information to the service network. The
device sends a service region change request to eNB message to the
access node to initiate the service region change procedure. The
access node receives a service region change request to eNB message
from the device and makes decision according to the information
carried in the service region change request to eNB message. Then
the access node sends a service region change request to anchor
message to the associated anchor node. The anchor node received a
service region change request to anchor message may query the
associated server node for RAN info if necessary. The anchor node
sends a service region change accept to eNB message with RAN info
to the associated access node. When the access node receives from
an anchor node a service region change accept to eNB message with
RAN info, and the service region change accept to eNB message
associated with a service region change request to anchor message
the access node issued to the anchor node, the access node sends a
service region change accept to UE message with RAN info to the
device which issued the associated service region change request to
eNB message. When the device receives from the access node a
service region change accept to UE message which associated with a
service region change request to eNB message the device issued to
the access node, the service region change complete procedure is
performed.
[0070] The service region change request to eNB message may include
indicator of interworking preference (e.g., offload preference, RAT
preference), indicator of the cause of request (e.g., request for
RAN assistance information), indicator of the capability to support
RAN rules, indicator of the capability to support RAN assistance
information, capability of supported 3GPP release, capability of
supported RAN rules, capability of supported RAN assistance
information, capability of supported RAN rules and RAN assistance
information sets, protocol discriminator; security header type,
tracking area update request message identity, EPS update type, NAS
key set identifier and Old GUTI.
[0071] The service region change request to anchor message may
include indicator of interworking preference (e.g., offload
preference, RAT preference), indicator of the cause of request
(e.g., request for RAN assistance information), indicator of the
capability to support RAN rules, indicator of the capability to
support RAN assistance information, capability of supported 3GPP
release, capability of supported RAN rules, capability of supported
RAN assistance information; capability of supported RAN rules and
RAN assistance information sets, protocol discriminator, security
header type, tracking area update request message identity, EPS
update type, NAS key set identifier; Old GUTI.
[0072] The service region change accept to eNB message may include
applied RAN assistance information, applied RAN rules, RAN
assistance information, RAN rules, the configuration of RAN rules
sets, the configuration of RAN assistance information sets, the
configuration of RAN rules and RAN assistance information sets,
supported RAN rule sets of other cells, supported RAN assistance
information sets of other cells, supported RAN rules and RAN
assistance information sets of other cells, protocol discriminator,
security header type, tracking area update accept message identity,
EPS update result and spare half octet.
[0073] The service region change accept to UE message may include
applied RAN assistance information, applied RAN rules, RAN
assistance information, RAN rules, the configuration of RAN rules
sets, the configuration of RAN assistance information sets, the
configuration of RAN rules and RAN assistance information sets,
supported RAN rule sets of other cells, supported RAN assistance
information sets of other cells, supported RAN rules and RAN
assistance information sets of other cells, protocol discriminator,
security header type, tracking area update accept message identity,
EPS update result and spare half octet.
[0074] In FIG. 26, the device served by an access node decides to
perform service region change procedure to update the latest
service region information to the service network. The device sends
a service region change request to eNB message to the access node
to initiate the service region change procedure. The access node
receives a service region change request to eNB message from the
device and makes decision according to the information carried in
the service region change request to eNB message. Then the access
node sends a service region change request to anchor message to the
associated anchor node. The anchor node received a service region
change request to anchor message from an access node sends a
service region change accept to eNB message to the access node.
When an access node receives from an anchor node a service region
change accept to eNB message which associated with a service region
change request to anchor message the access node issued to the
anchor node, the access node may query the associated server node
for RAN info if necessary. The access node sends an access node
status transfer message with RAN info to the associated anchor
node. The access node sends a service region change accept to UE
message with RAN info to the associated device. When the device
receives from the access node a service region change accept to UE
message which associated with a service region change request to
eNB message the device issued to the access node, the service
region change complete procedure is performed.
[0075] The access node status transfer message may include applied
RAN assistance information, applied RAN rules, RAN assistance
information, RAN rules, the configuration of RAN rules sets, the
configuration of RAN assistance information sets, the configuration
of RAN rules and RAN assistance information sets, supported RAN
rule sets of other cells, supported RAN assistance information sets
of other cells, supported RAN rules and RAN assistance information
sets of other cells.
[0076] FIGS. 27-28 illustrate a message flow of an attach procedure
for RAN info update. In FIG. 27, the device decides to contact the
network to obtain network service. The device sends a contact
request to eNB message to the access node. The access node receives
a contact request to eNB message from the device and makes decision
according to the information carried in the contact request to eNB
message. Then the access node sends a contact request to anchor
message to the associated anchor node. The anchor node received a
contact request to anchor message from the access node may query
the associated server node for RAN info if necessary. The anchor
node sends a contact accept message with RAN info to the access
node. When the access node receives from an anchor node a contact
accept message with RAN info, and the contact accept message is
associated with a contact request to anchor message the access node
issued to the anchor node, the access node sends a connection
reconfiguration message with RAN info to the associated device.
When the device receives from the access node a connection
reconfiguration message which associated with a contact request to
eNB message that issued from the device to the access node, the
connection complete procedure is performed.
[0077] The contact request to eNB B message may include indicator
of interworking preference (e.g., offload preference, RAT
preference), indicator of the cause of request (e.g., request for
RAN assistance information), indicator of the capability to support
RAN rules, indicator of the capability to support RAN assistance
information, capability of supported 3GPP release, capability of
supported RAN rules, capability of supported RAN assistance
information, capability of supported RAN rules and RAN assistance
information sets, protocol discriminator, security header type,
attach request message identity, EPS attach type, NAS key set
identifier, EPS mobile identity, UE network capability and ESM
message container.
[0078] The contact request to anchor message may include indicator
of interworking preference (e.g., offload preference, RAT
preference), indicator of the cause of request (e.g., request for
RAN assistance information), indicator of the capability to support
RAN rules, indicator of the capability to support RAN assistance
information, capability of supported 3GPP release, capability of
supported RAN rules, capability of supported RAN assistance
information, capability of supported RAN rules and RAN assistance
information sets, protocol discriminator, security header type;
attach request message identity, EPS attach type, NAS key set
identifier, EPS mobile identity, UE network capability, ESM message
container.
[0079] The contact accept message may include applied RAN
assistance information, applied RAN rules, RAN assistance
information, RAN rules, the configuration of RAN rules sets, the
configuration of RAN assistance information sets, the configuration
of RAN rules and RAN assistance information sets, supported RAN
rule sets of other cells, supported RAN assistance information sets
of other cells, supported RAN rules and RAN assistance information
sets of other cells, protocol discriminator; security header type,
attach accept message identity, EPS attach result, spare half
octet, T3412 value, TAI list and ESM message container.
[0080] The connection reconfiguration message may include applied
RAN assistance information, applied RAN rules, RAN assistance
information, RAN rules, the configuration of RAN rules sets, the
configuration of RAN assistance information sets, the configuration
of RAN rules and RAN assistance information sets, supported RAN
rule sets of other cells, supported RAN assistance information sets
of other cells, supported RAN rules and RAN assistance information
sets of other cells, rrc-TransacionIdentifier, critical Extensions
and SecurityConfigHO.
[0081] In FIG. 28, the device decides to contact the network to
obtain network service. The device sends a contact request to eNB
message to the access node. The access node receives a contact
request to eNB message from the device and makes decision according
to the information carried in the contact request to eNB message.
Then the access node sends a contact request to anchor message to
the associated anchor node. The anchor node received a contact
request to anchor message from the access node sends a contact
accept message to the access node. When the access node receives
from an anchor node a contact accept message which associated with
a contact request to anchor message the access node issued to the
anchor node, the access node may query the associated server node
for RAN info if necessary. The access node then may send the access
node status transfer message with RAN info to the anchor node. The
access node sends a connection reconfiguration message with RAN
info to the associated device. When the device receives from the
access node a connection reconfiguration message which associated
with a contact request to eNB message the device issued to the
access node, the connection complete procedure is performed.
[0082] As can be seen, by including new information elements in the
signaling/message of the access stratum procedure, handover
procedure, area update procedure, attach procedure. The access
nodes, server node and device can query and obtain RAN info for
update.
[0083] In order to include RAN assistance information and RAN rules
in the signaling or the abovementioned message of the access
stratum procedure, handover procedure, area update procedure and
attach procedure, the present invention provides a set design for
the RAN rules and RAN assistance information for reducing the
amount of data (i.e. RAN info).
[0084] Set design is illustrated as follows. The RAN assistance
information (hereafter called RAI) includes parameters, which are
grouped into RAI sets. For example, the parameters may include
threshDIBackhaulRateLow, threshRsrpLow, threshOffloadPreference,
threshBSSLoadHigh, threshRsrpHigh, and threshRsrqLow. A RAI set can
be identified with a RAI set number. The Server node may maintain
RAI sets and may send configure of RAI sets to the device. The RAI
sets may be stored in the device. In addition, the access node may
support some of RAI sets.
[0085] In addition, each parameter of RAN assistance information
may be associated to a value. FIG. 29 illustrates a first example
of configuration of RAI sets. RAN assistance information includes
four parameters, i.e., Parameter1, Parameter2, Parameter3, and
Parameter4, which are grouped into 16 RAI sets, i.e. RAI Set1-RAI
Set16. Four binary bits are used to present whether parameters are
included in the RAI set. RAI set1 is presented as {1,1,1,0}, which
means Parameter1, Parameter2, and Parameter3 are included in RAI
set1, but no Parameter4 in RAI set1.
[0086] FIG. 30 illustrates a second example of configuration of RAI
sets. RAN assistance information includes four parameters, i.e.,
Parameter1, Parameter2, Parameter3, and Parameter4, which are
grouped into 16 RAI sets. Four binary bits are used to present
whether parameters are included in the RAI set. For example,
{1,1,1,0} is presented that Parameter1, Parameter2, and Parameter3
are included in RAI set.
[0087] FIG. 31 illustrates a third example of configuration of RAI
sets. Similarly, there are four parameters, i.e. parameter1,
parameter2, parameter3, and parameter4, which are grouped into 4
RAI sets and each RAI set has an associated set identity, i.e. RAI
Set1-RAI Set4. RAI Set1 includes Parameter1. RAI Set2 includes
Parameter1 and Parameter2. RAI Set3 includes Parameter1,
Parameter2, and Parameter3. RAI Set4 includes Parameter1,
Parameter2, Parameter3, and Parameter4.
[0088] With the same manner, RAN rules (hereafter called RRs) could
be presented in a set design. In other words, RAN rules can be
grouped into RR sets. RAN rules may comprise (1) "IARP for NSWO"
rule: Route YouTube traffic directly to WLAN if the WLAN's backhaul
rate is greater to threshDIBackhaulRateLow; (2) "IARP for APN"
rule: Route Skype traffic to APN-x if the WLAN's BSS load exceeds
threshBssLoadHigh; (3) "ISMP" rule: Prefer EPC access over WLAN if
measured RSRP<threshRsrpLow; (4) "ISMP" rule: Prefer EPC access
over 3GPP if offloadpreference<threshoOffloadPreference and
measured RSRP>threshRsrpHigh; (5) "ISRP for IFOM" rule: Route
UDP/RTP flows to WLAN if Offload
preference>=threshOffloadPreference; (6) "WLANSP" rule: Select a
WLAN that interworks with partner1.com if the WLAN's backhaul
rate>=threshDIBackhaulRateLow and measured
RSRQ<threshRsrgLow; and (7) "ISMP" rule: Prefer EPC access over
WLAN if offload preference>=threshOffloadPreference. A RR set
can be identified with a RR set number. The Server node maintains
RR sets and may send the configuration of RR sets to the device. RR
sets may be stored in devices. In addition, the access node may
support some of RR sets.
[0089] FIG. 32 illustrates a first example of configuration of RR
sets. There are four RAN rules, i.e., RAN Rule1, RAN Rule2, RAN
Rule3, and RAN Rule4, which are grouped into 4 RR sets, i.e., RR
Set1-RR Set4. RR Set1 includes RAN Rule1. RR Set2 includes RAN
Rule1 and RAN Rule2. RR Set3 includes RAN Rule1, RAN Rule2, and RAN
Rule3. RR Set4 includes RAN Rule1, RAN Rule2, RAN Rule3, and RAN
Rule4.
[0090] FIG. 33 illustrates a second example of configuration of RR
sets. There are four RAN Rules, i.e., RAN Rule1, RAN Rule2, RAN
Rule3, and RAN Rule4, which are grouped into 16 RR sets, i.e., RR
Set1-RR Set16. Four binary bits are used to present whether RAN
rules are included in the RR set. RR set 1 is presented as
{1,1,1,0}, which means RAN Rule1, RAN Rule2, and RAN Rule3 are
included in RR set1.
[0091] FIG. 34 illustrates a third example of configuration of RR
sets. There are four RAN Rules, i.e., RAN Rule1, RAN Rule2, RAN
Rule3, and RAN Rule4, which are grouped into 16 RR sets. Four
binary bits are used to present whether RAN rules are included in
the RR set. {1,1,1,0} is presented that RAN Rule1, RAN Rule2, and
RAN Rule3 are included in the set.
[0092] In an embodiment, RAN rules and RAN assistance information
(hereafter called RnR) could be presented in a set design. RAN
rules and RAN assistance information can be grouped into RnR sets.
A RnR set can be identified by a RnR set number. The server node
maintains RnR sets and may send the configuration to the device.
The RnR sets may be stored in the devices. In addition, the access
node may support some of RnR sets.
[0093] FIG. 35 illustrates a first example of configuration of RnR
sets. Two parameters and two RAN rules, i.e. Parameter1,
Parameter2, RAN Rule1, and RAN Rule2, are grouped into 16 RnR sets
and each RnR set has an associated set identity, i.e. RnR Set1-RnR
Set16. Four binary bits are used to present whether parameters and
RAN rules are included in the RnR set. RnR set1 is presented as
{1,1,1,1}, which means Parameter1, Parameter2, RAN Rule1 and RAN
Rule2 are included in RnR set1.
[0094] FIG. 36 illustrates a second example of configuration of RnR
sets. Two parameters and two RAN rules, i.e. Parameter1,
Parameter2, RAN Rule1, and RAN Rule2, are grouped into 16 RnR sets.
Four binary bits are used to present whether parameters and RAN
rules are included in the RnR set. {1,1,1,1} is presented that
Parameter1, Parameter2, RAN Rule1 and RAN Rule2 are included in the
set.
[0095] FIG. 37 illustrates a third example of configuration of RnR
sets. Two parameters and two RAN rules, i.e. Parameter1,
Parameter2, RAN Rule1, RAN Rule2, and RAN Rule3, are grouped into 4
RnR sets and each RnR set has an associated set identity, i.e. RnR
Set1-RnR Set4. RnR Set1 includes Parameter1 and RAN Rule1. RnR Set2
includes Parameter2 and RAN Rule2. RnR Set3 includes Parameter1,
Parameter2, RAN Rule1, and RAN Rule2. RnR Set4 includes Parameter1,
Parameter2, RAN Rule1, RAN Rule2, and RAN Rule3.
[0096] Based on the process 70 and the RAN info set design, RAN
info (i.e. RAN assistance information and RAN rules) could be
updated with set-based configuration in the abovementioned
signaling/message of access stratum, handover, area update or
attach procedure.
[0097] Besides, the access node may update the RAN info by
providing the RAI set number/RR set number/RnR set number and
values of a RAI set/RnR set to the device. Therefore, the device
can apply the received values to the corresponding parameters of
the RAI set/RnR set stored in the device or apply RAN rules in the
RR set stored in the device.
[0098] For detailed RAN info update operation, please refer to
FIGS. 38-40. In FIG. 38, set-based RAI configuration/set-based RR
configuration/set-based RnR configuration may be pre-configured in
the server node of the PLMN. RAI set1 includes Parameter1. RAI set2
includes Parameter1 and Parameter2. RR set1 includes RAN Rule1. RR
set2 includes RAN Rule1 and RAN Rule2. Sever node may provide RAI
sets/RR sets/RnR sets to the device and access node1 and access
node2. The device, access node1 and access node2 store the RAI
sets/RR sets/RnR sets. Note that, RnR sets are not shown in FIG.
38-40 for simplicity, but applied with the same operation as RAI
sets/RR sets. Access node1 may support RAN info update for RAI set1
and RR set1. Access node2 may support RAN info update for RAI set2
and RR set2. When the device moves close to the access node1, the
access node1 may provide RAN info update to the device, i.e. RAI
set1=-90 dBm and RR set1. On the other hand, when the device moves
close to the access node2, the access node2 may provide RAN info
update to device, i.e. RAI set2={-90 dBm, 4 dB} and RR set2.
[0099] In FIG. 39, set-based RAI configuration/set-based RR
configuration/set-based RnR configuration is pre-configured in the
server node and access nodes. The server node does not provide RAI
sets, RR sets and RnR sets to the access node1 and access node2.
Access node1 may support RAN info update for RAI set1 and RR set1.
Access node2 may support RAN info update for RAI set2 and RR set2.
When the device moves close to the access node1, the access node1
may provide RAN info update to the device, i.e. RAI set1=-90 dBm
and RR set1. On the other hand, when the device moves close to the
access node2, the access node2 may provide RAN info update to
device, i.e. RAI set2={-90 dBm, 4 dB} and RR set2.
[0100] In FIG. 40, set-based RAI configuration/set-based RR
configuration/set-based RnR configuration is pre-configured in the
access nodes. Access node1 may support RAN info update for RAI set1
and RR set1. Access node2 may support RAN info update for RAI set2
and RR set2. When the device moves close to the access node1, the
access node1 may provide RAN info update to the device, i.e. RAI
set1=-90 dBm and RR set1. On the other hand, when the device moves
close to the access node2, the access node2 may provide RAN info
update to device, i.e. RAI set2={-90 dBm, 4 dB} and RR set2.
[0101] In an embodiment, the access node may provide only values of
a RAI set/RnR set to the device. If the device knows the RAI
set/RnR set used by the serving access node, the device can apply
the received values to corresponding parameters based on the stored
RAI sets/RnR sets. For example, the access node provides device a
list or a table to know neighboring access nodes' configuration of
supported RAN info.
[0102] For example, in FIG. 41, access node2 provides neighboring
access nodes' configuration of supported RAN info, which could be a
list or a table. The access node1 supports RR set1 and RAI set1.
The access node2 supports RR set2 and RAI set2. The device may
store the list or the table. When the device moves close to access
node1, the device may use the list or the table to understand the
configuration in the access node1, and the access node1 may provide
the update value to the device, i.e. -90 dBm. On the other hand,
when the device moves close to the access node2, the access node2
may provide the update values to the device, i.e., {-90 dBm, 4
dB}.
[0103] With the same manner, the access nodes may provide the
update value to the device, i.e. -90 dBm or {-90 dBm, 4 dB}, in
set-based RnR configuration. The detailed can be referred to FIG.
42.
[0104] The abovementioned steps of the processes including
suggested steps can be realized by means that could be a hardware,
a firmware known as a combination of a hardware device and computer
instructions and data that reside as read-only software on the
hardware device or an electronic system. Examples of hardware can
include analog, digital and mixed circuits known as microcircuit,
microchip, or silicon chip. Examples of the electronic system can
include a system on chip (SOC), system in package (SiP), a computer
on module (COM) and the communication device 60.
[0105] In conclusion, the present invention addresses to update
network detection and selection information and traffic routing
information, especially for RAN assistance information and RAN
rules. The UE, eNB and MME shall update the RAN assistance
information and RAN rules with set-based RAN assistance information
and RAN rules in the enhanced signaling/message of access stratum
procedure, handover procedure, area update procedure, attach
procedure, or cell selection or reselection procedure, so as to
reduce data amount for frequent update.
[0106] Those skilled in the art will readily observe that numerous
modifications and alterations of the device and method may be made
while retaining the teachings of the invention. Accordingly, the
above disclosure should be construed as limited only by the metes
and bounds of the appended claims.
* * * * *