CN112788689A

CN112788689A - System and method for enhanced session management in a NextGen mobile core network

Info

Publication number: CN112788689A
Application number: CN202110038397.3A
Authority: CN
Inventors: 克拉丽莎·玛奎赞; 安雪莉
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2017-02-01
Filing date: 2017-02-01
Publication date: 2021-05-11
Anticipated expiration: 2037-02-01
Also published as: EP3569033B1; US20200029252A1; EP4271114A3; WO2018141376A1; US11082894B2; EP4271114A2; CN110235510A; US20220022104A1; JP6898046B2; CN112788689B; CN110235510B; JP2020505864A; EP3569033A1

Abstract

The present invention relates to an enhanced session model capable of managing the configuration and use of a single packet data unit session, which is an association between a user equipment and a packet data network entity and which consists of multiple transport bearers between an access network and a core network. The core network comprises a session type management entity for controlling connectivity of the transport bearers, a plurality of user plane functional entities, a session type database and a control plane functional entity, wherein allocation of the transport bearers is exclusive allocation or shared allocation. The control plane functional entity may be functionally independent from the session type management entity, or may be extended based on the functionality of the session type management entity. The user equipment and the user plane function entity are respectively extended based on the functions of the user session type extension entity and the user plane session type extension entity, wherein the user session type extension entity and the user plane session type extension entity respectively comprise corresponding mapping tables specially used for distribution.

Description

System and method for enhanced session management in a NextGen mobile core network

Technical Field

The present invention relates to the design of mobile core network architecture for next generation systems, and more particularly to an architecture that supports the configuration and use of multiple transport bearers belonging to a single packet data unit session.

Background

According to the industry consensus, the fifth generation (5th generation, 5G) mobile technology will be standardized and deployed in 2020. In contrast to the fourth generation (4th generation, 4G) mobile technology, next generation networks are expected to support a variety of use cases in terms of performance attributes, such as ultra-reliable communication for mission critical services, electronic health, public safety, real-time vehicle control, connectivity between the haptic internet and drones, as follows: 3GPP TR22.891 "Feasibility Study by New Services and market Technology drivers (Feasibility Study on New Services and market technologies Enables)" 14 th edition and "5G white paper" released by the NGMN alliance 2015 at 2, 17. The support for such use cases can be realized only through a flexible network, so that the heterogeneous performance is realized, and the following references are made: "5G foreground-Key Capabilities to Unlock Digital Opportunities" (5G Prospects-Key Capabilities to Unlock Digital Opportunities) "published by NGMN alliance 2016, 7, month, 1.

For next generation mobile systems, it is expected that a wide variety of devices will be able to support a variety of new types of connections between various devices, such as smart phones, wearable devices, smart cars, electronic home appliances, and industrial devices. These devices are characterized by widely varying performance requirements. In addition, the need to integrate the communication services required by the industry vertical will also increase this need for diversification. This diverse demand will also necessitate that the network support and handle different mobility and session management models for these different requirements. In current Long Term Evolution (LTE) systems, there is only one session model, namely an Evolved Packet System (EPS) bearer applied to all types of devices and services. There is also no diversity in mobility or session management, as the procedures for maintaining a connection for a certain device (e.g. active or idle mobility management procedures) must perform the same changes at the Radio Access Network (RAN) and the Core Network (CN) so that this kind of session connection is maintained regardless of the type of device. Thus, device traffic from enhanced mobile broadband (eMBB) use cases and ultra-reliable low latency communication (uRLLC) use cases will be handled in the same way as a single EPS bearer model in current Evolved Packet Core (EPC). For example, mobility management for both types of devices will be implemented in three steps. In the first step, Handover (HO) preparation is performed, which has a high risk of packet loss and a high possibility of HO failure. Second, HO is performed. Third, HO is complete. This may result in packet loss and may increase communication delay. Services without strict transmission requirements (e.g., 10ms delay and 99.9999% reliability), such as those in eMBB use cases, can tolerate packet loss that may occur during HO management. However, without a session and mobility management model and flow that can provide its requirements, services in the urrllc use case, such as services, will not operate properly.

In mobile core networks, multiple connections have been studied. For example, the multiplex transmission control protocol (MPTCP) described in RFC 6897 is based on the following concept: a Transmission Control Protocol (TCP) connection is divided into a plurality of sub-streams using different Internet Protocol (IP) addresses or interfaces. However, this solution cannot be used to handle multiple transport bearers as a single Packet Data Unit (PDU), because MPTCP works at the transport layer of the application once the interfaces are connected and available, and therefore does not handle the session between the RAN and the core network. LTE dual connectivity involves two evolved base stations (enbs) providing radio resources to a given User Equipment (UE) with an active radio bearer, while there is a single S1-MME termination point for the UE between a Mobility Management Entity (MME) and an evolved universal terrestrial radio access network (E-UTRAN), referred to as follows: 3GPP TS 23.401 V13.2.0' enhanced General Packet Radio Service (GPRS) for Evolved Universal Terrestrial Radio Access Network (E-UTRAN) Access. Of the two enbs, one is the master eNB and the other is the secondary eNB. Therefore, for the UE, the cells in which the two base stations are located are the primary cell and the secondary cell, respectively, and still only one transport bearer in the CN is allocated to the primary cell and the secondary cell.

Disclosure of Invention

It is therefore an object of the present invention to provide an enhanced session model that enables the management of the configuration and use of a single packet data unit session consisting of multiple transport bearers between an access network and a core network of a mobile communications network.

This object is achieved by the features of the independent claims. Further embodiments of the invention are apparent from the dependent claims, the description and the drawings.

According to a first aspect, the present invention relates to a Core Network (CN) of a mobile communication network for managing a plurality of transport bearers. The CN comprises a Session Type Manager (STM) entity for controlling connectivity of the plurality of transport bearers between AN Access Network (AN) of the mobile communication network and the CN based on the selective allocation of the plurality of transport bearers; each transport bearer is defined as a logical connection between two entities sending data traffic; the allocating of the plurality of transport bearers is performed for at least one transport bearer of the CN and at least two transport bearers of the same AN on at least two different Access Points (APs) respectively located at the AN, each transport bearer belonging to a single Packet Data Unit (PDU) session, the PDU session being defined as AN association between a User Equipment (UE) and a Packet Data Network (PDN) entity. AN Enhanced Session Model (ESM) is defined as a model in which the UE has the at least two transport bearers of the same AN and the at least one transport bearer of the Core Network (CN), wherein the at least two transport bearers of the AN and the at least one transport bearer of the CN all belong to the single PDU session.

In a first implementation form of the CN according to the first aspect, the allocation between the at least two transport bearers of the AN and the at least one transport bearer of the CN is selected by the STM entity as AN exclusive allocation, where each transport bearer of the AN is connected to each respective transport bearer of the CN separately, or as a shared allocation, where the at least two transport bearers of the AN are connected together to a single transport bearer of the CN.

In a second implementation form of the CN according to the first aspect as such or the first implementation form of the first aspect, the CN comprises: a plurality of User Plane Function (UPF) entities defined as Network Functions (NFs) for processing user plane traffic to provide some network services; and a Control Plane Function (CPF) entity defined as a Network Function (NF) for performing a control plane function for the UE connected to the mobile communication network in order to exchange any data traffic with the PDN entity through the AN and the CN.

In a third implementation form of the CN according to the second implementation form of the first aspect, the CPF entity is an entity that is functionally independent of the STM entity or an entity that is extended based on the functionality of the STM entity; for receiving a session configuration request; for communicating with the STM entity to request session configuration information on the enhanced session when the CPF entity is a function independent entity or for determining session configuration information on the enhanced session when the CPF entity is extended based on a function of the STM entity; and means for sending information to the UPF entity and the UE on how to establish or change the session of the UE based on the session configuration information. The session configuration request relates to a session or service request from the UE or to a need to change an existing session by modifying or replacing the existing session, the need to change the existing session being identified by a Session Type Database (STDB) of the CPF entity, the STM entity or the CN. The session configuration information relates to a mode of operation of the session of the UE to be established, the mode of operation being selected by the STM entity as either a preemption mode or a synchronization mode or a reliability mode. The preemption mode involves resource reservation for the session of the UE to be established in the plurality of transport bearers between the AN and the CN; the synchronization mode involves simultaneous use of a selected transport bearer of the plurality of transport bearers between the AN and the CN; and the reliable mode involves transmission redundancy of data traffic of the selected one of the plurality of transport bearers between the AN and the CN.

In a fourth implementation form of the CN according to the third implementation form of the first aspect, when the CPF entity is an entity functionally independent of the STM entity, or is based on a functional extension of the STM entity, the STM entity is configured to: interacting with the STDB as a response to the session configuration information request to retrieve information of a session type to be used by the UE; identifying entities to configure from among UPF entities of the CN and APs of the AN to support the plurality of transport bearers associated with data traffic of the UE once the enhanced session is established based on the retrieved information of the session type; and determining session configuration information on the enhanced session and transmitting the session configuration information on the enhanced session to the CPF entity.

According to the fourth implementation manner of the first aspect, in a fifth implementation manner of the CN, the UE is extended based on a function of a user equipment session type extension (UE-STe) entity. The UE-STe entity is configured to establish a radio transport bearer with the AP having the same technology, to receive the session configuration information and the session type to be used by the UE from the CPF entity, and to determine how to transmit Uplink (UL) data traffic from the UE and receive Downlink (DL) data traffic toward the UE using the transport bearer of the AN.

In a sixth implementation form of the CN according to the fifth implementation form of the first aspect, the UE-STe entity comprises a mapping table dedicated to allocating the plurality of transport bearers at AN interface between the UE and the AN. The mapping table within the UE-STe entity includes a plurality of fields, one of which is a field regarding identification of a session used by the UE (session ID), one of which is a field regarding type of the identified session (session type), one of which is a field regarding operation mode of the identified session when the type of the identified session is an enhanced session (operation mode), and one of which is a field regarding identification of an AP associated with the identified session (AP ID).

According to the sixth implementation manner of the first aspect, in a seventh implementation manner of the CN, each UPF entity is extended based on a function of a corresponding user plane session type extension (UP-STe) entity. The UP-STe is configured to receive, from the CPF entity, information on a session type to be used by the UE and the session configuration information, and to determine how to transmit UL data traffic from the UE and DL data traffic toward the UE based on all the received information.

In AN eighth implementation form of the CN according to the seventh implementation form of the first aspect, each UP-STe entity comprises a respective mapping table dedicated to allocating the plurality of transport bearers at AN interface between the AN and the CN and inside the CN. Each mapping table within each UP-STe entity includes a plurality of fields, one being a field (session ID) regarding identification of a session used by the UE, one being a field (session type) regarding a type of the identified session, one being a field (operation mode) regarding an operation mode of the identified session when the type of the identified session is an enhanced session, and one being a field (UE ID) regarding identification of the UE associated with the identified session.

In a ninth implementation form of the CN according to the eighth implementation form of the first aspect, the UE-STe entity and the UP-STe entity are configured by the STM entity in the preemption mode, so as to use one set of transport bearers (primary set) for transmission of the UL and DL data traffic, while reserving another set of transport bearers (secondary set) for possible communication with the UE.

In a tenth implementation form of the CN according to the eighth implementation form of the first aspect, the UE-STe entity and the UP-STe entity are configured by the STM entity in the synchronization mode with respective different policies for selecting the plurality of transport bearers to be used simultaneously between the AN and the CN, wherein the UE-STe and UP-STe entities use respective default policies for all enhancement sessions or select one of the available policies for each enhancement session.

In AN eleventh implementation form of the CN according to the tenth implementation form of the first aspect, the policy applied at the UP-STe entity is a static policy or a full decision policy, and the policy applied at the UE-STe entity is a round robin scheduling or a conditional analysis of the AN.

In a twelfth implementation form of the CN according to the eighth implementation form of the first aspect, the UE-STe entity and the UP-STe entity are configured by the STM entity in the reliable mode to replicate the UL and DL data traffic.

The above object is also achieved according to a second aspect.

According to the second aspect, the present invention relates to a Session Type Manager (STM) entity of a Core Network (CN) of a mobile communication network according to the first aspect or any of the implementation manners of the first aspect.

The above object is also achieved according to the third aspect.

According to the third aspect, the present invention relates to a Control Plane Function (CPF) entity of a Core Network (CN) of a mobile communication network according to the first aspect or any of the implementation manners of the first aspect.

The above object is also achieved according to a fourth aspect.

According to a fourth aspect, the present invention relates to a User Plane Function (UPF) entity of a Core Network (CN) of a mobile communication network according to the first aspect or any one of the implementation manners of the first aspect.

The above object is also achieved according to a fifth aspect.

According to a fifth aspect, the present invention relates to a Session Type Database (STDB) of a Core Network (CN) of a mobile communication network according to the first aspect or any of the implementation manners of the first aspect.

The above object is also achieved according to a sixth aspect.

According to a sixth aspect, the present invention relates to a mobile communication network, including a Core Network (CN) according to the first aspect or any one of the implementation manners of the first aspect, AN Access Network (AN) according to the first aspect, a User Equipment (UE) according to the first aspect, and a Packet Data Network (PDN) entity according to the first aspect, where the UE and the PDN entity communicate with each other through the AN and the CN.

The above object is also achieved according to a seventh aspect.

According to the seventh aspect, the present invention relates to a method for managing a plurality of transport bearers within a mobile communication network, said mobile communication network being divided into AN Access Network (AN) and a Core Network (CN). The method comprises the following steps: controlling connectivity of the plurality of transport bearers between the AN and the CN based on the selective allocation of the plurality of transport bearers at a Session Type Manager (STM) entity. Each transport bearer is defined as a logical connection between two entities sending data traffic. The allocating of the plurality of transport bearers is performed for at least one transport bearer of the CN and at least two transport bearers of the same AN on at least two different Access Points (APs) respectively located at the AN, each transport bearer belonging to a single Packet Data Unit (PDU) session, the PDU session being defined as AN association between a User Equipment (UE) and a Packet Data Network (PDN) entity. AN Enhanced Session Model (ESM) is defined as a model in which the UE has the at least two transport bearers of the same AN and the at least one transport bearer of the Core Network (CN), wherein the at least two transport bearers of the AN and the at least one transport bearer of the CN all belong to the single PDU session.

In a first implementation form of the method according to the seventh aspect, the step of controlling connectivity of the plurality of transport bearers between the AN and the CN comprises the steps of: receiving a session configuration request at a Control Plane Function (CPF) entity, the session configuration request relating to establishment of a session from the UE connected to the mobile communication network for exchanging any uplink, UL, and downlink, DL, data traffic with the PDN entity through the AN and the CN, or relating to a need to modify AN existing session by modifying or replacing the existing session, the need being identified by the CPF entity, the STM entity, or a Session Type Database (STDB) interacting with the STM entity; determining, at the STM entity, session configuration information relating to establishment of the enhanced session; receiving the session configuration information at the CPF entity; deploying, from the CPF entity to the User Plane Function (UPF) entity of the CN, the AP of the AN, and the UE, the session configuration information, all for supporting the plurality of transport bearers associated with the data traffic of the UE for the enhanced session; and reserving resources of the plurality of transport bearers between the AN and the CN for the enhanced session based on the deployed session configuration information.

In a second implementation form of the method according to the first implementation form of the seventh aspect, the step of determining the session configuration information includes the following steps: defining, at the STM entity, an allocation of the plurality of transport bearers supported by the identified UPF entity and the AP.

In a third implementation of the method according to the second implementation of the seventh aspect, the allocating of the plurality of transport bearers is performed for at least two transport bearers of the AN and at least one transport bearer of the CN, wherein the at least two transport bearers of the AN and the at least one transport bearer of the CN all belong to the single PDU.

In a fourth implementation form of the method according to the third implementation form of the seventh aspect, the step of defining the allocation of the plurality of transport bearers comprises the steps of: selecting AN exclusive allocation, wherein each transport bearer of the AN is individually connected to each corresponding transport bearer of the CN, or selecting a shared allocation, wherein transport bearers of the AN are connected together to a single transport bearer of the CN.

In a fifth implementation manner of the method according to any one of the second to fourth implementation manners of the seventh aspect, the step of determining the session configuration information further includes the steps of: selecting, at the STM entity, AN operating mode of the UE from a preemption mode, a synchronization mode, and a reliable mode, wherein the preemption mode relates to resource reservation in the plurality of transport bearers between the AN and the CN, the synchronization mode relates to simultaneous use of a selected transport bearer in the plurality of transport bearers between the AN and the CN, and the reliable mode relates to redundancy of the data traffic.

In a sixth implementation of the method according to the fifth implementation of the seventh aspect, the need to modify an existing session by modifying the existing session is caused by a Handover (HO), which is triggered when the UE is in the preemption mode, for switching from a primary transport bearer to a secondary transport bearer, wherein the primary transport bearer is used for transmission of UL and DL data traffic and the secondary transport bearer is reserved for possible communication with the UE; the HO is triggered when the UE is in the synchronized mode or the reliable mode to allow the UE to connect to APs associated with sessions other than the existing enhanced session.

In a seventh implementation form of the method according to the sixth implementation form of the seventh aspect, the UE is based on a function extension of a user session type extension (UE-STe) entity. The UE-STe entity comprises a mapping table dedicated to allocating the plurality of transport bearers at AN interface between the UE and the AN, and is configured to: generating a UL data packet to be sent to the PDN entity; querying the mapping table to determine which session the UL data packet is associated with; selecting a unique transport bearer that can connect the UE and the PDN entity if the determined session is a session other than the enhanced session, sending the UL data packet to the PDN entity; determining whether the operating mode is the preemption mode, the synchronization mode, or the reliable mode if the determined session is the enhancement session; if the operation mode is the preemption mode, selecting the main transmission bearer and sending the UL data packet to the PDN entity; determining which policy should be employed if the mode of operation is the synchronous mode, to select a transport bearer based on the employed policy, to send the UL data packet to the PDN entity; determining all transport bearers associated with the enhanced session to copy the UL data packet to the determined all transport bearers, sending the UL data packet to the PDN entity, if the mode of operation is the reliable mode.

According to the seventh implementation manner of the seventh aspect, in an eighth implementation manner of the method, each UPF entity is extended based on a function of a corresponding user plane session type extension (UP-STe) entity. Each UP-STe entity comprises a respective mapping table dedicated to the allocation of the plurality of transport bearers at the interface between the AN and the CN and inside the CN, and is configured to: receiving a UL data packet from the UE in case of a UL data packet or a DL data packet from the PDN entity in case of a DL data packet; query its mapping table to determine which session the UL or DL data packet is associated with; selecting a unique transport bearer that can connect the UE and the PDN entity if the determined session is a session other than the enhanced session, the DL data packet being sent to the UE in case of a DL data packet or the UL data packet being sent to the PDN entity in case of a UL data packet; determining whether the operating mode is the preemption mode, the synchronization mode, or the reliable mode if the determined session is the enhancement session; if the operating mode is the preemption mode, selecting the primary transport bearer, sending a DL data packet to the UE in the case of a DL data packet or sending a UL data packet to the PDN entity in the case of a UL data packet; if the mode of operation is the synchronous mode, determining which policy other than the policy employed at the UE-STe entity should be employed to select a transport bearer based on the employed policy, the DL data packet being sent to the UE in the case of a DL data packet or the UL data packet being sent to the PDN entity in the case of a UL data packet; determining all transport bearers associated with the enhanced session to copy the UL or DL data packets to the determined all transport bearers if the mode of operation is the reliable mode, the DL data packets being sent to the UE in case of DL data packets or the UL data packets being sent to the PDN entity in case of UL data packets.

In AN eleventh implementation of the method according to the seventh or eighth implementation of the seventh aspect, the policy employed at the UP-STe entity is a static policy or a full decision policy, and the policy employed at the UE-STe entity is a round robin scheduling or a conditional analysis of the AN.

The above object is also achieved according to an eighth aspect.

According to an eighth aspect, the invention relates to a computer program comprising program code means for performing the method according to the fourth aspect or the first implementation form of the fourth aspect when said computer program is executed on a computer. Thus, the method can be performed in an automated and repeatable manner.

The computer program may be executed by the apparatus described above.

More specifically, it should be noted that the above-described means may be implemented on the basis of discrete hardware circuits having discrete hardware components, on the basis of an integrated chip or chip module means, or on the basis of a signal processing device or chip controlled by a software routine or program stored in a memory, written on a computer-readable medium or downloaded from a network, such as the internet.

It shall also be understood that preferred embodiments of the invention may also be any combination of the dependent claims or the above described embodiments with the respective independent claims.

These and other aspects of the invention are apparent from and will be elucidated with reference to the embodiments described hereinafter.

Drawings

In the following detailed description of the present disclosure, the invention will be explained in more detail in connection with exemplary embodiments shown in the drawings, in which:

fig. 1 shows different organization structure types (numbers (a) to (c)) of a single Packet Data Unit (PDU) session between AN Access Network (AN) and a Core Network (CN) of a mobile communication network in AN Enhanced Session Model (ESM), according to AN embodiment of the present invention;

fig. 2 shows different entities and interfaces in the CN of a mobile communication network within an ESM according to an embodiment of the invention in two cases: (a) the method comprises the following steps The CPF entity is functionally independent of the STM entity; and (b): the CPF entity is expanded based on the function of the STM entity;

fig. 3 shows a session configuration flow of ESM according to an embodiment of the present invention, which is triggered by a device;

fig. 4 shows a session configuration flow of ESM according to an embodiment of the present invention, which is triggered by a network;

fig. 5 illustrates two possible allocations of multiple transport bearers within an ESM according to an embodiment of the present invention: (a) the method comprises the following steps Exclusive allocation; and (b): sharing and distributing;

FIG. 6 illustrates three exemplary mapping tables for a UE-STe entity in a UE with an exclusive allocation of multiple transport bearers within an ESM with respective UP-STe entities within UPF1 and UPF2, in accordance with embodiments of the present invention;

FIG. 7 illustrates three exemplary mapping tables for a UE-STe entity in a UE with respective UP-STe entities in UPF1 and UPF2 in the case of shared allocation of multiple transport bearers within an ESM in accordance with an embodiment of the present invention;

fig. 8 illustrates the use of two sets of multiple transport bearers (B1 and B2) in preemption mode in the exemplary case of exclusive allocation, in accordance with an embodiment of the present invention, wherein: (a) the method comprises the following steps B1 and B2 correspond to the primary transport bearer set and the secondary transport bearer set, respectively, where the primary transport bearer is used; and (b): b1 and B2 correspond to the secondary transport bearer set and the primary transport bearer set, respectively, where the secondary transport bearer is used;

FIG. 9 illustrates the use of multiple transport bearers in synchronous mode in an exemplary case of exclusive allocation, according to an embodiment of the present invention;

FIG. 10 illustrates the use of multiple transport bearers in a reliable mode in an exemplary case of exclusive allocation, according to an embodiment of the invention;

fig. 11 is a flowchart illustrating processing steps of a UE-STe entity based on a UE operation mode according to an embodiment of the present invention;

fig. 12 is a flowchart illustrating processing steps of an UP-STe entity based on a UE operation mode according to an embodiment of the present invention;

FIG. 13 illustrates a UE-triggered HO procedure between multiple APs, all associated with the same ESM and UE-STe entity, in accordance with an embodiment of the present invention;

FIG. 14 shows a UE-triggered HO procedure between multiple APs, not all associated with the same ESM and UE-STe entity, in accordance with an embodiment of the present invention; and

fig. 15 shows several different implementations of the present invention in LTE architecture (numbers (a) to (c)).

The same reference numerals are used to denote the same or at least functionally equivalent features.

Detailed Description

Fig. 1 shows different organization types (numbers (a) to (c)) of a single Packet Data Unit (PDU) session between AN Access Network (AN) and a Core Network (CN) of a mobile communication network within AN Enhanced Session Model (ESM) according to AN embodiment of the present invention.

A single PDU session may be defined as AN association between a User Equipment (UE) and a Packet Data Network (PDN) entity, and AN ESM may be defined as a model in which the UE has at least two transport bearers of the same AN and at least one transport bearer of a CN, wherein the at least two transport bearers of the AN and the at least one transport bearer of the CN all belong to the single PDU session and are defined as logical connections between respective pairs of respective entities sending data traffic.

Thus, fig. 1 shows different configurations connecting multiple bearers to each other within the proposed ESM.

Fig. 1(a) depicts two transport bearers of AN over two access points (AP1 and AP2) that intersect at a first user plane functional entity (UPF1) of the CN. In this configuration of the proposed ESM, the number of transport bearers of the CN between the UPF1 and the second user plane functional entity (UPF2) corresponds to the number of transport bearers of the AN, so there are two transport bearers in the CN between the UPF1 and the UPF 2. Thus, the proposed ESM consists of the following tuples: (UE, AP1), (AP1, UPF1), (UE, AP2), (AP2, UPF1), (UPF1, UPF2), and (UPF2, PDN).

Fig. 1(b) depicts two transport bearers of AN on two access points (AP1 and AP2) that intersect at the UPF1 of the CN. In this configuration of the proposed ESM, only one transport bearer of the CN between UPF1 and UPF2 is responsible for sending traffic from both transport bearers of the AN. Thus, the proposed ESM consists of the following tuples: (UE, AP1), (AP1, UPF1), (UE, AP2), (AP2, UPF1), (UPF1_ a, UPF2), (UPF1_ b, UPF2), and (UPF2, PDN).

Fig. 1(c) depicts two transport bearers of AN on two access points (AP1 and AP2) that intersect at a third user plane functional entity (UPF3) of the CN, except UPF1 and UPF 2. Thus, the proposed ESM consists of the following tuples: (UE, AP1), (AP1, UPF1), (UPF1, UPF3), (UE, AP2), (AP2, UPF2), (UPF2, UPF3), and (UPF3, PDN).

All of the above-mentioned UPF entities (UPF1, UPF2, UPF3) can be defined as Network Functions (NFs) in the CN for handling user plane traffic in order to provide some network services. An example of a UPF entity may be a mobility anchor function entity.

Fig. 2 shows different entities and interfaces in the CN of a mobile communication network within an ESM according to an embodiment of the invention in two cases: (a) the method comprises the following steps The CPF entity is functionally independent of the STM entity: and (b): the CPF entity is extended based on the function of the STM entity. In the following, the term "CPF entity" refers to a CPF entity that is based on the functional extension of an STM entity or a CPF entity that is functionally independent of an STM entity, unless otherwise specified, depending on the context of the present invention.

These different entities and interfaces enable a mobile communication network comprising UE, AN, CN and PDN entities to support the configuration and use of the proposed ESM.

As can be seen from fig. 2(a), these entities in the CN include a Session Type Database (STDB), UPF entities (only one UPF entity is depicted for clarity), STM entities and CPF entities functionally independent of the STM entities.

As can be seen from fig. 2(b), these entities in the CN include a Session Type Database (STDB), UPF entities (only one UPF entity is drawn for clarity) and CPF entities extended based on the functionality of the STM entity (hereinafter also referred to as "extended CPF entities").

The CPF entity may be defined as AN NF in the CN for performing control plane functions for UEs connected to the mobile communication network in order to exchange any data traffic with the PDN entity through the AN and CN.

The STM entity may be defined as a logical network entity for controlling the connectivity of multiple transport bearers between AN and CN when using the proposed ESM.

To enable connectivity for UE traffic, the session type of the UE may be a session model used in current 4G systems, under which the UE is connected to only one AP using the same technology at a time, or the session type of the UE may be the proposed ESM, under which the UE is connected to multiple APs using the same technology at a time. The STM entity (see fig. 2(a)) or the functionality of the STM entity (see fig. 2(b)) is used whenever a session of a UE needs to be established in response to a session or service request from the UE, or whenever an existing session needs to be modified by modifying or replacing an existing session of the UE.

Referring to fig. 2(a), all steps are represented by respective circles around the numbers "1" to "6", and the CPF entity (functionally independent from the STM entity) receives a session configuration request from the UE over an access network session interface (ANs-If), which may be related to a session or service request, or to the need to modify an existing session by modifying or replacing it (step 1). The STM entity is actually triggered when the CPF entity (functionally independent from the STM entity) connects to the STM entity over a control network session type interface (CNs-If) to request which session type should be used for a given UE session setup or change request (step 2). Then, the STM entity interacts with the STDB through a session description interface (SD-If) to retrieve association information between the UE and a session type to be configured by the UE (step 3). When selecting ESM as the UE session type, the STM entity is also used to determine a number of AP and UPF entities to be configured in the User Plane (UP) in order to support a number of transport bearers of AN and CN associated with data traffic exchanged between the UE and the PDN entity for a given ESM establishment or ESM reconfiguration (step 4). After the STM entity has defined the session configuration information, this information will be propagated from the STM entity to the CPF entity (functionally independent of the STM entity) via the CNs-If (step 4'). Then, based on the information received from the STM entity, the CPF entity (functionally independent from the STM entity) sends the configuration defined by the STM entity to each UPF entity, and more specifically, to each user plane session type extension (UP-STe) entity indicated in the information through a session operation configuration interface (SOC-If) (step 5). In addition, the configuration of the ESM defined by the STM entity is also sent to the UE, and more particularly, to a user session type extension (UE-Ste) entity as shown in fig. 2 through ANs-If, so that the UE can also send and receive data traffic of the UE through an available transport bearer (step 1'). After the session is successfully established, Uplink (UL) data traffic from the UE and Downlink (DL) data traffic towards the UE are transmitted through the established session (step 6).

Referring to fig. 2(b), all steps are represented by respective circles around the numbers "1" to "6", and the CPF entity, which is based on the functional extension of the STM entity, receives a session configuration request from the UE through an access network session interface (ANs-If), which may be related to a session or service request, or a need to change an existing session by modifying or replacing the existing session (step 1). Then, the extended CPF entity interacts with the STDB through a session description interface (SD-If) so as to retrieve association information between the UE and a session type to be configured by the UE (step 2). When selecting ESM as the UE session type, the extended CPF entity is also used to determine a number of AP and UPF entities to be configured in the User Plane (UP) in order to support a number of transport bearers of AN and CN associated with data traffic exchanged between the UE and the PDN entity for a given ESM establishment or ESM reconfiguration (step 3). Then, based on the session configuration information defined by the extended CPF entity itself, the extended CPF entity sends the configuration to each UPF entity through a session operation configuration interface (SOC-If), and more specifically, to each user plane session type extension (UP-STe) entity as shown in fig. 2 (step 4). In addition, the configuration of the ESM defined by the extended CPF entity is also sent to the UE, and more specifically, sent to a user session type extension (UE-Ste) entity indicated in the configuration through an access network session interface (ANs-If), so that the UE can also send and receive data traffic of the UE through an available transport bearer (step 1'). After the session is successfully established, Uplink (UL) data traffic from the UE and Downlink (DL) data traffic towards the UE are transmitted through the established session (step 5).

It should be noted that when the CPF entity is functionally independent of the STM entity, the need to alter existing sessions can be identified at the CPF entity, STM or STDB. And when the CPF entity is extended based on the function of the STM entity, a need to change an existing session can be identified at the extended CPF entity or the STDB.

Each UPF entity in the CN is extended based on the function of the corresponding UP-STe entity, respectively, the UP-STe entity is configured to receive information about a session type to be used by the UE and session configuration information about an operation mode of a session of the UE to be established from the CPF entity through the SOC-If, and the UP-STe entity is further configured to determine how to transmit UL data traffic from the UE and DL data traffic towards the UE based on all the received information.

The UE is extended based on the function of a UE-STe entity for establishing a radio transport bearer with AN AP having the same technology, receiving a session type to be used by the UE and session configuration information about AN operation mode of a session of the UE to be established from a CPF entity through AN ANs-If, and also for determining how to transmit UL data traffic from the UE and receive DL data traffic toward the UE using a transport bearer of AN.

The session configuration flow introduced in the description paragraphs referred to in fig. 2(a) and 2(b) will be described in more detail below.

In this regard, fig. 3 illustrates a session configuration flow of an ESM according to an embodiment of the present invention, which is triggered by a device.

As shown in fig. 3, when the UE sends a session (or service) request to the CPF entity, an initial action of session configuration is triggered (step 1). The CPF entity interacting with the STM entity then processes the session request (step 2). When the STM entity receives a request to determine which session should be used, the STM entity interacts with the STDB to query and retrieve information about which session to use for a given UE (step 2). In addition, the STM entity defines configuration parameters (e.g., the type of CN transport bearer to be used) for the operation of the ESM to be configured within the UP-STe entity (step 2). When the CPF entity receives all information from the STM entity on how the ESM should be established, the CPF entity triggers the reservation of resources in multiple transport bearers between the UE (i.e., UE-STe entity) and the selected AP in the AN, between the selected AP and the UPF entity, and between the UPF entities in the CN (i.e., UP-STe entity) (step 3). Finally, when all entities of the UP confirm the reservation of the resources of the requested ESM to the CPF entity, the requested session is considered to be established (step 4).

During the connection of the UE to the mobile communication network, the session type of the UE and the resources associated with the transport bearer may change. In this case, the session configuration flow of the ESM may be regarded as a session reconfiguration flow of the ESM.

In this regard, fig. 4 shows a session configuration procedure of ESM according to an embodiment of the present invention, which is triggered by a network.

Different situations may occur. In the first case, the UE may have a current 4G session model and the network may define that the ongoing UE session needs to be changed to ESM. In the second case, the UE may have some transmission bearers in the UE and the ESM, and may need to change the AN between APs. In a third case, the UE may have an ESM and may need to change some transport bearers of the CN between UPFs due to anchor point reselection, etc.

As shown in fig. 4, after the above-described situation occurs, it may be determined that a change needs to be made to the session (legacy session or ESM session) (step 1). The entities involved in the determination are CPF entities, STM entities or STDB. The CPF entity may, for example, determine a change in the UP anchor point. In addition, the STM entity may, for example, receive context information in order to optimize the UE's customer-perceived experience (QoE), and the stored information about the session types used by the UE may be altered in the STDB. However, it is always the STM entity that makes the change decision, which will be enforced in the session used by the UE. After determining the changes to be configured, the STM entity again interacts with the CPF entity so that changes can be positively notified and communicated to the entity of the UP (step 2). The CPF entity interacts with the UPF entity to perform a change at the UP-STe entity of the UPF entity related to the session of the UE (step 3). Although different scenarios for changes are mentioned above, this step of the flow (step 3) is performed in all these scenarios, wherein the old resources are torn down and new resources are allocated for the change in order to implement the new or updated ESM. The interaction between the entities of the Control Plane (CP) and UP is completed, eventually re-establishing the ESM, while the STM entity has updated information about the changes that have been implemented in the session of the UE (step 4).

Connectivity of the plurality of transport bearers between the AN and the CN is controlled by the STM entity based on selective allocation of the plurality of transport bearers. The STM entity may select two allocations. The selective assignment is performed for at least one transport bearer of the CN and at least two transport bearers of the same AN on at least two different Access Points (APs) respectively located at the AN, each transport bearer belonging to a single Packet Data Unit (PDU) session.

Fig. 5 illustrates the following two possible allocations of multiple transport bearers within an ESM, in accordance with an embodiment of the present invention: (a) the method comprises the following steps Exclusive allocation; and (b): and (4) sharing and allocating.

In fig. 5(a), the selected allocation is AN exclusive allocation, where each transport bearer of the AN is separately connected to each corresponding transport bearer of the CN. As shown, there is AN association between the transport bearer CN-CN-B1 (through UPF1 and UPF2 of CN) and the transport bearer AN-CN-B1 (through AP1 and AP2 of AN and UPF1 of CN). As shown, there is another association between the other two transport bearers CN-CN-Bn (through UPF1 and UPF2 of CN) and the transport bearer AN-CN-Bn (through AP2 of AN and UPF1 of CN). Thus, such use of multiple transport bearers of the CN may achieve load balancing of data traffic of the UE in the core network or guarantee higher reliability, and so on.

In fig. 5(b), the selected allocation is a shared allocation, where at least two transport bearers of the AN are connected together to a single transport bearer of the CN. In this case, the STM entity determines that the transport bearer of the CN may be simplified and that multiple transport bearers of the AN will share the same transport bearer of the CN. As shown, both the transport bearer AN-CN-B1 (through AP1 and AP2 of the AN and UPF1 of the CN) and the transport bearer AN-CN-Bn (through AP2 of the AN and UPF1 of the CN) are associated with a single transport bearer CN-CN-B1 (through UPF1 and UPF 2). By indicating that the resources between the UPF entities are limited, the STM entities can be prompted to make decisions that share the same transport bearer of the CN.

As shown in fig. 5(a) and 5(B), there is also AN association between the Radio Access Network (RAN) transport bearer RAN-B1 (through the UE and the AP1 of the AN) and the transport bearer AN-CN-B1 (through the AP1 and AP2 of the AN and the UPF1 of the CN), and another association between the RAN transport bearer RAN-Bn (through the UE and the AP1 and AP2 of the AP) and the transport bearer AN-CN-Bn (through the AP2 of the AN and the UPF1 of the CN).

Further, the UE-STe entities include a mapping table dedicated to allocating a plurality of transport bearers at AN interface between the UE and the AN, and each UP-STe entity includes a respective mapping table dedicated to allocating a plurality of transport bearers at the interface between the AN and the CN and inside the CN. Thus, the allocation of multiple transport bearers between the AN and the CN within the ESM may be maintained.

The mapping table within the UE-STe entity and each UP-STe entity shares a number of fields, including:

-a field denoted "session ID" relating to the identity of the session used by the UE;

-a field denoted "PDN ID" relating to the identification of the PDN associated with the use of a session ID;

-a field denoted "UE UL bearer ID" relating to an identification of an allocation or mapping of data traffic to be sent from the UE to the PDN entity;

-a field denoted "UE DL bearer ID" relating to the identity of the allocation or mapping of data traffic to be sent from the PDN entity to the UE;

-a field denoted "session type", relating to an indication of the type of session used by the UE, the session being defined by

A "session ID" field identification; and

a field denoted "operation mode (for enhancing session model only)", which relates to the operation mode of the identified session when the type of the identified session is an enhanced session. The operating mode may be a preemption mode or a synchronization mode or a reliable mode. These three modes of operation may be configured for ESM by the STM entity, involving the manner in which the STM entity determines how the UE-STe entity and the UP-STe entity use the multiple transport bearers of ESM between the AN and the CN. More specifically, the preemption mode involves reservation of resources in multiple transport bearers between the AN and the CN for the identified session. The synchronous mode involves synchronous use of a selected one of the plurality of transport bearers between the AN and the CN and the reliable mode involves redundancy of data traffic transmission of the selected one of the plurality of transport bearers between the AN and the CN.

In addition, the mapping table within the UE-STe entity includes another field, denoted "AP ID", which relates to the identification of the AP associated with the identified session. In addition, the mapping table within the UP-STe entity includes another field, denoted "UE ID", which relates to the identity of the UE associated with the identified session.

All these mapping tables illustrate how the STM entity configures the UE-STe and UP-STe entities in FIG. 3 to map the UL and DL data traffic of the UE.

Referring to fig. 5(a), fig. 6 shows three exemplary mapping tables of a UE-STe entity in a UE (denoted "UE _ 1") with respective UP-STe entities in

UPFs

1 and 2 in the case of exclusive allocation of multiple transport bearers within an ESM.

Referring to fig. 5(b), fig. 7 illustrates three exemplary mapping tables of a UE-STe entity in a UE (denoted as "UE _ 1") with respective UP-STe entities in

UPFs

1 and 2 in the case of shared allocation of multiple transport bearers within an ESM.

As can be seen from the exemplary mapping tables in fig. 6 and 7, the operation mode of the identified session field is a preemption mode. In this mode, the STM entity indicates which resources of a plurality of transport bearers between the AN and the CN need to be reserved for the ESM associated with the UE, and the UE-STe and UP-STe entities are configured to use only one of the reserved resource sets at a time.

In this regard, FIG. 8 illustrates the use of two sets (B1 and B2) of transport bearers (RAN-B1, AN-CN-B1, CN-CN-B1, RAN-B2, AN-CN-B2, CN-CN-B2) in preemption mode in the exemplary case of exclusive allocation shown in FIG. 5(a), where (a): b1 and B2 correspond to the primary transport bearer set and the secondary transport bearer set, respectively; and (b): b1 and B2 correspond to the secondary transport bearer set and the primary transport bearer set, respectively. It should be noted that in another exemplary case, the allocation described above may also be a shared allocation as shown in fig. 5 (b).

In fig. 8(a), in case the UP-established entity is to use ESM in a preemptive mode of operation, there is a set of primary transport bearers (RAN-B1, AN-CN-B1, CN-B1) for all data traffic transport between the UE and the PDN entity, while another set of secondary transport bearers (RAN-B2, AN-CN-B2, CN-B2) will be reserved for possible UE communication. Resources for the secondary transport bearers (RAN-B2, AN-CN-B2, CN-B2) may be reserved as follows: all resources in the AN and CN are reserved for secondary transport bearers (RAN-B2, AN-CN-B2, CN-CN-B2), only waiting for UE side activation. Alternatively, these resources may be reserved as follows: resources of the CN are reserved only for secondary transport bearers (RAN-B2, AN-CN-B2, CN-B2), and upon detection of a need to activate these resources, AN and UE resources are allocated simultaneously.

Whatever the way the resources of the secondary transport bearers (RAN-B2, AN-CN-B2, CN-CN-B2) are reserved, the UP-STe entity will possess information about the secondary transport bearers (RAN-B2, AN-CN-B2, CN-CN-B2). Nevertheless, the configuration of the STM entity sending over SOC-If will determine that only the primary transport bearer (RAN-B1, AN-CN-B1, CN-CN-B1) is used for the transmission of UL and DL data traffic. Referring to fig. 6, this information is represented as an entry in a column corresponding to a field represented by "operation mode (for enhancing session model only)" of the UP-STe mapping table. Similarly, the UE-STe mapping table is configured with information indicating at least one transport bearer for the preemption mode and the at least one transport bearer is a primary transport bearer (RAN-B1, AN-CN-B1, CN-B1). It should be noted, however, that depending on the manner of reservation and establishment of the secondary transport bearers (RAN-B2, AN-CN-B2, CN-B2), the UE-STe entity may or may not enter the secondary transport bearers (RAN-B2, AN-CN-B2, CN-B2) in the UE-STe entity's mapping table.

In fig. 8(B), relative to fig. 8(a), the primary transport bearer set is changed from B1 to B2, so transmission of UL and DL data traffic is achieved through the following transport bearers: RAN-B2, AN-CN-B2, and CN-CN-B2; the secondary transport bearer set is changed from B2 to B1, so resources are reserved for the following transport bearers: RAN-B1, AN-CN-B1, and CN-CN-B1. This change involves interaction between the UP-STe entity and the Control Plane (CP) entities (i.e., the CPF and STM entities) in order to update the allocation or mapping of transport bearers for transmitting the UE's data traffic.

When the operation mode of the identified session field in the mapping table is the synchronous mode, then multiple transport bearers between the AN and the CN are configured at the entity of UP (i.e., at the UE-STe and UP-STe entities) for simultaneous use. Which transport bearers should be used are decided based on policies deployed on the respective UP-STe and UE-STe entities.

Fig. 9 illustrates the use of multiple transport bearers (RAN-B1, AN-CN-B1, CN-B1 and RAN-B2, AN-CN-B2, CN-B2) in a synchronous mode in the exemplary case of exclusive allocation as shown in fig. 5 (a). It should be noted, however, that in another exemplary case, the allocation described above may also be a shared allocation as shown in fig. 5 (b).

Two data traffic flows (denoted data traffic a and data traffic B) from and towards the UE are shown in fig. 9, the former being sent over the transport bearer RAN-B1 using AP1, and the latter being sent over the transport bearer RAN-B2 using AP 2. The UE-STe and UP-STe entities are entities that define which resources (i.e., which transport bearers) are used for the respective UL and DL data traffic. Thus, the UP-STe entity decides over which transport bearers the UL and DL data traffic should be propagated, while the UE-STe entity only defines which transport bearer should be used for the UL data traffic. It should be noted that in case of shared allocated transport bearers, it is not necessary to decide which transport bearers should be used. However, in case of current exclusive allocation, which transport bearers towards the UE should be used may be decided by any UPF entity as follows: a UPF entity extended based on the function of the respective UP-STe entity and located in a path toward and from the UE. The behavior of each UP-STe and the policy for transmission are determined by the STM entity and (in case the CPF entity is an entity functionally independent from the STM entity) propagated via the CNs-If to the CPF entity controlling the UP-STe entity, which then configures the policy for transmission via the SOC-If for the controlled UP-STe entity. The UE-STe entity is also configured by the STM entity such that the UP-STe entity and the UE-STe entity are configured with respective different policies for selecting a plurality of transport bearers to be used simultaneously between the AN and the CN. The UE-STe and UP-STe entities may use respective default policies for all enhanced sessions (i.e., ESMs) or select one of the available policies for each enhanced session (i.e., each ESM). Among other strategies, the strategy adopted at the UP-STe entity can be a static strategy or a full-decision strategy, and the strategy adopted at the UE-STe entity can be a circular scheduling or AN analysis of AN (AN) condition.

When a static policy is employed at the UP-STe entity, the STM entity determines the exact allocation of transport bearers for the UE's UL and DL data traffic at ESM establishment or ESM reconfiguration. Therefore, if other UP-STe entities exist on the path toward the UE, they are configured through an entry in the mapping table of the corresponding UP-STe entity with an accurate allocation of transport bearers. This policy enables a static configuration of the transport bearer, since it is defined once by the STM entity when the ESM is established or changed.

When a full decision strategy is adopted at the UP-STe entity, the STM entity determines that all UP-STe entities on the UL and DL data traffic paths are able to decide which transport bearers are used for the next hop in the UP-STe entity chain. Within each UP-STe entity where a decision is to be made, different strategies, e.g. looping, may be employed in order to analyze whether there is any congestion of the transport bearers and to prioritize one transport bearer over another. This policy enables dynamic configuration of the mapping table at the UP-STe entity without triggering the reconfiguration procedure. However, the involved UP-STe entities must be able to decide when to change the allocation of multiple transport bearers.

When the policies of round-robin scheduling or conditional analysis of the AN is employed at the UE-STe entity to alter the UL transport bearer to be used, there are two ways that the STM entity can configure the UE-STe entity using each of these policies. In the first approach, the policy may be hard-coded at the UP-STe entity, so that the STM entity can only define that the UE session is to run in a synchronous mode of operation, with or without the policy being decided by the definition of hard-coding at the UE-STe entity. In the second approach, the STM entity may define the synchronization mode of operation and which policy should be used at the UE-STe entity. Corresponding information (in case the CPF entity is an entity functionally independent from the STM entity) is then sent from the STM entity to the CPF entity over the CNs-If, and the CPF entity can configure the UE-STe entity over the ANs-If.

When the operation mode of the identified session field in the mapping table is reliable mode, the same data packets of UL and DL data traffic are sent over all transport bearers of the AN and CN forming the ESM for redundancy reasons.

Fig. 10 illustrates the use of multiple transport bearers (RAN-B1, AN-CN-B1, CN-B1 and RAN-B2, AN-CN-B2, CN-B2) in a reliable mode in the exemplary case of exclusive allocation as shown in fig. 5 (a). It should be noted, however, that in another exemplary case, the allocation described above may also be a shared allocation as shown in fig. 5 (b).

In the reliable mode, the UE-STe entity always replicates the UL data traffic and sends it to the PDN entity over multiple transport bearers of the AN. As for DL data traffic sent from the PDN entity to the UE, it depends on the allocation type of the multiple transport bearers being used. When the exclusive allocation as shown in fig. 10 is used, the UP-STe entity queries the respective mapping tables, determines transport bearers associated with the UE and the PDN entity for the DL data traffic, and further copies the data packets of the DL data traffic to all configured transport bearers involved in the DL data traffic within the ESM.

Thus, based on the above, the UE-STe and UP-STe entities must support different modes of operation configured by the STM entity, and must be able to determine how each packet should be processed. The UE-STe entity only defines how UL data traffic should be processed, while the UP-STe entity may define which transport bearers should be used for UL and DL data traffic.

Fig. 11 is a flowchart illustrating processing steps of a UE-STe entity based on an operation mode of a UE according to an embodiment of the present invention.

As shown in fig. 11, the UE-STe entity includes a mapping table dedicated to allocating a plurality of transport bearers at AN interface between the UE and the AN for performing the following steps:

-a first step (denoted by the number "1"): the UE-STe entity generates an UL data packet (to be sent to a PDN entity);

-a second step (denoted by the number "2"): the UE-STe entity queries its mapping table to determine which session the UL packet is associated with;

-if the determined session is a session other than an enhanced session (i.e. ESM), the UE-STe entity selects in a third step (denoted with the number "3") the only transport bearer available for connecting the UE and the PDN entity, and sends in a fourth step (denoted with the number "4") a UL data packet to the PDN entity;

-if the determined session is an enhanced session (i.e. ESM), the UE-STe entity in a fifth step (with number "5"

Indicating), and if the operation mode is the preemption mode, the UE-STe entity selects the primary transport bearer in a sixth step (indicated by the numeral "6") before sending the UL packet to the PDN entity;

-if the UE-STe entity determines in a seventh step (indicated with the number "7") that the operation mode is not a preemption mode but a synchronization mode, the UE-STe entity determines in an eighth step (indicated with the number "8") which policy should be employed and selects in a ninth step (indicated with the number "9") a transport bearer based on the employed policy before sending the UL packet to the PDN entity;

-if the UE-STe entity determines in a tenth step (denoted with the number "10") that the operation mode is not the synchronous mode but the reliable mode, the UE-STe entity determines all transport bearers associated with the enhanced session (i.e. ESM) and copies the UL data packets to all determined transport bearers in an eleventh step (denoted with the number "11") before sending them to the PDN entity;

-if the UE-STe entity determines in a twelfth step (denoted with the number "12") that the operation mode is neither the preemption mode nor the synchronization mode nor the reliable mode, the UE-STe entity sends an error notification to the CPF entity.

Fig. 12 is a flowchart illustrating processing steps of an UP-STe entity based on an operation mode of a UE according to an embodiment of the present invention.

As shown in fig. 12, each UP-STe entity comprises a respective mapping table dedicated to the allocation of a plurality of transport bearers at the interface between the AN and the CN for performing the following steps:

-a first step (denoted by the number "1"): the UP-STe entity receives an UL data packet from the UE in case of an UL data packet or a DL data packet from the PDN entity in case of a DL data packet;

-a second step (denoted by the number "2"): the UP-STe entity queries its mapping table to determine which session an UL or DL packet is associated with;

-if the determined session is a session other than the enhanced session (i.e. ESM), the UP-STe entity selects in a third step (denoted with the number "3") the only transport bearer available for connecting the UE and the PDN entity, and in a fourth step (denoted with the number "4") sends a DL data packet to the UE in case of a DL data packet or a UL data packet to the PDN entity in case of a UL data packet;

if the determined session is an enhanced session (i.e. ESM), the UP-STe entity proceeds in a fifth step (with the number "5"

Indicate), if the operation mode is the preemption mode, and if the operation mode is the preemption mode, the UP-STe entity selects the primary transport bearer in a sixth step (indicated by the numeral "6") before transmitting a DL data packet to the UE in case of a DL data packet or transmitting a UL data packet to the PDN entity in case of a UL data packet;

-if the UP-STe entity determines in a seventh step (denoted with the number "7") that the operation mode is not the preemption mode but the synchronization mode, the UP-STe entity determines in an eighth step (denoted with the number "8") which policy should be adopted in addition to the policy adopted at the UE-STe entity, before sending a DL data packet to the UE in case of a DL data packet or sending a UL data packet to the PDN entity in case of a UL data packet, and selects in a ninth step (denoted with the number "9") a transport bearer based on the adopted policy;

-if the UP-STe entity determines in a tenth step (denoted with the number "10") that the operation mode is not the synchronous mode but the reliable mode, the UP-STe entity sends a DL data packet to the UE in case of a DL data packet or sends a UL data packet to the PDN entity in case of a UL data packet, in an eleventh step (denoted with the number "11"

Representation) and copies UL or DL data packets to all the determined transport bearers associated with the enhanced session (i.e., ESM);

-if the UP-STe entity determines in a twelfth step (denoted with the number "12") that the operation mode is neither the preemption mode nor the synchronization mode nor the reliable mode, the UP-STe entity sends an error notification to the CPF entity.

As mentioned above, the session configuration request may relate to a need to modify an existing session by modifying or replacing it, which may be caused by a Handover (HO).

In this regard, fig. 13 illustrates a UE-triggered HO procedure between multiple APs all associated with the same ESM and UE-STe entity, in accordance with an embodiment of the present invention.

As shown, in the case where the UE triggers HO, the UE is actually moving from one AP (i.e., AP1) to another AP (i.e., AP2), where the UE has a transport bearer at both APs. Thus, the above trigger will occur at the AN for HO requirements.

This HO procedure relies on the subsequent steps of simplified HO execution (1), simplified HO completion (2) and optional enhanced session re-establishment (3).

Step 1: HO execution is considered simplified because the number of steps it performs is reduced. In fact, there is already an established transport bearer between the UE and the target AP (i.e., AP2 in fig. 13), and thus certain steps (e.g., steps for resource admission) need not be performed at the target AP.

Step 2: HO completion is also considered simplified because there is no need to request configuration of the transport bearer of the CN between the target AP and the entity of the CN. In practice, these transport bearers are already established and only minor changes need to be made depending on the mode of operation of the ESM.

And step 3: enhanced session re-establishment is optional because the determination by the STM entity is based on whether the target AP (i.e., AP2 in fig. 13) needs to include an entity that has other APs to act as ESMs for the UE that has just moved. If other APs need to be included, it means that the STM entity needs to configure the UP-STe and UE-STe entities, taking into account also the resources from the included APs and their respective corresponding transport bearers of the CN.

Fig. 14 shows a UE-triggered HO procedure between multiple APs, not all associated with the same ESM and UE-STe entity, according to an embodiment of the present invention.

As shown, in the case of a UE triggered HO, the UE actually moves from one AP (i.e., AP1) to another AP (i.e., AP3) via another AP (i.e., AP2), where the UE has a transport bearer at AP1, also at AP2, and no transport bearer at AP 3. In fact, the UE-STe entity of the UE with which the AP (i.e., AP3) is associated is different from the UE-STe entity of the UEs with which AP1 and AP2 are associated, and therefore the AP has no resources associated with ESM that the UE has in its source AP (i.e., AP 1).

The HO procedure relies on the subsequent steps of HO execution (1), HO completion (2) and ESM procedure reconfiguration (3).

Step 1 and step 2: HO execution and HO completion are performed according to the current standard such as 3 GPP.

And step 3: thereafter, the session configuration procedure proposed for ESM as shown in fig. 4 is triggered to reassemble the resources of the ESM of the UE and to indicate in which way the UE-STe and UP-STe entities need to handle the included transport bearers from the AP3 and the previous transport bearers related to the UE.

However, the HO procedure depends on the operating mode of the UE.

Thus, when the UE is in the preemption mode, HO is triggered to switch from a primary transport bearer for transmission of UL and DL data traffic to a secondary transport bearer, and vice versa, as shown in fig. 8(b), where the secondary transport bearer is reserved for possible communication with the UE. With reference to the steps in fig. 13, in case of a preemptive mode of operation, the HO procedure can be explained in more detail by its milestone steps of simplified HO execution (1), simplified HO completion (2) and (optionally) enhanced session re-establishment (3).

Step 1: during simplified HO execution, a source AP (e.g., AP1 in fig. 8 (b)) triggers HO of a UE with preconfigured AN resources in a target AP (e.g., AP2 in fig. 8 (b)). The target AP triggers the activation of pre-configured resources in both the AN and the CN. The target AP receives the UE context and sends a context release to the source AP.

Step 2: during the simplified HO completion, the target AP interacts simultaneously with the CPF entity (which in turn interacts with the STM entity) to trigger an update in the UP-STe entity of the CN, to update the DL mapping or allocation at the CN, to convert the preconfigured transport bearer into a primary transport bearer and to release the previous primary resources.

And step 3: during the (optional) enhanced session re-establishment, the STM entity may decide to reconfigure the resources of the transport bearers related to the previous primary transport bearer from the source AP, since these resources are now secondary resources of the UE. The STM entity may also decide on the neighboring APs comprising the target AP in order to make it part of the set of secondary resources available to the UE and thus belong to the same ESM.

When the UE is in either a synchronized mode or a reliable mode, a HO is triggered to enable the UE to connect to an AP associated with a session other than the existing enhanced session.

In case of the synchronous mode, there is no need to actually trigger the HO procedure when the UE-STe entity is already connected to an AP belonging to the same ESM. In fact, the UE already has its required connectivity. Although changes in the AN conditions may affect the UE-STe policy, these changes do not trigger HO procedures between APs already connected to the UE. However, when the UE-STe entity has no transport bearer associated with an AP not included in the ESM, the HO procedure must be triggered. For the UE-STe mapping table, this means that the UE will need to connect to a different AP that is not associated with the same ESM. In the latter case, the HO procedure of fig. 14 may be applied.

In the case of the reliable mode, HO is handled in the same manner as in the synchronous mode. HO between APs already connected to the UE-STe entity in the enhanced session does not need to be triggered, while HO between APs not connected to the UE-STe entity needs to be triggered and processed by standard HO procedures after the session configuration procedure proposed for ESM, as shown in fig. 4, in order to re-adjust the multiple resources in a single PDU, as shown in fig. 14.

In addition to the above configuration, reconfiguration and HO procedures, there are also resource release procedures for resources that are no longer used. The flow is implemented by an STM entity that informs the CPF entity of enhanced session configuration information that must be removed from the UE-STe and UP-STe entities. Based on this information, the CPF entity contacts the UE-STe and UP-STe entities and removes entries of resources that should be released (i.e., transport bearers associated with those resources) from their respective mapping tables.

Fig. 15 shows several different implementations (numbers (a) to (c)) of the present invention in a Long Term Evolution (LTE) architecture.

As shown, the present invention can be implemented in an LTE architecture according to at least three implementations, thereby enabling an LTE system to operate with multiple transport bearers using the same technology.

In the implementation of fig. 15(a), the STDB and STM entities of the present invention and their SD-If interfaces are added as new entities and interfaces of the LTE architecture, respectively. In addition, the CNs-If interface has been added to a Mobility Management Entity (MME), which is one of the entities of the LTE system for controlling session configuration and reconfiguration. A Serving Gateway (SGW) entity and a PDN Gateway (PGW) entity are also control entities of the LTE system for controlling PDN sessions. Thus, instead of adding a new interface from an STM entity to all control entities (i.e., MME, SGW and PGW) of the LTE system related to session management, the existing S11 and S5 interfaces of the LTE system are extended to enhanced S11(enhanced S11, eS11) and enhanced S5(enhanced S5, eS5) interfaces, so that the functionality of the CNs-If interface of the present invention can also be added to these existing interfaces of LTE. Furthermore, the SGW and PGW entities of the LTE system have been extended together with the corresponding proposed UP-STe entities, so that the SGW and PGW entities of the LTE system can not only support the proposed ESM but also perform the above-described procedures and operations. Finally, the S1 interface has also been extended to an enhanced S1(enhanced S1, eS1) interface between evolved nodeB (eNB) and MME entities. Since the eS1 interface also includes the functionality of the ANs-If interface of the present invention, the MME entity (which can be considered equivalent to the CPF entity of the present invention) can send to the UE-STe entity the information necessary for the UE to operate multiple transport bearers.

In the implementation of fig. 15(b), relative to the implementation of fig. 15(a), a Home Subscriber Server (HSS) entity has been extended based on the functionality of the STDB of the present invention. Thus, the SD-If interface of the present invention is added between the extended HSS entity and the STM entity.

In the implementation of figure 15(c), the HSS and MME entities have been extended based on the functionality of the STDB and STM entities of the present invention, respectively, relative to the implementation of figure 15 (a). Therefore, the interface of the present invention is not newly added. However, the existing S6a interface of the LTE system between the current extended HSS entity and the current extended MME entity has been extended to an enhanced S6a (enhanced S6a, eS6a) interface, so that the eS6a interface can provide the functionality of the SD-If interface of the present invention

To sum up, the present invention relates to AN Enhanced Session Model (ESM) capable of managing configuration and usage of a single Packet Data Unit (PDU) session, which is AN association between a User Equipment (UE) and a Packet Data Network (PDN) entity and is composed of multiple transport bearers between AN Access Network (AN) and a core network (core network, CN). The core network includes a Session Type Manager (STM) entity for controlling connectivity of the transport bearers, a plurality of User Plane Function (UPF) entities, a Session Type Database (STDB), and a Control Plane Function (CPF) entity, wherein allocation of the transport bearers is exclusive allocation or shared allocation. The CPF entity may be functionally independent of a Session Type Manager (STM) entity, or may be extended based on the functionality of the STM entity. A User Equipment (UE) and a User Plane Function (UPF) entity are respectively based on a function extension of a user session type extension (UE-STe) entity and a user plane session type extension (UP-STe) entity, wherein the UE-STe entity and the UP-STe entity each include a corresponding mapping table dedicated for allocation and can support different operation modes of the User Equipment (UE) configured by a Session Type Manager (STM) entity. Therefore, the present invention is advantageous in that multiple branches between a Radio Access Network (RAN) and a Core Network (CN) can be preconfigured (pre-admitted) for the same User Equipment (UE) using the same Radio Access Technology (RAT) by creating a distribution or mapping system between multiple transport bearers. Furthermore, the present invention can provide better mobility support for ultra-reliable low latency communication (ulrllc) use cases by reducing the flow steps for reconnection of the wireless part of the User Equipment (UE) session in the target Access Point (AP) and path switching in the Core Network (CN), and pre-configuring the Radio Access Network (RAN) and the Core Network (CN) before any Handover (HO) is performed. The invention also has the advantage of improving the application throughput of the UE side because synchronous transmission bearing is utilized between the Access Network (AN) and the Core Network (CN).

In terms of usage, the present invention can be applied to cases related to reliability. For example, ESM may be used for devices with ultra-reliable services. For another example, when AP1 is not delivering data traffic to the UE according to given requirements, the control plane may trigger HO between AP1 and AP2 in order to use the preconfigured transport bearer instead of the primary transport bearer. In addition, the invention can be used for reducing the loss and the performance degradation of the UE in the anchor point reselection process in the NextGen mobile core network, and can also be used for ensuring the reliability of the uRLLC use case in the NextGen.

While the invention has been illustrated and described in detail in the drawings and foregoing description, such illustration and description are to be considered illustrative or exemplary and not restrictive. The invention is not limited to the disclosed embodiments. Other modifications will be apparent to persons skilled in the art upon reading this disclosure. Such modifications may involve other features which are already known in the art and which may be used instead of or in addition to features already described herein.

The invention has been described in connection with various embodiments herein. However, other variations to the disclosed embodiments can be understood and effected by those skilled in the art in practicing the claimed invention, from a study of the drawings, the disclosure, and the appended claims. In the claims, the word "comprising" does not exclude other elements or steps, and the word "a" or "an" not specifically stated does not exclude a plurality. A single processor or other unit may fulfill the functions of several items recited in the claims. The mere fact that certain measures are recited in mutually different dependent claims does not indicate that a combination of these measures cannot be used to advantage. A computer program may be stored/distributed on a suitable medium, such as an optical storage medium or a solid-state medium supplied together with or as part of other hardware, but may also be distributed in other forms, such as via the internet or other wired or wireless telecommunication systems.

While the invention has been described in conjunction with specific features and embodiments thereof, it is evident that various modifications and combinations can be made thereto without departing from the spirit and scope of the invention. Accordingly, the specification and figures are to be regarded only as illustrative of the invention as defined in the appended claims and are intended to cover any and all modifications, variations, combinations, or equivalents within the scope of the invention.

Claims

1. A Core Network (CN) of a mobile communication network for managing a plurality of transport bearers, the CN comprising:

-a Session Type Manager (STM) entity for controlling connectivity of the plurality of transport bearers between AN Access Network (AN) of the mobile communication network and the CN based on the selective allocation of the plurality of transport bearers;

wherein

-each transport bearer is defined as a logical connection between two entities sending data traffic;

-said allocation of said plurality of transport bearers is performed for at least one transport bearer of said CN and at least two transport bearers of said same AN on at least two different Access Points (APs) respectively located at said AN, each transport bearer belonging to a single Packet Data Unit (PDU) session defined as AN association between a User Equipment (UE) and a Packet Data Network (PDN) entity; and

-AN Enhanced Session Model (ESM) is defined as a model in which the UE has the at least two transport bearers of the same AN and the at least one transport bearer of the Core Network (CN), wherein the at least two transport bearers of the AN and the at least one transport bearer of the CN all belong to the single PDU session.

2. Core Network (CN) according to claim 1, wherein the allocation between the at least two transport bearers of the AN and the at least one transport bearer of the CN is selected by the STM entity as AN exclusive allocation, wherein each transport bearer of the AN is connected separately to each respective transport bearer of the CN, or as a shared allocation, wherein the at least two transport bearers of the AN are connected together to a single transport bearer of the CN.

3. Core Network (CN) according to claim 1 or 2, characterized in that it comprises:

-a plurality of User Plane Function (UPF) entities, defined as Network Functions (NFs) for processing user plane traffic in order to provide some network services; and

-a Control Plane Function (CPF) entity defined as a Network Function (NF) for performing control plane functions for the UE connected to the mobile communication network for exchanging any data traffic with the PDN entity over the AN and the CN.

4. Core Network (CN) according to any of claims 3-4, wherein the CPF entity:

-is an entity functionally independent of the STM entity or an entity based on a functional extension of the STM entity;

-for receiving a session configuration request;

-for communicating with the STM entity for requesting session configuration information on the enhanced session when the CPF entity is a function independent entity or for determining session configuration information on the enhanced session when the CPF entity is based on a functional extension of the STM entity; and

-sending information to the UPF entity and the UE on how to establish or change the session of the UE based on the session configuration information;

wherein

-the session configuration request relates to a session or service request from the UE or to a need to change an existing session by modifying or replacing the existing session, the need to change the existing session being identified by a Session Type Database (STDB) of the CPF entity, the STM entity or the CN;

-the session configuration information relates to a mode of operation of the session of the UE to be established, the mode of operation being selected by the STM entity as either a preemption mode or a synchronization mode or a reliability mode;

-the preemption mode involves resource reservation for the session of the UE to be established in the plurality of transport bearers between the AN and the CN;

-the synchronization mode involves simultaneous use of a selected transport bearer of the plurality of transport bearers between the AN and the CN; and

-said reliable mode relates to a transmission redundancy of data traffic of said selected one of said plurality of transport bearers between said AN and said CN.

5. A Session Type Manager (STM) entity of a Core Network (CN) of a mobile communication network according to any of claims 1 to 4.

6. A Control Plane Function (CPF) entity of a Core Network (CN) of a mobile communication network according to any of claims 1 to 4.

7. A User Plane Function (UPF) entity of a Core Network (CN) of a mobile communication network according to any of claims 1 to 4.

8. A Session Type Database (STDB) of a Core Network (CN) of a mobile communication network according to any of claims 1 to 4.

9. A mobile communications network, comprising:

-a Core Network (CN) according to claims 1 to 4;

-AN Access Network (AN) according to claim 1;

-a User Equipment (UE) according to claim 1; and

-a Packet Data Network (PDN) entity according to claim 1;

wherein

-said UE and said PDN entity communicating with each other through said AN and said CN.

10. A method for managing a plurality of transport bearers within a mobile communications network, the mobile communications network being divided into AN Access Network (AN) and a Core Network (CN), the method comprising:

-controlling connectivity of the plurality of transport bearers between the AN and the CN based on the selective allocation of the plurality of transport bearers at a Session Type Manager (STM) entity,

wherein

11. The method of claim 10, wherein the step of controlling connectivity of the plurality of transport bearers between the AN and the CN comprises:

-receiving a session configuration request at a Control Plane Function (CPF) entity, said session configuration request relating to establishment of a session from said UE connected to said mobile communication network for exchanging any uplink, UL, and downlink, DL, data traffic with said PDN entity over said AN and said CN, or relating to a need to modify AN existing session by modifying or replacing said existing session, said need being identified by said CPF entity, said STM entity or a Session Type Database (STDB) interacting with said STM entity;

-determining session configuration information related to the establishment of the enhanced session at the STM entity;

-receiving the session configuration information at the CPF entity;

-deploying the session configuration information from the CPF entity to the User Plane Function (UPF) entity of the CN, the AP of the AN and the UE, the UPF entity of the CN, the AP of the AN and the UE all being configured to support the plurality of transport bearers associated with the data traffic of the UE for the enhanced session; and

-reserving resources of the plurality of transport bearers between the AN and the CN for the enhanced session based on the deployed session configuration information.

12. The method of claim 11, wherein the step of determining the session configuration information comprises:

-defining, at the STM entity, an allocation of the plurality of transport bearers supported by the identified UPF entity and the AP.

13. The method of claim 12, wherein the allocating of the plurality of transport bearers is performed for at least two transport bearers of the AN and at least one transport bearer of the CN, wherein the at least two transport bearers of the AN and the at least one transport bearer of the CN all belong to the single PDU session.

14. The method of claim 13, wherein the step of defining the allocation of the plurality of transport bearers comprises:

-selecting AN exclusive allocation, wherein each transport bearer of the AN is connected individually to each respective transport bearer of the CN, or selecting a shared allocation, wherein transport bearers of the AN are connected together to a single transport bearer of the CN.

15. A computer-readable medium, characterized in that it comprises computer program instructions for carrying out the method according to any one of claims 10 to 14, when said computer program is executed on a computer.

16. A computer program product comprising a computer program, characterized in that the computer program when executed implements the method of any of claims 10 to 14.