WO2020088091A1 - Status reporting method and device, message receiving method and device, storage medium, and electronic device - Google Patents

Abstract

The present disclosure provides a status reporting method and device, a message receiving method and device, a storage medium, and an electronic device. The status reporting method comprises: receiving a first indication message from a master node (MN), wherein the first indication message carries at least the following information: inactivity timer information of user equipment (UE); and reporting, according to the first indication message, an inactive status of the UE. The present technical solution is employed to resolve the issue in which the inactive status of a user in a dual connectivity scenario cannot be continued after the bearer has changed, such that it takes too much time to restart a timer.

Description

Status reporting, message receiving method and device, storage medium, electronic device Technical field

The present disclosure relates to the field of communications, and in particular, to a method and device for status reporting, message reception, storage medium, and electronic device.

Background technique

Dual-Connectivity (DC for short) was introduced in Release-12 of the 3rd Generation Partnership Project (3GPP for short), and dual-connectivity technology makes full use of wireless from different stations (same system, different systems) Air interface resources to improve user experience rate. Using macro / micro networking to improve spectrum efficiency and load balance, terminals supporting dual connectivity can simultaneously connect two Long-Term Evolution (LTE) base stations to increase the throughput of a single user. 3GPP R15 introduces 4 / 5G dual connection technology based on LTE dual connection Wireless resource utilization reduces system switching delay and system user and system performance.

In the existing dual connection technology, after the bearer is changed, the UE inactivity state is reset, resulting in increased service power consumption and wasted air interface resources. For example, in the E-UTRA-NR dual connectivity (E-UTRA-NR Dual Connectivity, referred to as EN-DC) scenario, the master node (Master Node, referred to as MN) bears decision-making, and the secondary node (Secondary Node, referred to as SN) It only reports the UE inactivity status (active, inactive), and the MN decides whether to release it. When the bearer is changed from the Master Cell Group (MCG) to the Secondary Cell Group (SCG) bearer (or the MN termination node to the SN termination node is changed), the UE is inactive under the original MN bearer The timer cannot continue delivery, resulting in the need to restart the timer after the bearer changes, and the user inactivity timer ue-InactiveTime specified in the protocol [1s, over 30 days].

The current standard protocol stipulates X2 port switching in the LTE system. The source eNB transmits the ue-InactiveTime cell to the target eNB through the X2 port Container. The target eNB continues the UE inactivity state after receiving it, improving air interface resource utilization and terminal power saving. The 3GPP R15 protocol has not considered this issue during the evolution of dual-connectivity (Multi-Radio Dual Connectivity, MR-DC).

The current problems are shown in Figure 1, including the following steps:

1). The MN initiates the SN addition request message, which includes the bearer type (MCG, SCG, Split) and bearer termination node type (MN terminated, SN terminated) information. The MN initiates the SN addition request, the MN has an LTE bearer before the UE is added, and maintains the UE inactivity timer, which is not carried in the message to the SN at this time.

2). The SN receives the MN's bearer service message, establishes the corresponding bearer, and replies with a confirmation response. If it is SN terminated termination bearer node, the service is changed from MCG bearer to SCG bearer, and a new user inactivity timer is reset and started.

3). The SN triggers to report the UE's inactive state according to the inactive state mechanism at a fixed period or event. If the UE is inactive, the MN decides the UE's inactive release strategy. If the UE is reactivated, it means that the new state has been reversed, and the MN has reactivated the service bearer on the SN side. Since the SN inactivity timer is maintained by the SN at this time and is not updated according to the state of the dual connection scenario, there may be an unreasonable problem that the timing is too long.

In the related art, in the dual connection scenario, the inactive state before the bearer change cannot be continued, which leads to the problem that the timing is too long, and no effective technical solution has been proposed.

Summary of the invention

Embodiments of the present disclosure provide a method and device for status reporting, message reception, storage medium, and electronic device, to at least solve the related art, in the dual connection scenario, the inactive state before the SN addition cannot be continued, which leads to overtime Long question.

According to an embodiment of the present disclosure, a status reporting method is provided, including:

Receiving a first indication message from the master node MN, where the first indication message is used to carry at least the following information: inactivity timer information of the user terminal UE;

Report the inactivity state of the UE according to the first indication information.

According to another embodiment of the present disclosure, a status reporting device is also provided, including:

The first receiving module is configured to receive a first indication message from the master node MN, where the first indication message is used to carry at least the following information: inactivity timer information of the user terminal UE;

The reporting module is configured to report the inactive state of the UE according to the first indication information.

According to another embodiment of the present disclosure, a message receiving method is also provided, including:

Receiving a second indication message from the secondary node SN, where the second indication message is used to carry at least the following information: inactivity timer information of the user terminal UE.

According to another embodiment of the present disclosure, a message receiving apparatus is also provided, including:

The second receiving module is configured to receive a second indication message from the secondary node SN, where the second indication message is used to carry at least the following information: inactivity timer information of the user terminal UE.

According to another embodiment of the present disclosure, there is also provided a storage medium including a stored program, wherein the program reporting method or message receiving method described in any one of the above is executed when the program is run.

According to another embodiment of the present disclosure, there is also provided an electronic device, and the storage medium includes a stored program, wherein the program reporting method or the message receiving method described in any one of the above is executed when the program runs.

Through the present disclosure, a first indication message from the master node MN is received, where the first indication message is used to carry at least the following information: inactivity timer information of the user terminal UE; report the inactivity of the UE according to the first indication information The active state adopts the above technical solution, which solves the problem that the inactive state before the SN addition cannot be continued in the dual connection scenario in the related art, thereby causing the problem that the timing is too long.

BRIEF DESCRIPTION

The drawings described herein are used to provide a further understanding of the present disclosure and form a part of the present application. The exemplary embodiments and descriptions of the present disclosure are used to explain the present disclosure and do not constitute an undue limitation on the present disclosure. In the drawings:

Figure 1 is a flowchart of user inactivity under dual connectivity in the prior art;

2 is a flowchart of a status reporting method according to an embodiment of the present disclosure;

3 is a flowchart of a user terminal inactivity time transfer process according to an example of the present disclosure;

4 is another flowchart of a user terminal inactivity time transfer process according to an example of the present disclosure;

5 is a flowchart of an SN addition process according to an example of the present disclosure;

6 is a flowchart of an MN-triggered SN modification process according to an example of the present disclosure;

7 is a flowchart of an SN-triggered SN modification process according to an example of the present disclosure;

8 is a flowchart of an MN triggered SN release process according to an example of the present disclosure;

9 is a flowchart of an SN triggered SN release process according to an example of the present disclosure;

10 is a flowchart of an SN-triggered SN change process according to an example of the present disclosure;

11 is a structural block diagram of a status reporting device according to an embodiment of the present disclosure;

12 is a flowchart of a message receiving method according to an embodiment of the present disclosure;

13 is a structural block diagram of a message receiving apparatus according to an embodiment of the present disclosure;

14 is a flowchart of MCG-> SCG bearer change according to a preferred embodiment of the present disclosure;

15 is a flowchart of changing the bearer type of MN Terminated bearer-> SN Terminated bearer according to the preferred embodiment of the present disclosure;

16 is a schematic diagram of MN terminated bearer change according to a preferred embodiment of the present disclosure;

FIG. 17 is a flowchart of changing the bearer type of SN Terminated bearer-> MN Terminated bearer according to the preferred embodiment of the present disclosure;

18 is a schematic diagram of SN terminated bearing change according to a preferred embodiment of the present disclosure;

FIG. 19 is a time flow chart of SN changing user inactivity state according to a preferred embodiment of the present disclosure.

detailed description

Hereinafter, the present disclosure will be described in detail with reference to the accompanying drawings and in conjunction with the embodiments. It should be noted that the embodiments in the present application and the features in the embodiments can be combined with each other if there is no conflict.

It should be noted that the terms “first”, “second”, etc. in the description and claims of the present disclosure and the above drawings are used to distinguish similar objects, and do not have to be used to describe a specific order or sequence.

In order to better understand the technical solutions of the embodiments of the present disclosure and the preferred embodiments of the present disclosure, the noun meanings of the embodiments of the present disclosure and the preferred embodiments are as follows:

Multi-system dual connection: Through non-ideal X2 / xn connections, one provides E-UTRA access and the other provides NR access. One node acts as the MN, the other node acts as the SN, and only the MN is connected to the core network.

MN termination node bearer: In the MR-DC dual connection, the PDCP of the wireless bearer is on the MN side.

SN termination node bearer: In the MR-DC dual connection, the PDCP of the wireless bearer is on the SN side.

MCG bearer: In the MR-DC dual connection, the wireless RLC is carried in the MCG.

SCG bearer: In the MR-DC dual connection, the wireless RLC is carried in the SCG.

Split bearer: In MR-DC dual connection, the wireless RLC bearer is in both MCG and SCG.

SpCell (Special Cell): the primary cell of the primary cell group and the secondary cell group.

In the related art, the UE maintains connection with two base stations at the same time. When the service bearer is changed from one base station to another base station, the user inactivity time mechanism cannot be effectively transmitted. The new bearer for service migration needs to set a new counter, which may increase the UE connection state time. In the state where the user has no service requirements, the terminal connection state time is unnecessarily increased, and the wireless air interface resources are also consumed.

The current protocol stipulates the following problems in the scenario:

1) In the dual connectivity scenario, the user inactivity timer fails to be transferred from the MN network element to the SN network element, or from the SN network element to the MN network element, resulting in the target network element resetting the new timer time, failing The user inactivity state before and after the change of the dual connection bearer continues, resulting in the problem of excessively long user timing.

2) The user inactivity timer control is only divided into the user UE level, and is not subdivided into the user bearer level, so it cannot be controlled separately for different bearers, and it cannot meet the requirements of refined business applications in vertical industries.

3) The user inactivity timer is not considered to be transferred between PDCP and RLC, so it is not effectively inherited in the bearer separation (CU / DU) scenario.

Example 1

In order to solve the above technical problems, a method for status reporting is provided in Embodiment 1. FIG. 2 is a flowchart of the status reporting method according to an embodiment of the present disclosure. As shown in FIG. 2, the process includes the following steps:

Step S202: Receive a first indication message from the master node MN, where the first indication message is set to carry at least the following information: inactivity timer information of the user terminal UE;

Step S204: Report the inactivity state of the UE according to the first indication information.

Through the present disclosure, a first indication message from the master node MN is received, where the indication message is used to carry at least the following information: inactivity timer information of the user terminal UE; report the inactivity of the UE according to the first indication information The active state adopts the above technical solution, which solves the problem that the inactive state before the bearer change cannot be continued in the dual connection scenario in the related art, thereby causing the problem that the timing is too long.

It should be noted that step S204 may be a fixed period or an event triggered to report the inactivity state of the UE, where the fixed period may be a fixed timer duration, and the user activity notification is directly reported to the MN after the timer expires. In the MN termination node mode, the MN side control plane is configured with a fixed period duration to control the PDCP and RLC states respectively. You can configure the bearer and user level cycle time according to the configuration. In the SN termination bearer mode, the SN side configures a fixed period to control the PDCP and RLC states, and can carry out periodic events at the bearer and user level according to the configuration. The range of the cycle time is in accordance with the ue-InactiveTime specified in the agreement. Event triggering, MN and SN internal decision, only when the current status and the last maintenance status information is inconsistent, event-driven trigger user activity notification to MN.

In the embodiment of the present disclosure, the inactivity timer information of the user terminal UE includes at least one of the following: remaining user inactivity time T1, user inactivity state maintenance time T2.

The remaining user inactive state time T1 refers to the remaining time of the user inactive state on the MN side. After the remaining time is exhausted, the MN can decide whether the user is released or not.

The user inactive state maintenance time T2 refers to the time during which the user on the MN side is maintained in the inactive state. After the inactive state maintenance time reaches the MN overall user inactive state set time, the MN can decide whether to release the user.

The embodiments of the present disclosure also provide the following technical solutions:

1). The user inactivity timer can be transmitted to the target side MN through the X2 / xn interface according to the user level (each UE) and the bearer level (each DRB). The user level means that the MN maintains only one UE level of user inactivity state information (T1 and T2), and the bearer level means that the MN needs to maintain one user multiple bearer (up to 16) user inactivity state information (T1 and T2) ).

2). The user inactivity timer can be displayed or implicitly passed to the target side. Explicit delivery means that the newly added cells in the message can be passed between the source side and the target side. Implicit delivery means passing through the existing cells and does not affect the main message structure.

3). After the SN receives the user inactivity related information, it can continue to be transmitted in the SN PDCP, SN RLC layer.

In the embodiment of the present disclosure, before receiving the indication message from the master node MN, the method further includes: triggering a bearer change and an SN change process.

Bearer changes include:

1) The bidirectional change of MCG to SCG of the MN termination node, the MN maintains the PDCP layer, and the RLC layer changes from MCG to SCG, that is, changes from MN RLC to SN RLC. Or change from SCG to MCG bearer, that is, change from SN RLC to MN RLC.

2) The two-way change of the MCG to Split of the MN termination node, the MN maintains the PDCP layer, and the RLC layer changes from MCG to Split, that is, changes from MN RLC to MN RLC and SN RLC. Or change from SCG Spit to MCG bearer, that is, change from MN RLC and SN RLC to MN RLC.

3) The bidirectional change from SCG to Split of the MN termination node, the MN maintains the PDCP layer, and the RLC layer changes from SCG to Split, that is, from SN RLC to SN RLC and MN RLC. Or change from SCG Spit to SCG bearer, that is, change from SN RLC and MN RLC to SN RLC.

4) The SN terminates the bidirectional change of MCG to SCG, the SN maintains the PDCP layer, and the RLC layer changes from MCG to SCG, that is, from MN RLC to SN RLC. Or change from SCG to MCG bearer, that is, change from SN RLC to MN RLC.

5) Two-way change of MCG to Split carried by SN termination, SN maintains PDCP layer, RLC layer changes from MCG to Split, that is, changes from MN RLC to MN RLC and SN RLC. Or change from SCG Spit to MCG bearer, that is, change from MN RLC and SN RLC to MN RLC.

6) Two-way change of SCG to Split carried by SN termination, SN maintains PDCP layer, RLC changes from SCG to Split, that is, changes from SN RLC to SN RLC and MN RLC. Or change from SCG Spit to SCG bearer, that is, change from SN RLC and MN RLC to SN RLC.

7). Change from SN termination bearer to MN termination node. Contains the scene.

-The MCG of the SN termination bearer is changed to the MCG of the MN termination node, that is, the PDCP migrates from the SN to the MN, and the RLC remains on the MN side.

-The MCG of the SN termination bearer is changed to the SCG of the MN termination node, that is, the PDCP migrates from the SN to the MN, and the RLC is changed from the MN side to the SN side.

-The MCG of the SN termination bearer is changed to the Split of the MN termination node, that is, the PDCP migrates from the SN to the MN, and the RLC changes from the MN side to the MN and SN side.

-The SCG of the SN termination bearer is changed to the MCG of the MN termination node, that is, PDCP migrates from the SN to the MN, and the RLC changes from the SN RLC to the MN RLC.

-The SCG of the SN termination bearer is changed to the SCG of the MN termination node, that is, the PDCP migrates from the SN to the MN, and the RLC remains at the SN RLC.

-The SCG of the SN termination bearer is changed to the Split of the MN termination node, that is, PDCP migrates from the SN to the MN, and the RLC is changed from the SN RLC to the MN RLC and SN RLC.

-The Split carried by the SN termination is changed to the MCG of the MN termination node, that is, the PDCP migrates from the SN to the MN, and the RLC is changed from the SN RLC and the MN RLC to the MN RLC.

-The Split of the SN termination bearer is changed to the SCG of the MN termination node, that is, the PDCP migrates from the SN to the MN, and the RLC is changed from the SN RLC and the MN RLC to the SN RLC.

-The split of the SN termination bearer is changed to the split of the MN termination node, that is, the PDCP migrates from the SN to the MN, and the RLC remains unchanged from the SN RLC and the MN RLC.

8). Change from MN termination node to SN termination bearer. Contains the scene.

-The MCG of the MN termination node is changed to the MCG carried by the SN termination, that is, the PDCP migrates from the MN to the SN, and the RLC remains on the MN side.

-The MCG of the MN termination node is changed to the SCG of the SN termination bearer, that is, the PDCP is migrated from the MN to the SN, and the RLC is changed from the MN RLC to the SN RLC.

-The MCG of the MN termination node is changed to the Split carried by the SN termination, that is, PDCP is migrated from the MN to the SN, and the RLC is changed from the MN RLC to the MN RLC and SN RLC.

-The SCG of the MN termination node is changed to the MCG carried by the SN termination, that is, the PDCP is migrated from the MN to the SN, and the RLC is changed from the SN RLC to the MN RLC.

-The SCG of the MN termination node is changed to the SCG carried by the SN termination, that is, the PDCP migrates from the MN to the SN, and the RLC remains at the SN RLC.

-The SCG of the MN termination node is changed to the Split carried by the SN termination, that is, PDCP is migrated from the MN to the SN, and the RLC is changed from the SN RLC to the MN RLC and SN RLC.

-Split of the MN termination node is changed to the MCG carried by the SN termination, that is, PDCP is migrated from MN to SN, and RLC is changed from SN RLC and MN RLC to MN RLC.

-Split of the MN termination node is changed to the SCG carried by the SN termination, that is, PDCP is migrated from MN to SN, and RLC is changed from SN RLC and MN RLC to SN RLC.

-The split of the MN termination node is changed to the split carried by the SN termination, that is, the PDCP migrates from the MN to the SN, and the RLC remains unchanged from the SN RLC and the MN RLC.

9). SN change process, that is, the MN remains unchanged, and the SN migrates from the old SN to the new SN. During the process, the old SN brings the user inactivity status information to the MN, and then the MN passes the passed user inactivity status. The information is then passed to the new SN. This process maintains the continuity of user inactivity.

In the embodiment of the present disclosure, reporting the inactivity state of the user terminal UE according to the first indication information includes determining the current inactivity timer information of the secondary node SN according to the first indication information; according to the current inactivity timing The device information is reported to the inactive state of the UE.

In the embodiment of the present disclosure, after receiving the first indication message from the master node MN, the method further includes: inheriting the remaining UE inactivity timer time through the SN, or setting a new timer time through the SN, or modifying the SN 'S current inactivity timer duration.

In the embodiment of the present disclosure, the first indication information includes at least one of the following: SN addition request message, SN modification request message triggered by SN modification, SN modification request confirmation message triggered by SN, SN modification request confirmation message, SN release Request message.

In order to better understand the above status reporting process, the following process will be described in conjunction with the following example.

3 and 4 are flowcharts of the inactive time transfer process of the user terminal according to an example of the present disclosure, including the following steps:

Step 1). The MN initiates the SN addition request message, and the content of the request message includes the bearer type (MCG, SCG, Split) and bearer termination node change type (MN terminated, SN terminated) information. The MN initiates the SN addition request. The MN has an LTE bearer before the UE is added and maintains the UE inactivity timer. This time the MN brings the UE inactivity information to the SN. There are two possibilities;

Scenario (1): The MN carries the remaining UE inactivity time T1 according to the UE level;

Scenario (2): The MN carries the UE inactivity state maintenance time T2 according to the UE level;

Step 2). The SN receives the MN's bearer service message, establishes the corresponding bearer, and replies with a response. Under the SN termination node bearer, the service is changed from the MCG bearer to the Split bearer. The SN side makes a decision based on the transfer information and local configuration strategy. The SN can inherit the remaining UE inactivity timer T1, the UE inactivity state maintenance time T2, or you can Set a new timer time T3.

Scenario (1): Because the SN terminates the node bearer, the SN maintains the PDCP state. The SN uses the remaining UE inactivity fixed time T1 as the current bearer user inactivity timer duration. The unused UE generates a new user inactivity timer T3 according to the bearer type. The SN can continue the user inactivity state. SN continues to pass to the RLC layer of SN PDCP and SN.

Scenario (2): Because the SN terminates the node bearer, the SN maintains the PDCP state. The SN receives the MN carrying the UE inactivity state maintenance time T2. The SN generates a new user inactivity timer T3 according to the UE's bearer type configuration. The SN uses the absolute difference between T2 and T3 as the new user inactivity effective timer. The SN delivers the effective timer duration to the SN PDCP and SN RLC layer.

Step 3). The SN reports the UE inactivity status through the SN activity notification according to the UE inactivity timer, period or event triggered by the MN.

A fixed timer is used in a fixed period, and the user activity notification is directly reported to the MN after the timer expires. In the MN termination node mode, the MN side control plane is configured with a fixed period to control the PDCP and RLC states respectively. You can configure the bearer and user level periodic events according to the configuration. In the SN termination bearer mode, the SN side configures a fixed period to control the PDCP and RLC states, and can carry out periodic events at the bearer and user level according to the configuration. Among them, the cycle range is based on the ue-InactiveTime specified in the agreement.

Event triggering refers to the internal decision of MN and SN after the timer expires. Only when the current state and the last maintenance state information are inconsistent, the event-driven trigger user activity notification is notified to MN.

The SN activity notification is controlled and reported by the UE inactive state information transmitted from the MN, and the SN side bearer inactive state information is reported. There are two possible scenarios:

Scenario (1): MN RLC and SN RLC report to the SN user according to the bearer level period or event. The inactive state is inactive. The SN combines the PDCP and RLC states with an activity notification message to the MN. The MN side determines the UE's inactive release strategy based on other remaining bearer RLC states and the SN to deliver information.

Scenario (2): MN RLC and SN RLC report to the SN user according to the bearer level period or event. The inactive state is re-activated. It means that the state of the SN cached user is inactive, the maintenance state is reversed, the SN carries the UE re-activated indication, and the MN needs to reactivate the SN side to activate the service bearer. The MN side decides the UE's inactive release strategy based on other remaining bearer RLC states, combined with SN delivery information.

Through the description of the above embodiments, those skilled in the art can clearly understand that the method according to the above embodiments can be implemented by means of software plus a necessary general hardware platform, and of course, it can also be implemented by hardware, but in many cases the former Better implementation. Based on such an understanding, the technical solution of the present disclosure can be embodied in the form of a software product in essence or part that contributes to the existing technology, and the computer software product is stored in a storage medium (such as ROM / RAM, magnetic disk, The CD-ROM includes several instructions to enable a terminal device (which may be a mobile phone, computer, server, or network device, etc.) to execute the methods described in the embodiments of the present disclosure.

Example 2

In this embodiment, a device for reporting status is also provided. The device is used to implement the above-mentioned embodiments and preferred implementation modes, and those that have already been described will not be repeated. As used below, the term "module" may implement a combination of software and / or hardware that performs predetermined functions. Although the devices described in the following embodiments are preferably implemented in software, implementation of hardware or a combination of software and hardware is also possible and conceived.

FIG. 11 is a structural block diagram of a device for reporting status according to an embodiment of the present disclosure. As shown in FIG. 11, the device includes:

The first receiving module 112 is configured to receive a first indication message from the master node MN, where the first indication message is used to carry at least the following information: inactivity timer information of the user terminal UE;

The reporting module 114 is configured to report the inactive state of the UE according to the first indication information.

Through the present disclosure, a first indication message from the master node MN is received, where the first indication message is used to carry at least the following information: inactivity timer information of the user terminal UE; report the inactivity of the UE according to the first indication information The active state adopts the above technical solution, which solves the problem that the inactive state before the bearer change cannot be continued in the dual connection scenario in the related art, thereby causing the problem that the timing is too long.

In the embodiment of the present disclosure, the inactivity timer information of the user terminal UE includes at least one of the following: remaining user inactivity time and user inactivity state maintenance time.

Example 3

An embodiment of the present disclosure also provides a message receiving method. FIG. 12 is a flowchart of a message receiving method according to an embodiment of the present disclosure. As shown in FIG. 12, the method includes the following steps:

Step S1202: Receive a second indication message from the secondary node SN, where the second indication message is used to carry at least the following information: inactivity timer information of the user terminal UE.

Through the present disclosure, a second indication message from the secondary node SN is received, where the second indication message is used to carry at least the following information: inactivity timer information of the user terminal UE; adopting the above technical solution, the related technology is solved In the dual connection scenario, the inactive state before the bearer change cannot be continued, which leads to the problem of excessively long timing.

In the embodiment of the present disclosure, the inactivity timer information of the user terminal UE includes at least one of the following: remaining user inactivity time and user inactivity state maintenance time.

In the embodiment of the present disclosure, before receiving the second indication message from the secondary node SN, the method further includes: triggering a bearer change and an SN change process.

In the embodiment of the present disclosure, after receiving the second indication message from the secondary node SN, the method further includes:

Inherit the remaining UE inactivity timer time through the MN, or set a new timer time through the MN, or modify the MN's current inactivity timer time.

In the embodiment of the present disclosure, the second indication information includes at least one of the following: SN addition request confirmation message, SN modification request confirmation message triggered by SN, SN modification request message triggered by SN, SN modification request message, SN Release confirmation message.

Example 4

In this embodiment, a message receiving device is also provided. The device is used to implement the above-mentioned embodiments and preferred implementation modes, and those that have already been described will not be repeated. As used below, the term "module" may implement a combination of software and / or hardware that performs predetermined functions. Although the devices described in the following embodiments are preferably implemented in software, implementation of hardware or a combination of software and hardware is also possible and conceived.

13 is a structural block diagram of a message receiving apparatus according to an embodiment of the present disclosure. As shown in FIG. 13, the apparatus includes:

The second receiving module 130 is configured to receive a second indication message from the secondary node SN, where the second indication message is used to carry at least the following information: inactivity timer information of the user terminal UE.

Through the present disclosure, a second indication message from the secondary node SN is received, where the second indication message is used to carry at least the following information: inactivity timer information of the user terminal UE; adopting the above technical solution, the related technology is solved In the dual connection scenario, the inactive state before the bearer change cannot be continued, which leads to the problem of excessively long timing.

In the embodiment of the present disclosure, the inactivity timer information of the user terminal UE includes at least one of the following: remaining user inactivity time and user inactivity state maintenance time.

The technical solutions of the embodiments of the present disclosure provide a precise control of the inactivity state of the UE in dual connectivity, and the new bearer type inherits the user inactivity state indication of the original bearer type. Without influencing the standard interface message structure, a user inactive state cell delivery is proposed, which can better continue the UE's business behavior, reduce user state transition time, and reduce user power consumption. At the same time, it saves wireless air interface resources and ensures the effective use of system resources.

It should be noted that the above modules can be implemented by software or hardware, and the latter can be implemented by the following methods, but not limited to this: the above modules are all located in the same processor; or, the above modules can be combined in any combination The forms are located in different processors.

In the following, the above status reporting process will be described in conjunction with the interaction flow between MN and SN.

FIG. 5 is a flowchart of an SN addition process according to an example of the present disclosure. As shown in FIG. 5, it includes:

1). The SN addition process triggered by the MN, the MN carries the remaining UE inactivity time T1 or the user inactivity state maintenance time T2 in the SN ADD request message message, which is carried according to the service bearer level or UE level.

2). The SN is replying with a response.

FIG. 6 is a flowchart of an MN-triggered SN modification process according to an example of the present disclosure. As shown in FIG. 6, it includes:

1). The SN modification process triggered by the MN, the MN carries the remaining UE inactivity time T1 or the user inactivity state maintenance time T2 in the SN modification request message, which is carried according to the user level or service bearer level.

2). The SN is replying with a response.

7 is a flowchart of an SN modification process triggered by an SN according to an example of the present disclosure. As shown in FIG. 7, it includes:

1) The SN modification process triggered by the SN. The MN carries the remaining UE inactivity time T1 or the user inactivity state maintenance time T2 in the SN ADD request request message, which is carried according to the user level or service bearer level.

2). The MN is replying with a response.

FIG. 8 is a flowchart of a MN triggered SN release process according to an example of the present disclosure. As shown in FIG. 8, it includes:

1). The SN release process triggered by the MN. The MN releases the SN release request message carrying the remaining UE inactivity for a fixed time T1 or user inactivity state maintenance time T2, which is carried according to the user level or service bearer level.

2). The SN is replying with a response.

FIG. 9 is a flowchart of an SN triggered SN release process according to an example of the present disclosure. As shown in FIG. 9, it includes:

1). SN release request triggered by SN.

2). The MN responds to the response, and the MN releases the response message in the SN carrying the remaining UE inactivity time T1 or user inactivity state maintenance time T2, which is carried according to the user level or service bearer level.

10 is a flowchart of an SN triggered SN change process according to an example of the present disclosure. As shown in FIG. 10, it includes:

1). SN triggered SN change request.

2). The MN responds to the response, and the MN changes the response message in the SN to carry the remaining UE inactivity time T1 or user inactivity state maintenance time T2, which is carried according to the user level or service bearer level.

It should be noted that the UE inactivity state information can also be appropriately set to MN-triggered SN modification, SN-triggered SN modification, SN deletion, and SN change. The related technical principles are the same as SN addition.

Using the above technical solution, a precise control, the new bearer type inherits the user inactivity status indication of the original bearer type. On the premise of not affecting the standard interface message structure, a kind of user inactive state cell transmission is proposed. The above technical solution of the embodiment of the present disclosure should not only be set as the existing EN-DC scenario, but also include the subsequent continuous evolution of MR-DC with 5GC, that is, NGEN-DC, NE-DC, and NR-DC scenarios.

As shown in Figure 16, in the MN Terminated scenario, the PDCP control anchor is in the MN. SN RLC needs periodic or event report user status notification to MN, MN combines MN RLC and PDCP to decide UE's subsequent behavior. The user status notification is reported based on the MN node transmitting user inactivity status period or event trigger.

As shown in Fig. 18, in the SN Terminated scenario, the PDCP control anchor is in the SN.

Method 1: MN RLC and SN RLC need to report the user status notification to SN PDCP. SN combines the SN's PDCP status information with periodic or event reporting user status notification to MN. MN combines other bearer MN RLC and PDCP to decide the UE's subsequent behavior.

Method 2: The MN maintains the RLC itself, the SN combines the SN's PDCP and RLC status information, reports the user status to the MN by reporting the period or event, and the MN combines other bearers MN RLC and PDCP to decide the UE's subsequent behavior.

Refer to Table 1 for the MN's processing flow according to the user bearer level.

Table 1

Refer to Table 2 for the processing flow of MN according to the bearer level

Table 2

In summary, through the technical solutions of the above embodiments, the MN based on the user inactivity status information transmitted by the SN, and combined with other remaining bearers on the MN side RLC bearer status unified decision release, after adding the SN inherits the MN user inactivity status information , And the SN takes effect within the timer range according to the UE level, and the SN maintains this timer in PDCP and RLC, MN, RLC and SN RLC report user inactivity status to SN PDCP, SN through internal decision through SN activity notification message Inform the MN that the MN will make unified decisions so that the wireless network can control the UE's inactive behavior more accurately. The DRB-level user inactivity information can also be transferred between MN and SN, the principle is the same as the UE level.

In the embodiment of the present disclosure, the message structure (taking SN addition as an example)

The UE inactivity timer can be set to the bearer level (DRB) or the user level (UE). MN and SN can flexibly configure corresponding timers according to the type of transfer bearer. Among them, ue-MrdcInactiveTime is a UE-level timer, and drb-InactiveTime1 and drb-InactiveTime2 are DRB-level timers. Other messages are delivered in a similar structure.

The above technical solutions are described below in conjunction with preferred embodiments, but are not intended to limit the technical solutions of the embodiments of the present disclosure.

Preferred embodiment 1. As shown in FIG. 14, MCG-> SCG bearer type change (using remaining inactive time)

Step 1. In the EN-DC scenario, the service starts with the establishment of MCG bearers, and delivers SN measurement control, triggering the SN addition process. Before the SN is added, the MN starts the user inactivity timing duration T1 according to the service type, for example, 10 minutes.

Step 2. The UE reports the B1 / B2 measurement report, and the MN triggers the addition of the SN.

Step 3. The SN add message establishes the SN terminated SCG bearer, triggers MCG-> SCG bearer change, and carries the remaining inactivity timer T2 (2 minutes), assuming that the UE inactivity state has been maintained on the MCG bearer for 8 minutes.

Step 4. The SN receives the add request message, establishes the relevant bearer, and inherits the service timer T2 (2 minutes).

Step 5-6. After the bearer is changed to the SCG bearer, the SN continues the remaining UE inactivity timer. According to the T2 time, the SN RLC counts the UE inactive state to the SN within the timer range. After the timer expires, the SN event triggers the UE inactive state to the MN. (The event is triggered when the user's inactive state is inconsistent with the previous one, and it is triggered only when a reverse transmission occurs).

-If the UE has been in an inactive state, after the T2 timer expires, it sends an SN activity notification to the MN, carrying the Inactive state.

-If the UE status reverses, send an SN activity notification to the MN immediately, carrying the UE re-actived status.

Steps 7-8. The MN needs to decide the follow-up behavior according to the MN RLC and PDCP, according to the UE or the bearer level, because the SN will only actively report the activity notification message, and there is no mechanism for deciding the UE behavior. In the case where the SN connection has always existed, it will always actively send an activity notification message until the SN is released. If the UE has been in the inactive state, the continuation event triggers the MN to send an SN activity notification, carrying the UE Inactive state. The MN decides whether to release the UE resources. If the MN combines the MN RLC and the MN PDCP of the remaining bearer to decide that the UE or the bearer also meets the release condition, it initiates the air interface resource release.

Preferred Embodiment 2. FIG. 15 is a flowchart of changing the bearer type of MN termination node-> SN termination node according to the preferred embodiment of the present disclosure, as shown in FIG. 15,

Step 1. In the EN-DC scenario, the service starts with the establishment of MCG bearers, and delivers SN measurement control, triggering the SN addition process. Before the SN is added, the MN starts the UE-InactiveTime T1 according to the service type, for example, 10 minutes.

Step 2. The UE reports the B1 / B2 measurement report, and the MN triggers the addition of the SN.

Step 3. The SN adds a message to establish the MN terminated bearer, and carries the remaining T2 (7 minutes), assuming that the UE inactivity timer has been maintained on the MCG bearer for 3 minutes.

Step 4. The SN receives the add request message, establishes the relevant bearer, and inherits the service timer T2 (7 minutes).

Steps 5-6. Due to resource configuration, MN triggers MN terminated-> SN terminated modification request (as shown in Figure 16), and carries UE inactivity timer T3 (2 minutes).

Step 7-8. After the bearer is changed to SN terminated, the SN continues the remaining UE inactivity timer. According to the T3 time, the SN counts the UE inactivity state within the timer range. After the timer expires, the event triggers the UE inactivity state to the MN. (The event is triggered when the user's inactive state is inconsistent with the previous one, and it is triggered only when a reverse transmission occurs)

-If the UE has been in the inactive state, after the T3 timer expires, it sends an SN activity notification to the MN, carrying the Inactive state.

-If the UE status reverses, send an SN activity notification to the MN immediately, carrying the UE re-actived status.

Steps 9-10. The MN needs to decide the follow-up behavior according to the MN, RLC and PDCP, according to the UE or the bearer level. Since the SN will only actively report the activity notification message, there is no mechanism for deciding the UE behavior. In the case where the SN connection has always existed, it will always actively send an activity notification message until the SN is released. If the UE has been in the inactive state, the continuation event triggers the MN to send an SN activity notification, carrying the Inactive state. The MN decides whether to release the UE resources. If the MN combines the MN RLC and the MN PDCP to decide that the UE or bearer also meets the release conditions, it initiates the air interface resource release.

Preferred embodiment 3

FIG. 17 is a flowchart of changing the SN terminated bearer-> MN terminated bearer bearer type according to the preferred embodiment of the present disclosure, as shown in FIG. 17,

Step 1. In the EN-DC scenario, the service starts with the establishment of LTE bearers, and SN measurement control is issued, triggering the SN addition process. Before the SN is added, the MN starts ue-InactiveTime T1 according to the service type, for example, 60s.

Step 2. The UE reports the B1 / B2 measurement report, and the MN triggers the addition of the SN.

Step 3. The SN adds a message to establish the MN terminated bearer, and carries the user inactivity state maintenance time T2 (30s), assuming that the UE inactivity timer has been maintained on the MCG bearer for 30s.

Step 4. The SN receives the add request message and establishes the relevant bearer. The SN configures a new time T3 (40s) according to the service bearer type, and the effective timer T4 = T3-T2 = 10s. If T3 is less than T2, T4 takes the value 0.

Steps 5-6. Due to resource configuration, the SN triggers the SN terminated-> MN terminated modification request (as shown in Figure 18), and carries the UE inactivity timer T5 (6s).

Step 7-8. After the bearer is changed to MN terminated, the MN configures a new time T1 (60s) according to the service bearer type, and the effective timer T6 = T1-T5 = 55s. If T1 is less than T5, T6 takes the value 0. According to the T6 time, the SN counts the UE inactivity state within the timer range. After the timer expires, the event triggers the UE inactivity state to the MN. (The event is triggered when the user's inactive state is inconsistent with the previous one, and it is triggered only when a reverse transmission occurs)

-If the UE has been in the inactive state, after the T6 timer expires, it sends an SN activity notification to the MN, carrying the Inactive state.

-If the UE status reverses, send an SN activity notification to the MN immediately, carrying the UE re-actived status.

Steps 9-10. The MN needs to decide the follow-up behavior according to the MN RLC and PDCP, according to the UE or the bearer level, because the SN will only actively report the activity notification message, and there is no mechanism to decide the UE behavior. In the case where the SN connection has always existed, it will always actively send an activity notification message until the SN is released. If the UE has been in the inactive state, the event triggers to send an SN activity notification to the MN, carrying the Inactive state. The MN decides whether to release the UE resources. If the MN combines the MN RLC and the MN PDCP to decide that the UE or bearer also meets the release conditions, it initiates the air interface resource release.

Preferred embodiment 4

FIG. 19 is a time flow chart of SN changing user inactivity state according to a preferred embodiment of the present disclosure, as shown in FIG. 19,

Step 1. In the EN-DC scenario, the service starts with the establishment of MCG bearers, and delivers SN measurement control, triggering the SN addition process. Before the SN is added, the MN starts the user inactivity timing duration T1 according to the service type, for example, 5 minutes.

Step 2. The UE reports the B1 / B2 measurement report, and the MN triggers the SN addition. The SN addition message carries the UE inactivity time T2 (2 minutes), that is, the UE inactivity timer on the MCG bearer has been maintained for 2 minutes.

Step 3. Due to air interface measurement, the original SN1 cannot provide services and needs to be changed to the new SN2. MN releases SN1.

Step 4. In the process of adding a new SN2, the MN carries the UE inactivity for a fixed time T4 (1 minute). The SN sets the updated inactivity timer T4 = T3-T2 = 1 minute. If T3 is less than T2, then T4 takes the value Is 0. The MN determines the release state of the UE. According to the T4 time, the SN counts the UE inactivity state within the timer range. After the timer expires, the event triggers the UE inactivity state to the MN. (The event is triggered when the user's inactive state is inconsistent with the previous one, and it is triggered only when a reverse transmission occurs)

-If the UE has been in an inactive state, after the T4 timer expires, it sends an SN activity notification to the MN, carrying the Inactive state.

-If the UE status reverses, send an SN activity notification to the MN immediately, carrying the UE re-actived status.

Subsequent SN2 continues to inform the MN through the SN activity notification message event, and the MN combines the remaining bearer MN RLC and PDCP to decide the subsequent UE behavior.

Example 5

An embodiment of the present disclosure also provides a storage medium including a stored program, wherein the method described in any one of the above is executed when the above program runs.

Optionally, in this embodiment, the above storage medium may be set to store program code for performing the following steps:

S1. Receive a first indication message from the master node MN, where the first indication message is used to carry at least the following information: inactivity timer information of the user terminal UE;

S2. Report the inactivity state of the UE according to the first indication information.

Example 6

An embodiment of the present disclosure also provides a storage medium including a stored program, wherein the method described in any one of the above is executed when the above program runs.

Optionally, in this embodiment, the above storage medium may be set to store program code for performing the following steps:

S3. Receive a second indication message from the secondary node SN, where the second indication message is used to carry at least the following information: inactivity timer information of the user terminal UE.

Optionally, in this embodiment, the above storage medium may include, but is not limited to: a USB flash drive, a read-only memory (Read-Only Memory, ROM for short), a random access memory (Random Access Memory, RAM for short), Various media that can store program codes, such as removable hard disks, magnetic disks, or optical disks.

Optionally, for specific examples in this embodiment, reference may be made to the examples described in the foregoing embodiments and optional implementation manners, and details are not repeated in this embodiment.

Obviously, those skilled in the art should understand that the above-mentioned modules or steps of the present disclosure can be implemented by a general-purpose computing device, and they can be concentrated on a single computing device or distributed in a network composed of multiple computing devices Above, optionally, they can be implemented with program code executable by the computing device, so that they can be stored in the storage device to be executed by the computing device, and in some cases, can be in a different order than here The steps shown or described are performed, or they are made into individual integrated circuit modules respectively, or multiple modules or steps among them are made into a single integrated circuit module to achieve. In this way, the present disclosure is not limited to any specific combination of hardware and software.

The above are only preferred embodiments of the present disclosure, and are not intended to limit the present disclosure. For those skilled in the art, the present disclosure may have various modifications and changes. Any modifications, equivalent substitutions, improvements, etc. made within the principles of this disclosure shall be included in the scope of protection of this disclosure.

Claims (18)

A status reporting method, including: Receiving a first indication message from the master node MN, where the first indication message is set to carry at least the following information: inactivity timer information of the user terminal UE; Report the inactivity state of the UE according to the first indication information. The method according to claim 1, wherein the inactivity timer information of the user terminal UE includes at least one of the following: remaining user inactivity time T1, user inactivity state maintenance time T2. The method according to claim 1, wherein before receiving the first indication message from the master node MN, the method further comprises: Trigger a bearer change, where the bearer change includes: a bearer change between the primary cell group MCG and the secondary cell group SCG, a bearer change between the MCG and Split, a change between the SCG and Split bearer, an SN termination node and a MN termination node The combination of MCG, SCG and Split under the change. The method of claim 1, wherein the method further comprises: Through the X2 / Xn interface, the UE's inactivity timer information is transferred to the MN according to the user level or bearer level; The UE's inactivity timer information is passed to the MN in an explicit or implicit manner. The method according to claim 4, wherein the method further comprises: After receiving the user's inactivity related information through the SN, it continues to be transferred in the SN packet data aggregation protocol PDCP, or the SN radio link control RLC layer. The method according to claim 1, wherein reporting the inactivity state of the user terminal UE according to the first indication information includes: Determine the current inactivity timer information of the secondary node SN according to the first indication information; Report the inactivity state of the UE according to the current inactivity timer information. The method according to claim 2, wherein after receiving the first indication message from the master node MN, the method further comprises: Inherit the remaining UE inactivity timer time through the SN, or set a new timer time through the SN, or modify the SN's current inactivity timer time. The method according to any one of claims 1 to 7, wherein The first indication information includes at least one of the following: SN addition request message, MN triggers SN modification request message for SN modification, SN triggers SN modification request confirmation message, SN change request confirmation message, SN release request message. A status reporting device, including: The first receiving module is configured to receive a first indication message from the master node MN, where the first indication message is set to carry at least the following information: inactivity timer information of the user terminal UE; The reporting module is configured to report the inactive state of the UE according to the first indication information. The apparatus according to claim 9, wherein the inactivity timer information of the user terminal UE includes at least one of the following: remaining user inactivity time T1, user inactivity state maintenance time T2. A message receiving method, including: Receiving a second indication message from the secondary node SN, where the second indication message is set to carry at least the following information: inactivity timer information of the user terminal UE. The method according to claim 11, wherein the inactivity timer information of the user terminal UE includes at least one of the following: remaining user inactivity time and user inactivity state maintenance time. The method according to claim 11, wherein before receiving the second indication message from the secondary node SN, the method further comprises: Trigger a bearer change, where the bearer change includes: a bearer change between the primary cell group MCG and the secondary cell group SCG, a bearer change between the MCG and Split, a change between the SCG and Split bearer, an SN termination node and a MN termination node The combination of MCG, SCG and Split under the change. The method according to claim 11, wherein after receiving the second indication message from the secondary node SN, the method further comprises: Inherit the remaining UE inactivity timer time through the MN, or set a new timer time through the MN, or modify the MN's current inactivity timer time. A message receiving device, including: The second receiving module is configured to receive a second indication message from the secondary node SN, where the second indication message is used to carry at least the following information: inactivity timer information of the user terminal UE. The apparatus according to claim 15, wherein the inactivity timer information of the user terminal UE includes at least one of the following: remaining user inactivity time T1, user inactivity state maintenance time T2. A storage medium storing a computer program in the storage medium, wherein the computer program is configured to execute the method described in any one of claims 1 to 8 or any one of claims 11 to 14 when it is run. An electronic device includes a memory and a processor, a computer program is stored in the memory, the processor is configured to run the computer program to execute the claims 1 to 8, or any of claims 11 to 14 The method described in the item.

Images