WO2017076441A1 - Gestion de connexions - Google Patents

Gestion de connexions Download PDF

Info

Publication number
WO2017076441A1
WO2017076441A1 PCT/EP2015/075705 EP2015075705W WO2017076441A1 WO 2017076441 A1 WO2017076441 A1 WO 2017076441A1 EP 2015075705 W EP2015075705 W EP 2015075705W WO 2017076441 A1 WO2017076441 A1 WO 2017076441A1
Authority
WO
WIPO (PCT)
Prior art keywords
radio resource
resource control
user terminal
connections
control connection
Prior art date
Application number
PCT/EP2015/075705
Other languages
English (en)
Inventor
Yang Liu
Mikko Saily
Lei Du
Original Assignee
Nokia Solutions And Networks Oy
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by Nokia Solutions And Networks Oy filed Critical Nokia Solutions And Networks Oy
Priority to PCT/EP2015/075705 priority Critical patent/WO2017076441A1/fr
Priority to EP15793744.2A priority patent/EP3372048A1/fr
Publication of WO2017076441A1 publication Critical patent/WO2017076441A1/fr

Links

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/30—Connection release
    • H04W76/34—Selective release of ongoing connections

Definitions

  • the invention relates to communications.
  • an apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: coordinate one or more radio resource control connections to a user terminal, at least one of the one or more connections being maintained by the apparatus; maintain mobile context information of the user terminal, the mobile context comprising information on the one or more radio resource control connections; receive an indication to remove at least one of the one or more radio resource control connections to the user terminal; check the radio resource connection status of the user terminal and if at least one other of the one or more radio resource connections to the user terminal exists, and continue maintaining the mobile context information of the user terminal.
  • an apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: receive a request to set up a radio resource control connection to a user terminal, the request comprising information on a node apparatus acting as a anchor point of radio resource control connections to the user terminal; set up the radio resource control connection to the user terminal; request information on a mobile context of the user terminal from the node apparatus, and receive information on the mobile context of the user terminal from the node apparatus.
  • an apparatus comprising: at least one processor; and at least one memory including computer program code, the at least one memory and the computer program code configured to, with the at least one processor, cause the apparatus at least to perform: establish a first radio resource control connection to a first node apparatus; establish at least one second radio resource control connection to at least one second node apparatus and inform the at least one second node apparatus about the first node apparatus, the first node apparatus operating as a anchor point of radio resource control connections of the apparatus; determine a need to release a radio resource control connection of the established first radio resource control connection and the at least one second radio resource control connection, and check statuses of other radio resource control connections among the established first radio resource control connection and the at least one second radio resource control connection and if the other radio resource control connections are released, enter into an idle mode.
  • a method comprising: coordinating one or more radio resource control connections to a user terminal, at least one of the one or more connections being maintained by the apparatus; maintaining mobile context information of the user terminal, the mobile context comprising information on the one or more radio resource control connections; receiving an indication to remove at least one of the one or more radio resource control connections to the user terminal; checking the radio resource connection status of the user terminal and if at least one other of the one or more radio resource connections to the user terminal exists, and continuing maintaining the mobile context information of the user terminal.
  • a method comprising: receiving a request to set up a radio resource control connection to a user terminal, the request comprising information on a node apparatus acting as a anchor point of radio resource control connections to the user terminal; setting up the radio resource control connection to the user terminal; requesting information on a mobile context of the user terminal from the node apparatus, and receiving information on the mobile context of the user terminal from the node apparatus.
  • a method comprising: establishing a first radio resource control connection to a first node apparatus; establishing at least one second radio resource control connection to at least one second node apparatus and inform the at least one second node apparatus about the first node apparatus, the first node apparatus operating as a anchor point of radio resource control connections of the apparatus; determining a need to release a radio resource control connection of the established first radio resource control connection and the at least one second radio resource control connection, and checking statuses of other radio resource control connections among the established first radio resource control connection and the at least one second radio resource control connection and if the other radio resource control connections are released, entering into an idle mode.
  • a computer program embodied on a non- transitory computer-readable medium, the computer program comprising program code portions for controlling executing of a process, the process comprising: coordinating one or more radio resource control connections to a user terminal, at least one of the one or more connections being maintained by the apparatus; maintaining mobile context information of the user terminal, the mobile context comprising information on the one or more radio resource control connections; receiving an indication to remove at least one of the one or more radio resource control connections to the user terminal; checking the radio resource connection status of the user terminal and if at least one other of the one or more radio resource connections to the user terminal exists, and continuing maintaining the mobile context information of the user terminal.
  • a computer program embodied on a non- transitory computer-readable medium, the computer program comprising program code portions for controlling executing of a process, the process comprising: receiving a request to set up an radio resource control connection to a user terminal, the request comprising information on a node apparatus acting as a anchor point of radio resource control connections to the user terminal; setting up an radio resource control connection to the user terminal; requesting information on the mobile context of the user terminal from the node apparatus, and receiving information on the mobile context of the user terminal from the node apparatus.
  • a computer program embodied on a non- transitory computer-readable medium, the computer program comprising program code portions for controlling executing of a process, the process comprising: establishing a first radio resource control connection to a first node apparatus; establishing at least one second radio resource control connection to at least one second node apparatus and inform the at least one second node apparatus about the first node apparatus, the first node apparatus operating as a anchor point of radio resource control connections of the apparatus; determining a need to release a radio resource control connection of the established first radio resource control connection and the at least one second radio resource control connection, and checking statuses of other radio resource control connections among the established first radio resource control connection and the at least one second radio resource control connection and if the other radio resource control connections are released, entering into an idle mode.
  • an apparatus comprising means for coordinating one or more radio resource control connections to a user terminal, at least one of the one or more connections being maintained by the apparatus; means for maintaining mobile context information of the user terminal, the mobile context comprising information on the one or more radio resource control connections; means for receiving an indication to remove at least one of the one or more radio resource control connections to the user terminal; means for checking the radio resource connection status of the user terminal and if at least one other of the one or more radio resource connections to the user terminal exists, and means for continuing maintaining the mobile context information of the user terminal.
  • an apparatus comprising means for receiving a request to set up a radio resource control connection to a user terminal, the request comprising information on a node apparatus acting as a anchor point of radio resource control connections to the user terminal; means for setting up the radio resource control connection to the user terminal; requesting information on a mobile context of the user terminal from the node apparatus, and means for receiving information on the mobile context of the user terminal from the node apparatus.
  • an apparatus comprising means for establishing a first radio resource control connection to a first node apparatus; means for establishing at least one second radio resource control connection to at least one second node apparatus and means for informing the at least one second node apparatus about the first node apparatus, the first node apparatus operating as a anchor point of radio resource control connections of the apparatus; means for determining a need to release a radio resource control connection of the established first radio resource control connection and the at least one second radio resource control connection, and means for checking statuses of other radio resource control connections among the established first radio resource control connection and the at least one second radio resource control connection and if the other radio resource control connections are released, means for entering into an idle mode.
  • Figure 1 illustrates a simplified view of a communication environment
  • Figure 2 is a flow chart
  • Figure 3 illustrates an example of a state machine
  • Figure 4 is a flow chart
  • Figure 5 is a flow chart
  • Figure 6 illustrates an example of signalling in a multi connectivity operation
  • Figures 7, 8 and 9 illustrate simplified examples of apparatuses.
  • Embodiments are applicable to any base station, user equipment (UE), user terminal (UT), server, corresponding component, and/or to any communication system or any combination of different communication systems that support dual or multi connectivity and required functionalities.
  • UE user equipment
  • UT user terminal
  • server corresponding component
  • Embodiments are applicable to any base station, user equipment (UE), user terminal (UT), server, corresponding component, and/or to any communication system or any combination of different communication systems that support dual or multi connectivity and required functionalities.
  • the protocols used, the specifications of communication systems, servers and user terminals, especially in wireless communication develop rapidly. Such development may require extra changes to an embodiment. Therefore, all words and expressions should be interpreted broadly and they are intended to illustrate, not to restrict, embodiments.
  • UMTS telecommunications system
  • UTRAN radio access network
  • E-UTRAN long term evolution
  • LTE-A long term evolution advanced
  • evolutions of LTE-A such as 5G, Wireless Local Area Network (WLAN) or Wi-Fi based on IEEE 802.1 I stardard, worldwide interoperability for microwave ac-cess (WiMAX), Bluetooth®, personal communications services (PCS) and systems using ultra-wideband (UWB) technology.
  • IEEE refers to the Institute of Electrical and Electronics Engineers.
  • Figure 1 illustrates a simplified view of a communication environment only showing some elements and functional entities, all being logical units whose implementation may differ from what is shown.
  • the connections shown in Figure 1 are logical connections; the actual physical connections may be different.
  • the systems also comprise other functions and structures. It should be appreciated that the functions, structures, elements and the protocols used in or for communication are irrelevant to the actual invention. Therefore, they need not to be discussed in more detail here.
  • the embodiments are not, however, restricted to the system given as an example but a person skilled in the art may apply the solution to other communication systems provided with necessary properties.
  • base stations there are base stations, access points or node apparatuses 102, 104, 106 each having a service area which may be overlapping with service areas of other access points.
  • These access points are base stations which may serve macro cells or so called small cells (SC), micro cells or pico cells, which have considerably smaller coverage area compared to the macro cells.
  • SC small cells
  • These small cells may be denoted as micro or pico cells and the coverage areas of the cells may be overlapping.
  • a cell may be also denoted as a logical or virtual cell using available radio resources at local geographical area.
  • the access points 102, 104, 106 depict an apparatus controlling one or more cells via which network access is provided to user terminals.
  • a network node is an evolved node B (eNB, eNodeB).
  • the evolved node B or any corresponding network apparatus controlling one or more cells is a computing device configured to control the radio resources, and connected to the evolved packet core network, thereby providing the user equipment or user terminal 100 a connection to the communication system.
  • the evolved node B comprises all radio-related functionalities of the communication whereby the evolved node B, for example, schedules transmissions by assigning certain uplink resources for the user equipment and informing the user terminal about transmission formats to be used.
  • the user terminal 100 may have one or more radio connections 1 18, 120, 122 to one or more access nodes 102, 104, 106.
  • the access points 102, 104, 106 may be communicate with each other using a suitable interface 108.
  • the interface may be denoted as X2 interface.
  • each of the access points 102, 104, 106 may be connected via interfaces 1 10, 1 12 and 1 14 to core network (CN) 1 16 of the communication system.
  • CN core network
  • one of the network apparatuses the access points are connected to in the core network may be control management mobile gateway (CMGW), for example.
  • CMGW control management mobile gateway
  • 5G system it is likely to use multiple input - multiple output (MIMO) antennas, many more base stations or nodes than the LTE (a so-called small cell concept), including macro sites operating in co-operation with smaller stations and perhaps also employing a variety of radio technologies for better coverage and enhanced data rates.
  • MIMO multiple input - multiple output
  • 5G will likely be comprised of more than one radio access technology (RAT), each optimized for certain use cases and/or spectrum.
  • RAT radio access technology
  • 5G mobile communications will have a wider range of use cases and related applications including video streaming, augmented reality, different ways of data sharing and various forms of machine type applications, including vehicular safety, different sensors and real-time control.
  • 5G is expected to have multiple radio interfaces, namely below 6GHz, cmWave and mmWave, and also being integradable with existing legacy radio access technologies, such as the LTE. Integration with the LTE may be implemented, at least in the early phase, as a system, where macro coverage is provided by the LTE and 5G radio interface access comes from small cells by aggregation to the LTE. In other words, 5G is planned to support both inter-RAT operability (such as LTE-5G) and inter-RI operability (inter-radio interface operability, such as below 6GHz - cmWave, below 6GHz - cmWave - mmWave).
  • inter-RAT operability such as LTE-5G
  • inter-RI operability inter-radio interface operability
  • NFV network functions virtualization
  • a virtualized network function may comprise one or more virtual machines running computer program codes using standard or general type servers instead of customized hardware. Cloud computing or data storage may also be utilized.
  • node operations In radio communications this may mean node operations to be carried out, at least partly, in a server, host or node operationally coupled to a remote radio head. It is also possible that node operations will be distributed among a plurality of servers, nodes or hosts. It should also be understood that the distribution of labour between core network operations and base station operations may differ from that of the LTE or even be non-existent.
  • Some other technology advancements probably to be used are Software- Defined Networking (SDN), Big Data, and all-I P, which may change the way networks are being constructed and managed.
  • CPS cyber-physical system
  • ICT devices sensors, actuators, processors microcontrollers, etc.
  • Mobile cyber physical systems in which the physical system in question has inherent mobility, are a subcategory of cyber- physical systems. Examples of mobile physical systems include mobile robotics and electronics transported by humans or animals.
  • the user terminal UT (or user apparatus, user equipment) 100 illustrates one type of an apparatus to which resources on the air interface are allocated and assigned, and thus any feature described herein with user terminal (user equipment) may be implemented with a corresponding apparatus.
  • the user terminal 100 refers to a portable computing device that includes wireless mobile communication devices operating with or without a subscriber identification module (SIM), including, but not limited to, the following types of devices: mobile phone, smart-phone, personal digital assistant (PDA), laptop computer, e- reading device, and tablet.
  • SIM subscriber identification module
  • a user device may also be a device having capability to operate in Internet of Things (loT) network which is a scenario in which objects are provided with the ability to transfer data over a network without requiring human-to-human or human-to-computer interaction.
  • LoT Internet of Things
  • user terminal may have a connection to access nodes or points simultaneously (multi-connectivity), improving bit rate performance through multiple downlink streams, as well as signal strength and resilience. It is assumed that multi-connectivity is a key feature in supporting multi-layer networks consisting of both macro and small cell coverage.
  • Another example of the application of multi-connectivity is mission critical or ultra-reliable machine-type communication.
  • Examples of possible applications are reliable cloud connectivity, V2X wireless coordination (coordination based on short messages) and sensor-based alarms in critical systems.
  • Ultra-reliable communication is sensitive to channel impairments, such as fading, shadowing and interference, handover reliability is of importance as well.
  • One way to meet such stringent requirements is to use multiple simultaneous connections not only for data transmission, but also for control purposes, such as radio resource control transmission.
  • radio resource control The major functions of the radio resource control (RRC) protocol include connection establishment and release functions, broadcast of system information, radio bearer establishment, reconfiguration and release, RRC connection mobility management procedures, paging notification and release and outer loop power control.
  • RRC radio resource control
  • the RRC configures the user and control planes according to the network status and allows for radio resource management strategies to be implemented.
  • terminology may vary in different radio protocols and thus term radio resource control should be understood to cover not only the functions or operations of RRC as defined in the LTE, but also similar operations in relation to other standards.
  • inventions suitable for supporting multi-connectivity or multiple- connectivity radio resource control connections are disclosed in further detail by means of Figure 2.
  • the embodiments may be carried out by an access node which operates as an anchor node (such as a master in a master-slave type operation).
  • the anchor node is typically a node where S1 -C interface (LTE terminology) is terminated that is to say, the anchor node may communicate with a core network. It may thus operate as a coordinating node towards "slave" nodes.
  • the embodiment starts in block 200.
  • one or more radio resource control connections to a user terminal are coordinated of which radio resource control connections at least one is also provided.
  • a single-connectivity case there is only one radio resource control connection provided and coordinated.
  • more than one radio resource control connections are coordinated of which one or more are also provided.
  • An anchor node may communicate with a core network in a coordinated-manner on behalf of slave nodes with regard to multi-connectivity operation of a user terminal.
  • the managing across different access points may utilise X2 Application Protocol (X2AP), for example.
  • X2AP X2 Application Protocol
  • the number of nodes involved may vary as well as the number of connections and the coordination of the changes may be carried out by the anchor node as well.
  • a new RRC connection may be established for the user terminal.
  • the user terminal may communicate in relation to this matter independently from the anchor node and after is has set up a new RRC connection with another access point, it transmits information on this radio resource control RRC connection establishment to the anchor node.
  • the mobile context information of the user terminal is maintained.
  • the mobile context comprises information on the one or more radio resource control connections.
  • the mobile context of a user terminal comprises information on control plane resources (user terminal identifiers, user terminal capabilities%), a quality of service (QoS) profile related to the user terminal and security context associated with this user terminal and association with core network (CN).
  • QoS quality of service
  • CN core network
  • context information is in relation to authentication, authorization and accounting.
  • the operation of radio resource control may be controlled by a state machine which defines certain specific states that a user terminal may be in. The different states in this state machine have usually different amounts of radio resources associated with them and these are the resources that the user terminal may use when it is present in a given specific state.
  • the node providing the RRC connection creates a mobile context for the user terminal. If the user device's status is changed into a multiple RRC connection state and one or more further or additional RRC connections are set up, the node providing the first RRC connection operates as an anchor node for the user terminal in relation to these connections and combines all the related RRC connections to this mobile context for coordination purposes (terminating S1 - C interface from a core network).
  • all the RRC connection in the multiple-connectivity operation is one RRC connection and it communicates in the radio network side with the anchor node. It should be understood that it is possible to change the anchor node, if required.
  • the anchor node notifies the core network about the release of a radio resource control connection only if there are no other radio resource control connections to the user terminal.
  • an indication to remove at least one of the one or more radio resource control connections to the user terminal is received.
  • the indication may be a connection release request message from the user terminal or an access node providing the radio resource control connection (the latter is possible in the case the indication is in relation to a multi-connectivity RRC connection provided by an access point or node operating as a slave node).
  • the radio resource connection status of the user terminal is checked and if at least one other of the one or more radio resource connections to the user terminal exists, in block 210, maintaining the mobile context information of the user terminal is continued.
  • the radio resource connection status check may be carried out by means of checking the status of the state machine or based on radio channel measurements (for example, the use terminal may be in a multiple RRC connection state, but a connection is lost).
  • the mobile context may be removed after the RRC connection is released. If the user terminal is in a single RRC connection state, but the connection is lost and only one RRC connection is up, the mobile context may be removed after the RRC connection is released. If the user terminal is in a multiple RRC connection state and more than one RRC connections are up, the requested RRC connection is released, but the mobile context is maintained still to be used for other RRC connections. If the RRC connection to be released is provided by the anchor node, one of the slave nodes may become a new anchor node provided there are more than one RRC connections up and thus the user terminal is still in the multiple RRC connection state.
  • FIG. 3 illustrates an example of the state transition diagram (state machine) of a user terminal adaptable to the variation in the number of radio resource connections.
  • the user terminal may be in an RRC idle state 316 when it has no RRC connections to network. If a single RRC connection is established 304, the user terminal will be single RRC connected 300 while being in the RRC connected state. If the connection is released 306, the user terminal returns to RRC idle state 316.
  • RRC idle state establishes 308 more than one RRC connections at the same time it will be multiple RRC connected 302 while being in the RRC connected state. If all RRC connections are released 310 at the same time, the user terminal returns to RRC idle state 316.
  • the user terminal If the user terminal is single RRC connected 300 and a new RRC connection is established, the user terminal will be 312 multiple RRC connected 302. Likewise, if a user terminal which is multiple RRC connected 302 releases one of more RRC connections, but keeps only one RRC connection established, the user terminals will be 314 single RRC connected 300. However, if a user terminal which is multiple RRC connected 302 releases 316 one of more RRC connections, but keeps more than one RRC connection established, the user terminals remains multiple RRC connected 302. The same naturally applies if the user terminal establishes 316 a new RRC connection while being multiple RRC connected 302.
  • single RRC connected 300 corresponds to the legacy RRC connected state and multiple RRC connected 302 is defined to support multiple RRC connections of the user terminal.
  • the anchor node may receive from the other access point a request regarding mobile context information of the user terminal to be used for the multi- connectivity operation.
  • at least one RRC connection is configured to be inactive regarding data transmission, in which case the data transmission may be activated by a command.
  • the embodiment ends in block 212.
  • the embodiment may be repeated in many ways, arrow 214 shows one example. This example depicts an embodiment, when another indication to remove at least one of the one or more radio resource control connections to the user terminal is received.
  • inventions suitable for supporting multi-connectivity radio resource control connections are disclosed in further detail by means of Figure 4.
  • the embodiments may be carried out by an access node which operates as a slave node in a master-slave type operation.
  • the embodiment starts in block 400.
  • a request to set up a radio resource control connection to a user terminal is received.
  • the request comprises information on a node apparatus acting as an anchor point of radio resource control connections to the user terminal.
  • radio resource control connections are coordinated of which one or more are also provided.
  • An anchor node may communicate with a core network in a coordinated-manner on behalf of slave nodes with regard to multi- connectivity operation of a user terminal.
  • the radio resource control connection to the user terminal is set up.
  • the node providing the RRC connection creates a mobile context for the user terminal. If the user device's status is changed into a multiple RRC connection state and one or more further or additional RRC connections are set up, the node providing the first RRC connection operates as an anchor node for the user terminal in relation to these connections and combines all the related RRC connections to this mobile context for coordination purposes (terminating S1 -C interface from a core network). From the core network's perspective, all the RRC connection in the multiple-connectivity operation is one RRC connection and it communicates in the radio network side with the anchor node.
  • other nodes than the anchor node may request the mobility context of the user terminal from the anchor node to be used with regard to other related RRC connections.
  • information on the mobile context of the user terminal is received from the node apparatus operating as an anchor point or node.
  • a need to release the radio resource control RRC connection to a user terminal is determined, for example by receiving a request form the user terminal.
  • the information on the need is transmitted to the node apparatus acting as anchor point and the radio resource control connection is released.
  • the embodiment ends in block 410.
  • the embodiment may be repeated in many ways, arrow 412 shows one example.
  • inventions suitable for supporting multi-connectivity radio resource control connections are disclosed in further detail by means of Figure 5.
  • the embodiments may be carried out by a user terminal.
  • the embodiment starts in block 500.
  • a first radio resource control connection to a first node apparatus is established or set up. This may be carried out based on a request transmitted to an access point or node (the first node apparatus) and configuration information received as a response to the request.
  • At least one second radio resource control connection to at least one second node apparatus is established or set up and the at least one second node apparatus is informed about the first node apparatus operating as a controller or an anchor point/node of radio resource control connections of the user terminal in the multi-connectivity operation.
  • the user terminal may select which node is to be operated as an anchor point, for example on the basis of signal qualities of access points measured by the user terminal.
  • first radio resource control connection and one or more of the at least one second radio resource control connections may be set up simultaneously (or the setting up is triggered simultaneously, the actual procedures may be carried out independently and thus establishing the connections may take variable periods of time) or one by one according to the need.
  • the radio resource control connections may also be set up one by one, or connections may be added according to a need for multi-connectivity.
  • a need to release a radio resource control connection of the established first radio resource control connection and the at least one second radio resource control connection is determined.
  • the determination may be made by the user device (based on a need, for example, service or application used, or based on measurements made on the radio channel, etc) or by the serving node (based on a need, for example, service or application used, or based on measurements made on the radio channel, etc). If the serving node determines the need to release an RRC connection, it may communicate it to the user device.
  • the user terminal is able to transfer (transmit and receive) radio resource control messages with each of the access nodes it communicates with independently from the other access nodes.
  • Each of the radio resource control connection may also be configured/reconfigured independently.
  • the configuration/reconfiguration may also be aligned in such a manner that the configurations are as similar as possible for all the RRC connections with regard to the multi-connectivity operations.
  • the user device may also request for an RRC connection and set it up without communicating with the anchor node (The user terminal informs the anchor node after the RRC connection is set up for the RRC connection being added to the already created mobility context).
  • a mobile context may be removed after the RRC connection is released. If the user terminal is in a multiple RRC connection state, but the connection is lost and only one RRC connection is up, the mobile context may be removed after the RRC connection is released. If the user terminal is in a multiple RRC connection state and more than one RRC connections are up, the requested RRC connection is released, but the mobile context is maintained still to be used for other RRC connections. If the RRC connection to be released is provided by the anchor node, one of the slave nodes may become a new anchor node provided there are more than one RRC connections up and thus the user terminal is still in the multiple RRC connection state.
  • FIG. 3 illustrates an example of the proposed state transition diagram (state machine) of a user terminal (see above).
  • a user terminal is in an idle mode, it is only listening to control channel broadcasts, such as paging notifications and no radio resources are assigned to it and when the user terminal is in a connected state, it either transmits data or waits for data transmission, and dedicated radio resources are allocated and a mobility context established by the network.
  • control channel broadcasts such as paging notifications and no radio resources are assigned to it
  • dedicated radio resources are allocated and a mobility context established by the network.
  • the user device may issue a request to the network.
  • the user terminal carries out neighbour cell measurements for the multiple RRC connections and reports the measurement results to the access node acting as an anchor point.
  • At least one of the radio resource control connections may be configured to be inactive or active based on the information received from the anchor point or node.
  • the user device may share its capability between different radio resource control connections, for example it may share its radio head between multiple transmissions.
  • the user terminal while being in multiple RRC connected state may be configured with a user terminal specific discontinuous transmission (DRX).
  • the DRX may be applied to and coordinated between all the RRC connections.
  • the user terminal may be configured into an RRC intermediate state which has the characteristics of an inactive data transmission.
  • the RRC may include at least one RRC Intermediate state connection which can be in the context of the multiple RRC connected state for improved robustness, for example when radio conditions of the user terminal suddenly deteriorate.
  • the RRC Intermediate state can be activated and included into the multiple RRC connected state using RRC protocol signalling or with a command from a medium access control MAC network element, for example.
  • the activation of the pending RRC configuration may be carried out on the basis of an RRC instance. This allows almost latency free RRC reconfiguration.
  • the embodiment ends in block 510.
  • the embodiment may be repeated in many ways, arrow 512 shows one example.
  • different services for the same device may be supported in a multi-connectivity state.
  • an RRC connection which is robust might be used to a service requiring strong continuity.
  • Another simultaneous RRC connection having higher latency might be used for another service which is not delay sensitive.
  • Figure 6 illustrates an example of signalling in a multi connectivity setup procedure.
  • user terminal 100 initiates two RRC connections setup procedures with two different access points 102 and 104.
  • the user terminal receives system information transmissions 600, 602 from access points 102, 104.
  • the user terminal may be configured to perform measurements on the transmissions and select an access point acting as an anchor point on the basis of the measurements.
  • the user terminal is configured to transmit RRC establishment requests, 604, 606 to the access points 104, 102.
  • the requests may comprise indication that the access point 104 is selected to act as the anchor point.
  • the access points 102, 104 respond 608, 610 to the request by setting up an RRC connection.
  • the user terminal 100 transmits an RRC connection setup complete message 612, 614 to both access points.
  • the access point acting as an anchor point informs a core network 1 16 (a control management mobile gateway, CMGW, for example) about the user terminal 616.
  • the core network transmits a mobile context setup request 618 to the access point 104 acting as the anchor point which is configured to respond with a mobile context set up response 620.
  • the access point 104 acting as the anchor point creates a mobile context for the user terminal. Both RRC connections of the user terminal are mapped to this mobile context. From the core network point of view, there is only one interface, namely to the access point 104.
  • the access point 102 not acting as the anchor point is configured to request 622 information on the mobile context from the access point 104 acting as the anchor point.
  • the access point 104 waits until it receives the mobile context from the core network and then responses to the access node 102 with a mobile context acknowledgement 624, or the access point 102 waits for a certain period of time after sending 622, either based on standardized timer or implementation-specific mechanism and then continues with the procedure.
  • Actual data transfer 626 between the user terminal and the access points 102, 104 is initiated e.g. after the user terminal carries out a random access procedure to the access point 102 and sets up an RRC connection accordingly.
  • the user terminal may perform neighbour cell measurements on different radio interfaces and indicate to an anchor node if a better cell is found which may trigger an RRC relocation procedure to the better cell (an anchor point may be changed as well). Additionally, based on the measurements, the user terminal may request an addition of a new RRC connection.
  • the access point providing the new RRC connection may be identified using a cellJD of the access point. It should be understood that the number of RRC connections and thus RRC entities may vary. For example, the user terminal may initially have simultaneous RRC connections with different access points. An RRC entity is kept for each connection. The user terminal may then later, due to mobility, have RRC connections only with one network entity or access point. In that case there is no need to maintain multiple RRC entities since all the connections of the user terminal are collocated in one access point and the network may use only one RRC entity to manage all connections.
  • Figure 7 illustrates an embodiment of an apparatus.
  • the figure illustrates a simplified example of an apparatus suitable for applying embodiments described above by means of Figure 5 (and 3).
  • the apparatus may be a user terminal or a part of a user terminal of a communications system.
  • the apparatus is depicted herein as an example illustrating some embodiments. It is apparent to a person skilled in the art that the apparatus may also comprise other functions and/or structures and not all described functions and structures are required. Although the apparatus has been depicted as one entity, different modules and memory may be implemented in one or more physical or logical entities.
  • the apparatus of the example includes a control circuitry 700 configured to control at least part of the operation of the apparatus.
  • the apparatus may comprise a memory 702 for storing data. Furthermore the memory may store software 704 executable by the control circuitry 800. The memory may be integrated in the control circuitry.
  • the apparatus comprises a transceiver 706.
  • the transceiver is operationally connected to the control circuitry 700. It may be connected to an antenna arrangement (not shown).
  • the software 704 may comprise a computer program comprising program code means adapted to cause t e control circuitry 700 of the apparatus to establish a first radio resource control connection to a first node apparatus; establish at least one second radio resource control connection to at least one second node apparatus and inform the at least one second node apparatus about the first node apparatus, the first node apparatus operating as a anchor point of radio resource control connections of the apparatus;
  • the apparatus may further comprise user interface 708 operationally connected to the control circuitry 700.
  • the user interface may comprise a display, a keyboard or keypad, a microphone and a speaker, for example.
  • Another example of an apparatus comprises means (700, 706, 704) for establishing a first radio resource control connection to a first node apparatus, means (700, 704, 706) for establishing at least one second radio resource control connection to at least one second node apparatus and means (700, 704, 706) for informing the at least one second node apparatus about the first node apparatus, the first node apparatus operating as a anchor point of radio resource control connections of the apparatus, means (700, 704, 706) for determining a need to release a radio resource control connection of the established first radio resource control connection and the at least one second radio resource control connection, and means (700, 704, 706) for checking statuses of other radio resource control connections among the established first radio resource control connection and the at least one second radio resource control connection and if the other radio resource control connections are released, means (700) for entering into
  • Figure 8 illustrates another embodiment of an apparatus.
  • the figure illustrates a simplified example of an apparatus applying embodiments described above by means of Figure 2 (and 3) and/or Figure 4 (and 3).
  • the apparatus may be a network element, an eNodeB or an access point or a part of an eNodeB or an access point of a communications system.
  • the apparatus is depicted herein as an example illustrating some embodiments. It is apparent to a person skilled in the art that the apparatus may also comprise other functions and/or structures and not all described functions and structures are required. Although the apparatus has been depicted as one entity, different modules and memory may be implemented in one or more physical or logical entities.
  • the apparatus of the example includes a control circuitry 800 configured to control at least part of the operation of the apparatus.
  • the apparatus may comprise a memory 802 for storing data.
  • the memory may store software 804 executable by the control circuitry 820.
  • the memory may be integrated in the control circuitry.
  • the apparatus comprises one or more transceivers 806.
  • the transceiver is operationally connected to the control circuitry 800. It may be connected to an antenna arrangement (not shown).
  • an apparatus comprising means (800, 804, 806) for coordinating one or more radio resource control connections to a user terminal, at least one of the one or more connections being maintained by the apparatus, means (802, 804) for maintaining mobile context information of the user terminal, the mobile context comprising information on the one or more radio resource control connections, means (800, 806) for receiving an indication to remove at least one of the one or more radio resource control connections to the user terminal, means (800, 804, 806) for checking the radio resource connection status of the user terminal and, if at least one other of the one or more radio resource connections to the user terminal exists, means (800, 804) for continuing maintaining the mobile context information of the user terminal.
  • an apparatus comprising means (800,806) for receiving a request to set up an radio resource control connection to a user terminal, the request comprising information on a node apparatus acting as a anchor point of radio resource control connections to the user terminal, means (800, 804, 806) for setting up an radio resource control connection to the user terminal, means (800, 806) for requesting information on the mobile context of the user terminal from the node apparatus, and means (800, 806) for receiving information on the mobile context of the user terminal from the node apparatus.
  • the software 804 may comprise a computer program comprising program code means adapted to cause the control circuitry 800 of the apparatus at least to: manage one or more radio resource control connections to a user terminal, at least one of the one or more connections being maintained by the apparatus; maintain mobile context information of the user terminal, the mobile context comprising information on the one or more radio resource control connections; receive an indication to remove at least one of the one or more radio resource control connections to the user terminal; check the radio resource connection status of the user terminal and if at least one other of the one or more radio resource connections to the user terminal exists; continue maintaining the mobile context information of the user terminal.
  • the software 804 may comprise a computer program comprising program code means adapted to cause the control circuitry 800 of the apparatus at least to: receive a request to set up an radio resource control RRC connection to a user terminal, the request comprising information on a node apparatus acting as a controller of radio resource control RRC connections to the user terminal; set up an radio resource control RRC connection to the user terminal: request information on the mobile context of the user terminal from the node apparatus; and receive information on the mobile context of the user terminal from the node apparatus.
  • the apparatus may further comprise interface circuitry 808 configured to connect the apparatus to other devices and network elements of communication system, for example to a core network.
  • the interface may provide a wired or wireless connection to the communication network.
  • the apparatus may be in connection with core network elements, access points, eNodeB's, and with other respective apparatuses of communication systems.
  • the apparatus of Figure 9 may comprise a remote control unit RCU 900, such as a host computer or a server computer, operatively coupled (e.g. via a wireless or wired network) to a remote radio head RRH 902 located in the base station.
  • RCU 900 such as a host computer or a server computer
  • RRH 902 remote radio head
  • at least some of the described processes may be performed by the RCU 900.
  • the execution of at least some of the described processes may be shared among the RRH 902 and the RCU 900.
  • the RCU 900 may generate a virtual network through which the RCU 900 communicates with the RRH 902.
  • virtual networking may involve a process of combining hardware and software network resources and network functionality into a single, software-based administrative entity, a virtual network.
  • Network virtualization may involve platform virtualization, often combined with resource virtualization.
  • Network virtualization may be categorized as external virtual networking which combines many networks, or parts of networks, into the server computer or the host computer (e.g. to the RCU). External network virtualization is targeted to optimized network sharing. Another category is internal virtual networking which provides network-like functionality to the software containers on a single system. Virtual networking may also be used for testing the terminal device.
  • the virtual network may provide flexible distribution of operations between the RRH and the RCU.
  • any digital signal processing task may be performed in either the RRH or the RCU and the boundary where the responsibility is shifted between the RRH and the RCU may be selected according to implementation.
  • the embodiments are not, however, restricted to the system and apparatuses given above as an example but a person skilled in the art may apply the solution to other communication systems and apparatuses provided with necessary properties.
  • an example of a suitable communications system is the 5G concept.
  • the proposed solutions may enable consistent operation and configuration management between network and user terminal especially if the user terminal connections to network include multi-connectivity with same or different radio interface (namely in 5G,
  • the apparatuses or controllers able to perform the above-described steps may be implemented as an electronic digital computer, which may comprise a working memory (RAM), a central processing unit (CPU), and a system clock.
  • the CPU may comprise a set of registers, an arithmetic logic unit, and a controller.
  • the controller is controlled by a sequence of program instructions transferred to the CPU from the RAM.
  • the controller may contain a number of microinstructions for basic operations.
  • the implementation of microinstructions may vary depending on the CPU design.
  • the program instructions may be coded by a programming language, which may be a high-level programming language, such as C, Java, etc. , or a low-level programming language, such as a machine language, or an assembler.
  • the electronic digital computer may also have an operating system, which may provide system services to a computer program written with the program instructions.
  • the term 'circuitry' refers to all of the following: (a) hardware- only circuit implementations, such as implementations in only analogue and/or digital circuitry, and (b) combinations of circuits and software (and/or firmware), such as (as applicable): (i) a combination of processor(s) or (ii) portions of processor(s)/software including digital signal processor(s), software, and memory(ies) that work together to cause an apparatus to perform various functions, and (c) circuits, such as a
  • circuitry would also cover, for example and if applicable to the particular element, a baseband integrated circuit or applications processor integrated circuit for a mobile phone or a similar integrated circuit in a server, a cellular network device, or another network device.
  • An embodiment provides a computer program embodied on a distribution medium, comprising program instructions which, when loaded into an electronic apparatus, are configured to control the apparatus to execute the embodiments described above.
  • the distribution medium may be a non-transitory distribution medium.
  • the computer program may be in source code form, object code form, or in some intermediate form, and it may be stored in some sort of carrier, which may be any entity or device capable of carrying the program.
  • Such carriers include a record medium, computer memory, read-only memory, and a software distribution package, for example.
  • the computer program may be executed in a single electronic digital computer or it may be distributed amongst a number of computers.
  • the apparatus may also be implemented as one or more integrated circuits, such as application-specific integrated circuits ASIC.
  • Other hardware embodiments are also feasible, such as a circuit built of separate logic components.
  • a hybrid of these different implementations is also feasible.

Landscapes

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

Abstract

Dans un mode de réalisation, l'invention concerne un appareil conçu pour effectuer au moins les étapes consistant : à coordonner une ou plusieurs connexions de commande de ressources radio avec un terminal utilisateur, au moins une de la ou des connexions étant maintenue par l'appareil ; à maintenir des informations de contexte mobile du terminal utilisateur, le contexte mobile comportant des informations sur la ou les connexions de commande de ressources radio ; à recevoir une indication visant à supprimer au moins une de la ou des connexions de commande de ressources radio au terminal d'utilisateur; à vérifier l'état de connexion de ressource radio du terminal utilisateur et si au moins une autre de la ou des connexions de ressources radio au terminal d'utilisateur existe, et continuer à maintenir les informations de contexte mobile du terminal utilisateur.
PCT/EP2015/075705 2015-11-04 2015-11-04 Gestion de connexions WO2017076441A1 (fr)

Priority Applications (2)

Application Number Priority Date Filing Date Title
PCT/EP2015/075705 WO2017076441A1 (fr) 2015-11-04 2015-11-04 Gestion de connexions
EP15793744.2A EP3372048A1 (fr) 2015-11-04 2015-11-04 Gestion de connexions

Applications Claiming Priority (1)

Application Number Priority Date Filing Date Title
PCT/EP2015/075705 WO2017076441A1 (fr) 2015-11-04 2015-11-04 Gestion de connexions

Publications (1)

Publication Number Publication Date
WO2017076441A1 true WO2017076441A1 (fr) 2017-05-11

Family

ID=54540034

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/EP2015/075705 WO2017076441A1 (fr) 2015-11-04 2015-11-04 Gestion de connexions

Country Status (2)

Country Link
EP (1) EP3372048A1 (fr)
WO (1) WO2017076441A1 (fr)

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013040070A1 (fr) * 2011-09-12 2013-03-21 Ntt Docomo, Inc. Procédé et appareil au niveau des couches physiques et liaisons pour communications mobiles
US20130130693A1 (en) * 2011-11-23 2013-05-23 Omar Salvador User equipment signaling traffic reduction
WO2016029932A1 (fr) * 2014-08-26 2016-03-03 Nokia Solutions And Networks Oy Accès à un réseau basé sur une diffusion
WO2016087708A1 (fr) * 2014-12-05 2016-06-09 Nokia Technologies Oy Réduction de latence pour équipement utilisateur à trafic interactif par salves

Family Cites Families (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
EP2508025B1 (fr) * 2010-09-28 2016-01-06 BlackBerry Limited Gestion de connexion de réseau résidentiel/d'entreprise et scénarios de repli à commutation de circuits (csfb)
EP2557890B1 (fr) * 2011-08-12 2019-07-17 BlackBerry Limited Messagerie simplifiée d'ue+enb
US9723651B2 (en) * 2014-11-10 2017-08-01 Qualcomm Incorporated Enhanced connection management for multiple access networks
US10667321B2 (en) * 2015-02-09 2020-05-26 Intel IP Corporation Evolved Node-B, user equipment, and methods for transition between idle and connected modes

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2013040070A1 (fr) * 2011-09-12 2013-03-21 Ntt Docomo, Inc. Procédé et appareil au niveau des couches physiques et liaisons pour communications mobiles
US20130130693A1 (en) * 2011-11-23 2013-05-23 Omar Salvador User equipment signaling traffic reduction
WO2016029932A1 (fr) * 2014-08-26 2016-03-03 Nokia Solutions And Networks Oy Accès à un réseau basé sur une diffusion
WO2016087708A1 (fr) * 2014-12-05 2016-06-09 Nokia Technologies Oy Réduction de latence pour équipement utilisateur à trafic interactif par salves

Also Published As

Publication number Publication date
EP3372048A1 (fr) 2018-09-12

Similar Documents

Publication Publication Date Title
US20180310241A1 (en) Providing service
US20230254684A1 (en) Communication of user terminal having multiple subscription identities
US20220330026A1 (en) Counter measures for attacking messages
US20220322487A1 (en) Low-latency communication with discontinuous transmission
US20240204848A1 (en) Method and apparatus for partial csi reporting
US20240049091A1 (en) Determining handover command transmission based on survival time
EP2826301B1 (fr) Appareil et procédé de transfert intercellulaire entre différents réseaux porteurs
US20230232455A1 (en) Enhanced carrier selection
WO2017076441A1 (fr) Gestion de connexions
US20230397042A1 (en) Data arrival indication
KR20200089704A (ko) 무선 통신 시스템 내의 간섭을 식별하는 방법 및 장치
WO2017081360A1 (fr) Multi-connectivité de dispositif de terminal dans un système cellulaire
FI130523B (en) Improvements in resource reservation
US20230239753A1 (en) Reconfiguration failure handling for cpac
US20230388890A1 (en) Handover of a communication session
EP4391649A1 (fr) Procédure de transfert conditionnel
US20240090072A1 (en) Terminal Redirection
US20240172319A1 (en) Adjusting communication gaps related to receiving paging messages
US20230379975A1 (en) Restricting a random access procedure
US11356902B2 (en) Control of handovers over different connections of a hybrid access user terminal
WO2022262969A1 (fr) Amélioration du transfert de données par support divisé (split bearer)
WO2023160973A1 (fr) Gestion de conflit entre cho et changement conditionnel de spcell
EP4338329A1 (fr) Coordination entre ue dans des transmissions de diffusion de groupe
WO2024068131A1 (fr) Accès retardé à une cellule primaire d'un groupe de cellules secondaires
FI20215076A1 (en) Improved carrier selection

Legal Events

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

Ref document number: 15793744

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

WWE Wipo information: entry into national phase

Ref document number: 2015793744

Country of ref document: EP