WO2016003113A1 - Procédé et système pour commander une continuité de service dans un système de communication sans fil - Google Patents

Procédé et système pour commander une continuité de service dans un système de communication sans fil Download PDF

Info

Publication number
WO2016003113A1
WO2016003113A1 PCT/KR2015/006498 KR2015006498W WO2016003113A1 WO 2016003113 A1 WO2016003113 A1 WO 2016003113A1 KR 2015006498 W KR2015006498 W KR 2015006498W WO 2016003113 A1 WO2016003113 A1 WO 2016003113A1
Authority
WO
WIPO (PCT)
Prior art keywords
base station
handover
terminal
bearer
service
Prior art date
Application number
PCT/KR2015/006498
Other languages
English (en)
Korean (ko)
Inventor
정상수
Original Assignee
삼성전자 주식회사
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 삼성전자 주식회사 filed Critical 삼성전자 주식회사
Publication of WO2016003113A1 publication Critical patent/WO2016003113A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/02—Buffering or recovering information during reselection ; Modification of the traffic flow during hand-off
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/08—Reselecting an access point
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W36/00—Hand-off or reselection arrangements
    • H04W36/34—Reselection control
    • H04W36/38—Reselection control by fixed network equipment

Definitions

  • Embodiments of the present disclosure relate to a method and apparatus for controlling service continuity when a terminal receives a specific service in a wireless communication system.
  • an embodiment of the present disclosure relates to a control method and apparatus for supporting service continuity when a handover occurs while a user terminal receives a service having a specific QoS requirement.
  • a 5G communication system or a pre-5G communication system is called a system after a 4G network (Beyond 4G Network) or a system after an LTE system (Post LTE).
  • 5G communication systems are being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Gigabit (60 GHz) band).
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • FD-MIMO massive array multiple input / output
  • Array antenna, analog beam-forming, and large scale antenna techniques are discussed.
  • 5G communication systems have advanced small cells, advanced small cells, cloud radio access network (cloud RAN), ultra-dense network (ultra-dense network) , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, Coordinated Multi-Points (CoMP), and interference cancellation
  • cloud RAN cloud radio access network
  • D2D Device to Device communication
  • D2D Device to Device communication
  • CoMP Coordinated Multi-Points
  • Hybrid FSK and QAM Modulation FQAM
  • SWSC Slide Window Superposition Coding
  • ACM Advanced Coding Modulation
  • FBMC Fan Bank Multi Carrier
  • NOMA non orthogonal multiple access
  • SCMA sparse code multiple access
  • IoT Internet of Things
  • IoE Internet of Everything
  • M2M machine to machine
  • MTC Machine Type Communication
  • IT intelligent Internet technology services can be provided that collect and analyze data generated from connected objects to create new value in human life.
  • IoT is a field of smart home, smart building, smart city, smart car or connected car, smart grid, health care, smart home appliances, advanced medical services, etc. through convergence and complex of existing information technology (IT) technology and various industries. It can be applied to.
  • wireless communication systems have been developed to provide voice services while guaranteeing user activity.
  • wireless communication systems are gradually expanding to not only voice but also data services, and to the extent that they can provide high speed data services.
  • a shortage of resources and users require faster services, and thus, a more advanced wireless communication system is required.
  • LTE Long Term Evolution
  • 3GPP The 3rd Generation Partnership Project
  • LTE is a technology that implements high-speed packet-based communication with a transmission rate of up to 100 Mbps.
  • various methods are discussed.
  • the network structure can be simplified to reduce the number of nodes located on the communication path, or the wireless protocols can be as close to the wireless channel as possible.
  • An embodiment of the present invention is to provide a method and apparatus for controlling service continuity when a terminal receives a specific service in a wireless communication system.
  • An embodiment of the present invention also provides a control method and apparatus for supporting service continuity when a handover occurs while a user terminal receives a service having a specific Quality of Service (QoS) requirement.
  • QoS Quality of Service
  • a handover target base station identifier for a terminal in a method for supporting handover of a core network node, receiving a handover request including a handover target base station identifier for a terminal, the handover target Determining, by the base station, whether the terminal supports a quality of service (QoS) condition for a service currently in use, and if the handover target base station does not support a QoS condition for a service currently used by the terminal, And mapping a QCI for a service and transmitting a handover progress message including the QCI mapping information to a core node of a handover target of the terminal.
  • QoS quality of service
  • the handover target base station identifier for the communication unit and the terminal for communicating with at least one network node Receives a handover request, the handover target base station determines whether the terminal supports a Quality of Service (QoS) condition for the service currently in use, the handover target base station for the service currently being used by the terminal If it does not support the QoS condition, the control unit for mapping the QCI for the currently used service (mapping), and transmits a handover progress message including the QCI mapping information to the handover target core network node of the terminal; It provides a device comprising a.
  • QoS Quality of Service
  • the method for supporting a handover of a base station determining whether a handover is required for a user terminal using a specific bearer, if it is determined that the handover is necessary, And selecting a handover target base station supporting the specific bearer and performing a handover procedure for the terminal with respect to the selected handover target base station.
  • the handover method of the terminal using a specific bearer to communicate with the base station, reporting the cell measurement result to the base station and based on the measurement result And receiving a handover request message including handover target base station information from the base station, wherein the handover target base station supports the specific bearer being used by the terminal.
  • the terminal in the method for supporting handover of a core network node, determining whether a horse uses a bearer having a specific QCI (QoS Class Identifier) value, and the terminal is preset If using a bearer having a specific QCI value, generating handover restriction information for the terminal and transmitting the generated handover restriction information to a serving base station of the terminal;
  • the terminal provides at least one neighbor base station information capable of supporting a bearer having the specific QCI value to the terminal.
  • a communication unit and a terminal communicating with at least one network node have a specific QCI (QoS Class Identifier) value. Determining whether to use a bearer, if the terminal is using a bearer having a predetermined specific QCI value, generates handover restriction information for the terminal, and transmits the generated handover restriction information to the serving base station of the terminal And a control unit configured to control the control unit, wherein the handover restriction information includes at least one neighbor base station information capable of supporting a bearer having the specific QCI value.
  • QCI QoS Class Identifier
  • the core network A control unit configured to receive handover restriction information for the terminal from a node, determine whether the terminal requires handover, and control to select a base station to be handed over to the terminal based on the received handover restriction information; It provides a device comprising a.
  • the QoS of the service when handover is required for a user terminal having a specific QoS requirement, is limited by limiting candidates of the base station or area to be handed over to those that can satisfy the same QoS requirements. It can be guaranteed continuously.
  • FIG. 1 is a view showing the structure of a communication system according to an embodiment of the present disclosure.
  • FIG. 2 is a table illustrating QoS parameters that can be used in an operator network.
  • FIG. 3 is a diagram illustrating an operation of an operator network node according to an embodiment of the present invention.
  • FIG. 4 is a diagram illustrating an operation of an operator network node according to a second embodiment of the present invention.
  • 5 is a diagram illustrating information exchange between base stations.
  • FIG. 6 is a diagram illustrating the operation of an operator network node according to a third embodiment of the present invention.
  • FIG. 7 is a diagram illustrating an operation of an operator network node that occurs when a user terminal switches from an idle mode to a connected mode according to a fourth embodiment of the present invention.
  • FIG. 8 is a diagram illustrating a core network node according to an embodiment of the present invention.
  • FIG. 9 is a diagram illustrating a base station according to an embodiment of the present invention.
  • FIG. 10 is a view showing a terminal according to an embodiment of the present invention.
  • each block of the flowchart illustrations and combinations of flowchart illustrations may be performed by computer program instructions. Since these computer program instructions may be mounted on a processor of a general purpose computer, special purpose computer, or other programmable data processing equipment, those instructions executed through the processor of the computer or other programmable data processing equipment may be described in flow chart block (s). It creates a means to perform the functions. These computer program instructions may be stored in a computer usable or computer readable memory that can be directed to a computer or other programmable data processing equipment to implement functionality in a particular manner, and thus the computer usable or computer readable memory. It is also possible for the instructions stored in to produce an article of manufacture containing instruction means for performing the functions described in the flowchart block (s).
  • Computer program instructions may also be mounted on a computer or other programmable data processing equipment, such that a series of operating steps may be performed on the computer or other programmable data processing equipment to create a computer-implemented process to create a computer or other programmable data. Instructions for performing the processing equipment may also provide steps for performing the functions described in the flowchart block (s).
  • each block may represent a portion of a module, segment, or code that includes one or more executable instructions for executing a specified logical function (s).
  • logical function e.g., a module, segment, or code that includes one or more executable instructions for executing a specified logical function (s).
  • the functions noted in the blocks may occur out of order.
  • the two blocks shown in succession may in fact be executed substantially concurrently, or the blocks may sometimes be executed in the reverse order, depending on the corresponding function.
  • ' ⁇ part' used in the present embodiment refers to software or a hardware component such as an FPGA or an ASIC, and ' ⁇ part' performs certain roles.
  • ' ⁇ ' is not meant to be limited to software or hardware.
  • ' ⁇ Portion' may be configured to be in an addressable storage medium or may be configured to play one or more processors.
  • ' ⁇ ' means components such as software components, object-oriented software components, class components, and task components, and processes, functions, properties, procedures, and the like. Subroutines, segments of program code, drivers, firmware, microcode, circuits, data, databases, data structures, tables, arrays, and variables.
  • the functionality provided within the components and the 'parts' may be combined into a smaller number of components and the 'parts' or further separated into additional components and the 'parts'.
  • the components and ' ⁇ ' may be implemented to play one or more CPUs in the device or secure multimedia card.
  • the present technology targeting the LTE system may be applied to a UTRAN / GERAN system having a similar system structure.
  • the ENB (RAN node) may be replaced by the RNC / BSC, the S-GW may be omitted or included in the SGSN, and the P-GW may correspond to the GGSN.
  • the EPS bearer concept of the LTE system may correspond to the PDP context of the UTRAN / GERAN system.
  • a handover occurs while the user terminal is receiving a service having a specific QoS requirement, it is necessary to keep the service that the user terminal was receiving. In the area subject to handover, it is difficult to support service continuity for the user terminal unless they have the same QoS requirements. If service continuity is not supported when a user terminal occurs in the user terminal, the user experience service quality is lowered, and in particular, when the service is a public safety net service or an emergency service, the basic requirements of the service cannot be satisfied.
  • the communication system may be a mobile communication system based on LTE.
  • a radio access network of an LTE mobile communication system includes a next-generation base station (Evolved Node B, EUTRAN, hereinafter referred to as ENB or Node B) 130, a mobility management entity (MME) 150, and It consists of S-GW (Serving-Gateway) (140).
  • EUTRAN Next-generation base station
  • MME mobility management entity
  • the user equipment (hereinafter referred to as UE) 100 is connected to the external network through the ENB 130 and the S-GW 140 and the P-GW (P-GW) 160.
  • the user terminal In order to transmit and receive data through the PGW, the user terminal needs to create a PDN connection, and one PDN connection may include one or more EPS bearers.
  • AF (Application Function) 110 is a device for exchanging information associated with the application at the user (application) level.
  • the PCRF 120 is a device for controlling a policy related to a quality of service (QoS) of a user, and a policy and charging control (PCC) rule corresponding to the policy is transmitted to the P-GW 160. Is applied.
  • QoS quality of service
  • PCC policy and charging control
  • the ENB 130 is a Radio Access Network (RAN) node and corresponds to the RNC of the UTRAN system and the BSC of the GERAN system.
  • the ENB 130 is connected to the UE 100 through a radio channel and performs a role similar to that of the existing RNC / BSC.
  • RAN Radio Access Network
  • the S-GW 140 is a device that provides a data bearer, and generates or removes a data bearer under the control of the MME 150.
  • the MME 150 is a device for various control functions.
  • One MME 150 may be connected to a plurality of base stations.
  • PCRF 120 Policy Charging and Rules Function 120 is an entity that collectively controls QoS and billing for traffic.
  • FIG. 2 is a table illustrating QoS parameters that can be used in an operator network.
  • QoS parameters are divided by QCI (QoS Class Index), and resource allocation type (priority), packet delay rate (PDB), and packet error rate (packet error) for each QCI. loss rate) and representative services.
  • QCI QoS Class Index
  • resource allocation type priority
  • PDB packet delay rate
  • packet error rate packet error rate
  • representative services For example, an EPS bearer using QCI No. 1 is used for a service having a low PDB value and a relatively high priority, for example, a voice call service.
  • QCI 65 is commonly used for Mission Critical Push To Talk (MCPTT) voice services and can be used to provide public safety services in emergency or disaster situations.
  • MCPTT Mission Critical Push To Talk
  • the EPS bearer for MCPTT using QCI 65 has a low priority and a very small PDB value.
  • the EPS bearer for the MCPTT / nMCPTT service will be considered to use 65/66 as the QCI value, but this is for convenience of description and the main points of the embodiments of the present invention. The same may be applied even when the EPS bearer for the MCPTT / nMCPTT service uses different QCI values, for example, 11/12.
  • the user terminal is receiving a service with specific QoS requirements (ie has an EPS bearer for a specific QCI).
  • a handover has occurred according to the location or channel state of the user terminal, but it may not be possible to support the EPS bearer having the QCI in a base station or an area (cell) that may be the target of the handover.
  • a user terminal is using an EPS bearer for MCPTT using QCI 65 in an E-UTRAN network, but a handover has occurred, and a base station or area (cell) that can be a target of handover in the vicinity is a UTRAN network.
  • the UTRAN network may not support the EPS bearer whose QCI is 65.
  • EPS bearer using QCI 65 cannot be used after handover, so it is difficult to continuously support the service.
  • the core network performs mapping to the QCI having the QoS parameter most similar to the existing QoS parameter, and accordingly the EPS bearer context is set to the new QCI. It is renewed to provide service continuously.
  • the service used by the user terminal is MCPTT (that is, when using the EPS bearer with the QCI of 65). It is for explaining the operation based on the service having, and the main gist of the present embodiment is not limited to the EPS bearer of the MCPTT service and QCI 65.
  • a communication system includes a user terminal (UE) 310, a base station (eNB) 320, a radio network controller (RNC) 330, a mobility management entity (MME) 340. And a serving GPRS support node 350 (SGSN).
  • UE user terminal
  • eNB base station
  • RNC radio network controller
  • MME mobility management entity
  • SGSN serving GPRS support node 350
  • the original base station is set to the eNB, the handover target base station to the RNC, the one core network node to the MME, the handover target core network node to SGSN, but this is only one embodiment of the entities constituting the network, the scope of the embodiment It is not limited to this.
  • the base station and the handover target base station may be an eNB, RNC, BSC.
  • the core network node and the handover target core network node may be MME or SGSN.
  • the user terminal 310 receives a service having a specific quality of service (QoS) requirement and, accordingly, has an EPS bearer having a specific QoS Class Identifier (QCI) (S310).
  • QoS quality of service
  • the service may be an MCPTT or a Non Mission Critical Push To Talk Voice (nMCPTT) service. Therefore, the QCI for the service may be 65 or 66.
  • the original base station (eNB or RNC / BSC) 320 recognizes that handover is required for the user terminal.
  • the original base station sends a handover required message to the core network node (MME or SGSN, 340), which includes an identifier of the base station 330 or the area (cell) to be handovered ( S320).
  • MME core network node
  • SGSN GPRS Support Node
  • the core network node (MME or SGSN) 340 After receiving the handover request, the core network node (MME or SGSN) 340 checks an EPS bearer context (EPS bearer context) that the user terminal uses or a service being used by the user terminal (S330). In addition, the core network node 340 is based on the identifier information of the base station 330 or the area (cell) that is the target of the handover received from the original base station 310, in the handover target base station or area (cell) It is checked whether the user terminal 310 supports the QoS requirement for the service being used or the QCI of the EPS bearer for supporting the service (S330).
  • EPS bearer context EPS bearer context
  • the service being used by the user terminal 310 may be MCPTT or nMCPTT, so the QCI of the EPS bearer may be 65 or 66.
  • the core network node 340 may determine whether QCI 65 or 66 is supported in the base station 330 or the cell (cell) to be handed over. If the QoS requirement or QCI for the original user terminal 310 service is not supported in the base station or the area (cell) to be handed over, the core network node 340 performs a QoS mapping operation. At this time, the QoS mapping operation may be performed according to the local configuration of the core network node.
  • the mapping operation is to perform mapping in the core network node 340 to a QCI having a QoS parameter most similar to an existing QoS parameter for a service currently used by the terminal. This is to continuously provide services by updating EPS bearer context with QCI.
  • the QoS parameter may include a QoS class indicator (QCI), an allocation and retention priority (ARP), a guaranteed bit rate (GBR), or an MBR.
  • QCI QoS class indicator
  • ARP allocation and retention priority
  • GRR guaranteed bit rate
  • MBR MBR
  • the configuration information of the core network node 340 is set such that an EPS bearer having a QCI of 65 is mapped to an EPS bearer having a QCI of 1, and an EPS bearer having a QCI of 64 is mapped to an EPS bearer having a QCI of 1. It may be (S330).
  • the original core network node 340 may transmit a message for handover progress to the handover target core network node 350.
  • the message for the handover process may be a forward relocation request message.
  • This message contains the EPS bearer context according to the result mapped in step S330 above.
  • the handover target core network node 350 may transmit a message for requesting handover to the handover target base station 330.
  • the message for handover may be a relocation request or a handover request message.
  • This message contains the EPS bearer context according to the result mapped in step S330.
  • the handover target base station node 330 transmits a response message to the handover target core network node 350.
  • This message contains the EPS bearer context according to the result mapped in step S330 above.
  • step S330 If it is determined in step S330 that the original core network node 340 supports the service QoS requirement for the handover user terminal 310 or the EPS bearer for supporting the handover, the process proceeds to step S340 without a separate mapping operation. A message may be sent for over progress.
  • the original core network node 340 performs mapping for QoS parameters.
  • the mapping to the QoS parameter may be performed in the handover target core network node 350. That is, in S330 of FIG. 3, the original core network node 340 may transmit a message for handover progress to the handover target core network node 350 based on the original EPS bearer context without performing QoS mapping.
  • the message for the handover process may be a forward relocation request message.
  • the handover target core network node 350 that receives the message for handover progress may support QoS parameters for the EPS bearer received from the original core network node 340 in the base station or cell (cell) to which the handover is to be performed.
  • the handover target core network node 350 may perform QoS mapping.
  • the QoS mapping operation is the same as described in S330. After mapping, it may operate as described in S350 and S360.
  • a process for modifying the EPS bearer context may be additionally performed.
  • the core network node may transmit a UE context setup message for the changed EPS bearer context to the base station.
  • the base station and the terminal may perform an RRC connection reconfiguration procedure based on the UE context setup message, and may apply the changed EPS bearer context through this.
  • the PDP context may be used instead of the EPS bearer.
  • the second embodiment of the present invention selects a target base station or area (cell) when a handover occurs for a user terminal having a service having a specific QoS requirement (that is, having an EPS bearer having a specific QCI).
  • a specific QoS requirement that is, having an EPS bearer having a specific QCI.
  • FIG. 4 is a diagram illustrating an operation of an operator network node according to a second embodiment of the present invention.
  • the service used by the user terminal 410 is MCPTT (that is, when using an EPS bearer with a QCI of 65), but this is based on a service having a specific QoS requirement.
  • MCPTT that is, when using an EPS bearer with a QCI of 65
  • a main point of the present embodiment is not limited to the EPS bearer having the MCPTT service and the QCI of 65.
  • the user terminal 410 is using the MCPTT or nMCPTT service, and therefore has a EPS bearer with a QCI of 65 or 66 (S410).
  • the base station 420 may perform a measurement for measuring a channel state of the user terminal (S420).
  • the base station 420 determines that handover is necessary based on the measurement result, and selects a base station or an area (cell) to be the handover target (S430).
  • the base station 420 if the user terminal 410 is using an EPS bearer having a predetermined specific QCI value, the base station or area (cell) to be a handover target to search the neighbor cell list and support the specific QCI value Can be selected. For example, when the user terminal 410 is using an EPS bearer of QCI 65 or 66, the base station 420 searches for a neighbor cell list (NCL) to determine whether the EPS bearer of QCI 65 or 66 is supported. .
  • NCL neighbor cell list
  • the base station 420 may perform a handover process by selecting a base station or an area (cell) capable of supporting an EPS bearer of QCI 65 or 66. That is, in the present embodiment, the base station 420 is storing the NCL including information indicating whether the neighboring base station or region (cell) can support the EPS bearer of QCI 65/66, and selects the target of the handover based on this. do. Whether the QCI supports the EPS bearer having 65 or 66 may include determining whether it can support the MCPTT or nMCPTT service.
  • neighbor base station information may be stored to determine whether the neighbor base station supports an EPS bearer having a QCI of 65 or 66.
  • neighbor base station information may be stored through information exchange between base stations.
  • the neighboring base station having the highest QoS similarity may be selected as the base station for handover. This may also be applied to the following third and fourth embodiments.
  • the service used by the user terminal is MCPTT (that is, when using an EPS bearer with QCI of 65), but this is based on a service based on a service having a specific QoS requirement.
  • MCPTT that is, when using an EPS bearer with QCI of 65
  • the main points of the present embodiment are not limited to the EPS bearer having the MCPTT service and the QCI of 65.
  • the base station 510 If the base station 510 needs X2 connection with another base station 520, it transmits an X2 setup request to the base station (S510).
  • This message includes information indicating whether the MCPTT or nMCPTT service can be supported, that is, whether the QCI supports the EPS bearer having 65 or 66.
  • the neighbor base station 520 receiving this stores whether the other base station supports MCPTT or nMCPTT in the NCL (S520).
  • the neighbor base station 520 transmits a response message for the request to the base station 510 (S530).
  • the response message may be an X2 configuration response message.
  • the X2 configuration response message may include information indicating whether the neighbor base station 520 supports MCPTT or nMCPTT.
  • the base station 510 stores whether the neighbor base station supports MCPTT or nMCPTT in the NCL.
  • the base station or area (cell) to which the handover is to be performed when selecting the method to exclude those that can not support the EPS bearer having the QCI.
  • the difference from the second embodiment is that the base station node does not perform the operation based on the NCL, but performs the operation based on a HRL (Handover Restriction List) received from the MME (or SGSN).
  • HRL Heandover Restriction List
  • FIG. 6 is a diagram illustrating the operation of an operator network node according to a third embodiment of the present invention.
  • the service used by the user terminal is MCPTT (that is, when using an EPS bearer with QCI of 65), but this is based on a service based on a service having a specific QoS requirement.
  • the main points of the present embodiment are not limited to the EPS bearer having the MCPTT service and the QCI of 65.
  • the user terminal 610 is registered in the operator network, and has not set up an EPS bearer for MCPTT or nMCPTT during the basic registration procedure (S610).
  • the user terminal 610 and the operator's network set an EPS bearer for MCPTT or nMCPTT service, that is, an EPS bearer having a QCI of 65 or 66 according to the service request (S620).
  • EPS bearer is configured for the user terminal 610, it can be seen that the QCI is 65 or 66 (S630). Therefore, when generating a handover restriction list (HRL) for the user terminal, the base station or region (cell) that does not support the MCPTT or nMCPTT of the base station or region (cell) that is the target of the handover is excluded (S630). That is, the base station or area (cell) that does not support the EPS bearer with the QCI of 65 or 66 is set to be excluded from the handover target.
  • HRL handover restriction list
  • the core network node 630 is UTRAN as a prohibited RAT (Radio Access Technology) of the HRL. Set.
  • the HRL generated by the core network node 630 is transmitted to the base station 620 (S640).
  • the generated HRL may be transmitted through an S1_AP or Iu message.
  • the message may be one of a downlink NAS transport and an E-RAB setup request.
  • the base station 620 may store the received HRL.
  • the base station 620 selects a base station or an area (cell) to be subjected to handover based on the HRL received from the core network node 620 (S650).
  • FIG. 7 is a diagram illustrating an operation of an operator network node that occurs when a user terminal switches from an idle mode to a connected mode according to a fourth embodiment of the present invention.
  • the service used by the user terminal is MCPTT (that is, when using an EPS bearer with QCI of 65), but this is based on a service based on a service having a specific QoS requirement.
  • the main points of the present embodiment are not limited to the EPS bearer having the MCPTT service and the QCI of 65.
  • the user terminal 710 transmits a request message and a service request message to the core network node 730 in order to switch to a connection state for receiving a service from an idle state (S710).
  • the core network node (MME or SGSN, 730) of the operator's network may know that the user terminal has an EPS bearer with a QCI of 65 or 66 according to the EPS bearer context of the user terminal 710 (S720).
  • the core network node 730 when generating the HRL for the user terminal 710, the core network node 730 does not support MCPTT or nMCPTT among base stations or areas (cells) that are subject to handover, that is, QCI is 65 or 66.
  • a base station or an area (cell) not supporting the EPS bearer is set to be excluded from the handover target (S720).
  • the core network node configures the UTRAN as a prohibited RAT (Radio Access technology) of the HRL.
  • RAT Radio Access technology
  • the HRL generated by the core network node 730 is transmitted to the base station 720 through the S1_AP or Iu message (S730).
  • the message may be an Initial context setup request message.
  • the base station 720 selects a base station or an area (cell) to be subjected to handover based on the HRL received from the core network node 730 (S740).
  • the fifth embodiment of the present invention by determining the connection mode and the detailed connection state of the user terminal in consideration of the traffic characteristics of the user terminal, a method of reducing the battery consumption of the user terminal, increasing the availability of the operator network added To present. More specifically, if the user terminal has completed the data transmission and reception, the probability of the subsequent data traffic transmission is low, it is notified to the base station control node may cause a transition to a low battery consumption state.
  • the layer on which an operation is performed is changed (for example, a request message for changing a connection state from a NAS instead of RRC) or used for a request
  • the message may be changed (for example, a UE Assistance Information message or an RRC Release Request message instead of the SCRI message of the RRC layer), or some steps / operations of the embodiments of the present invention may be omitted or the order may be changed.
  • the user terminal may transmit a request message for changing the connection state to the base station.
  • This operation according to embodiments of the present invention, the upper layer (traffic monitoring unit, application synchronizer, or NAS layer) has finished sending and receiving traffic, the PS data session has ended, user inactivity, or RRC disconnection is required It may be performed when at least one or more pieces of information for notifying the communication to the communication control unit (RRC layer).
  • RRC layer communication control unit
  • determining whether to notify one or more of the above information may be determined by embodiments of the present invention.
  • the user terminal may use the UE Assistance Information message as a request message, which includes information indicating that the transmission and reception of traffic has ended, the PS data session has ended, the RRC connection needs to be disconnected, user inactivity, or low power consumption is required.
  • One or more may be included.
  • the base station may transmit an operation for releasing the RRC connection to the user terminal, that is, an RRC connection release message to the user terminal.
  • the base station may transmit a request message to release the UE context to the MME. Meanwhile, the UE Assistance Information may be replaced with an RRC connection release request message.
  • the information may be included in a header or a control element used when the user terminal transmits a user plane data packet, rather than a separate control message transmitted by the user terminal to the base station. Meanwhile, the base station may delay performing the operation of releasing the RRC connection until the user plane data transmission and reception for the user terminal is terminated.
  • the user terminal may transmit a request message for changing the connection state to the MME.
  • the MME may transmit a request message for changing the connection state.
  • NAS layer communication control unit
  • determining whether to notify one or more of the above information may be determined by embodiments of the present invention.
  • the user terminal may use a NAS message as a request message, and the message may include one or more pieces of information indicating that the transmission and reception of the traffic has ended, the PS data session has ended, the RRC connection needs to be disconnected, user inactivity, or low power consumption is required. This may be included.
  • the NAS message may be an EMM status message, indicating that the traffic transmission and reception is terminated, the PS data session is terminated, the RRC connection needs to be released, user inactivity, or low power consumption is required.
  • the information may be included in the EMM cause information element.
  • RRC connection release to the user terminal may mean that the MME releases the logical connection associated with the user terminal.
  • the MME may transmit a UE context release command message to the base station.
  • the message may include one of information indicating that traffic transmission and reception is terminated due to disconnection, PS data session is terminated, RRC connection release is required, user inactivity, or low power consumption is required.
  • the base station If the base station receives the UE context release command message from the MME, the base station performs an operation for releasing the RRC connection for the user terminal. If the message received by the base station includes information indicating that the transmission and reception of the traffic is terminated, the PS data session is terminated, the RRC connection needs to be released, user inactivity, or low power consumption is required, the base station is a user terminal. After waiting for all user plane data transmission and reception to, the RRC connection may be released.
  • the user terminal may transmit the WLAN through a system information block (SIB) or an RRC connection reconfiguration (RRC message) transmitted by a base station (E-UTRAN or UTRAN).
  • SIB system information block
  • RRC message RRC connection reconfiguration
  • E-UTRAN or UTRAN E-UTRAN or UTRAN
  • Offloading control information ie, RAN rule
  • the WLAN offloading control information includes a list of WLANs to which the user terminal can connect, various parameters (eg, signal strength, congestion, offloading preference indicator, etc.) that the user terminal can use to select the WLAN or determine whether to offload traffic. Includes timer values to apply when performing an offloading operation.
  • the user terminal camps in the E-UTRAN or the UTRAN to receive the service and receives the information and is in operation, and may move to the base station or the area that does not provide the information.
  • a user terminal receives a service from a Release-12 base station capable of transmitting a System Information Block (SIB) or an RRC message including the WLAN offloading control information to an area of a Release-11 base station having no information providing function. You may have moved.
  • a user terminal may receive a service from an E-UTRAN / UTRAN base station capable of transmitting an SIB or RRC message including the WLAN offloading control information and then move to an area of the GERAN base station.
  • SIB System Information Block
  • RRC message including the WLAN offloading control information
  • the user terminal since the user terminal cannot receive the WLAN offloading control information from the base station, it may be in an unclear state how to perform the WLAN offloading operation.
  • the base station capable of providing WLAN offloading control information provides WLAN offloading control information to a user terminal through an SIB or RRC message
  • the WLAN offloading control information is provided. Characterized by including information that can be used in the area that can not provide.
  • the WLAN offloading control information (wlan-offloadcommon IE included in the SIB17 message or wlan-OffloadDedicated IE included in the RRC connection reconfiguration message) provided by the base station to the user terminal may be applied by the terminal receiving the information.
  • the user terminal includes the GERAN as the applicable RAT information in the wlan-offloadDedicated IE received from the base station, the user terminal is WLAN offloading according to the control information included in the wlan-offloadDedicated IE received in the GERAN region. You can perform the operation.
  • the mobility controlInfo IE of the RRC connection release message or the RRC connection reconfiguration message for switching the user terminal to another RAT or Cell the user terminal has finished switching or handover WLAN offloading control information that can be applied later.
  • the base station when the user terminal needs to switch / hand over to another RAT or base station or area, the base station performs WLAN offloading control to be applied in the target base station or area to a command message (the RRC connection release or RRC connection reconfiguration) sent to the user terminal.
  • Include information (wlan-offloadDedicated IE or wlan-offloadCommon IE).
  • Determining whether the base station includes the information in a message sent to the user terminal may be limited to a specific RAT or a base station / area. That is, the base station may include the information only when a switching or handover operation is required for a specific RAT or a base station / area for the user terminal. For example, when the user terminal is switched or handed over to the GERAN region, the base station may include the WLAN offloading control information in an RRC connection release message or an RRC connection reconfiguration message.
  • the user terminal performs a WLAN offloading operation based on the WLAN offloading control information provided by the base station and then switches / hands over to a base station or an area that does not provide the WLAN offloading control information
  • the user terminal is stored. If the applicable RAT condition or location condition is included in the WLAN offloading control information, it is determined whether this condition is satisfied. If the condition is met, the user terminal can continue using the stored WLAN offloading information (ie, received from the previous base station) to perform the WLAN offloading operation.
  • the user terminal receives the WLAN offloading control information (wlan-offloadDedicated IE or wlan-offloadCommon IE) to be used in the target base station or area in the RRC connection release or handover command message (RRC connection reconfiguration message)
  • the WLAN offloading operation may be performed based on the received WLAN offloading control information.
  • the WLAN offloading control information transmitted to the user terminal during the RRC connection release process or the handover process may be information that is limitedly applied to the target RAT or the base station / area.
  • the base station 800 may be an eNB, RNC or BSC.
  • the base station 800 may include a communication unit 810 and a control unit 830.
  • the communication unit 810 may communicate with at least one network node.
  • the controller 830 may control the overall operation of the base station 800.
  • the controller 830 may control to perform a handover operation for the corresponding terminal based on the QCI mapping information received from the core network node.
  • the controller 830 determines whether a handover is necessary for a user terminal using a specific bearer, and if it is determined that the handover is necessary, a hand supporting the specific bearer in a neighbor base station list.
  • An over-target base station may be selected, and the selected handover target base station may be controlled to perform a handover procedure for the terminal.
  • the specific bearer may be a bearer supporting a Mission Critical Push To Talk Voice (MCPTT) or a Non Mission Critical Push To Talk Voice (nMCPTT) service.
  • the controller 830 may control to establish an X2 interface connection with at least one neighboring base station and update the neighbor base station list based on a message for setting the X2 interface connection.
  • the message for establishing the X2 connection may include information indicating whether to support the MCPTT or nMCPTT.
  • the controller 830 communicates with a terminal using a bearer having a specific QCI value, receives handover restriction information for the terminal from a core network node, and determines whether the terminal requires handover. Based on the received handover restriction information, it may be controlled to select a base station for handover for the terminal.
  • the handover restriction information may include at least one neighbor base station information capable of supporting a bearer having the specific QCI value to the terminal.
  • the bearer having the specific QCI value may be a bearer supporting a Mission Critical Push To Talk Voice (MCPTT) or Non Mission Critical Push To Talk Voice (nMCPTT) service.
  • the base station 800 may perform not only the operation described with reference to FIG. 8 but also the operation of the base station according to the embodiment of the present invention described with reference to FIGS. 1 to 7.
  • the core network node may be an MME or SGSN.
  • the core network node 900 may include a communication unit 910 and a control unit 930.
  • the communication unit 910 may communicate with at least one network node.
  • the controller 930 may control the overall operation of the core network node 900.
  • the control unit 930 receives a handover request including a handover target base station identifier for a terminal, and the handover target base station provides QoS (Quality) for a service currently used by the terminal. If the handover target base station does not support the QoS condition for the service currently used by the terminal, it maps the QCI for the currently used service, and the hand of the terminal.
  • the handover progress message including the QCI mapping information may be transmitted to the over-target core network node.
  • the controller 930 may control the terminal to map the QIC to a QCI having a QoS parameter most similar to an existing QoS parameter for a service currently being used.
  • the QCI mapping information may be used to form an EPS bearer of the handover target core network node and the handover target base station for a service currently in use for the terminal.
  • controller 930 is an EPS (Evolved Packet System) bearer having a QCI value of 1 if the service currently being used by the terminal is a Mission Critical Push To Talk Voice (MCPTT) or a Non Mission Critical Push To Talk Voice (nMCPTT). Can be controlled to map QCI.
  • EPS Evolved Packet System
  • the controller 930 determines whether the terminal uses a bearer having a specific QCI (QoS Class Identifier) value, and if the terminal is using a bearer having a predetermined specific QCI value, handover restriction for the terminal.
  • Information may be generated and control may be performed to transmit the generated handover restriction information to a serving base station of the terminal.
  • the handover restriction information may include at least one neighbor base station information capable of supporting a bearer having the specific QCI value to the terminal.
  • the controller 930 may control to exclude the base station that does not support the bearer having the specific QCI value from the handover restriction information.
  • the handover restriction information may be used by the serving base station to select a handover target base station when there is a handover request for the terminal.
  • the configuration and function of the core network node 900 are divided and described, but this is for convenience of description and the scope of the present invention is not limited thereto.
  • the core network node 900 may perform not only the operation described with reference to FIG. 9 but also an operation of the core network node according to an embodiment of the present invention described with reference to FIGS. 1 to 7.
  • the terminal 1000 may include a communication unit 1010 and a control unit 1030.
  • the communication unit 1010 may communicate with at least one network node.
  • the controller 1030 may control the overall operation of the terminal 1000.
  • the controller 1030 may control to perform a handover procedure for the base station to be handed over based on QCI mapping information and handover restriction information exchanged between the base station and the core network node. In addition, based on the new bearer configuration information, it is possible to perform the RRC connection reconfiguration process.
  • the controller 1030 communicates with a base station using a specific bearer, reports a cell measurement result to the base station, and includes the handover target base station information based on the measurement result from the base station. It can be controlled to receive the over request message.
  • the handover target base station may support the specific bearer being used by the terminal.
  • the specific bearer may be a bearer supporting a Mission Critical Push To Talk Voice (MCPTT) or a Non Mission Critical Push To Talk Voice (nMCPTT) service.
  • MCPTT Mission Critical Push To Talk Voice
  • nMCPTT Non Mission Critical Push To Talk Voice
  • the terminal 1000 may perform not only the operation described with reference to FIG. 10 but also an operation according to the embodiment of the present invention described with reference to FIGS. 1 to 7.

Landscapes

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

Abstract

La présente invention concerne une technologie de communication combinant un système de communication 5G, qui prend en charge un débit de transmission de données supérieur dépassant le système 4G, avec une technologie de l'Internet des objets (IoT), et un système associé. La présente invention, sur la base de technologies de communication 5G et de l'Internet des objets (IoT), peut s'appliquer à des services intelligents (par exemple, une maison intelligente, un bâtiment intelligent, une ville intelligente, une voiture intelligente ou connectée, des soins de santé, l'éducation numérique, le commerce de détail, les services liés à la sécurité et à la sûreté, et analogues). Un mode de réalisation de la présente invention concerne un procédé et un système pour commander une continuité de service lorsqu'un terminal reçoit un service particulier en provenance d'un système de communication sans fil. Un mode de réalisation de la présente invention concerne un procédé et un système pour commander une continuité de service lorsqu'un transfert intercellulaire se produit pendant qu'un terminal utilisateur reçoit un service ayant une exigence de qualité de service (QoS) particulière. Un mode de réalisation de la présente invention concerne un procédé et un système de fonctionnement d'un nœud de réseau principal, d'une station de base et d'un terminal de façon à prendre en charge une continuité de service lorsqu'un transfert intercellulaire se produit.
PCT/KR2015/006498 2014-06-30 2015-06-25 Procédé et système pour commander une continuité de service dans un système de communication sans fil WO2016003113A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR1020140081061A KR102232787B1 (ko) 2014-06-30 2014-06-30 무선 통신 시스템에서 서비스 연속성을 제어하는 방법 및 장치
KR10-2014-0081061 2014-06-30

Publications (1)

Publication Number Publication Date
WO2016003113A1 true WO2016003113A1 (fr) 2016-01-07

Family

ID=55019585

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2015/006498 WO2016003113A1 (fr) 2014-06-30 2015-06-25 Procédé et système pour commander une continuité de service dans un système de communication sans fil

Country Status (2)

Country Link
KR (1) KR102232787B1 (fr)
WO (1) WO2016003113A1 (fr)

Cited By (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018028295A1 (fr) * 2016-08-12 2018-02-15 电信科学技术研究院 Dispositif et procédé destinés au traitement de paramètre de qos dans un scénario de commutation
CN107889080A (zh) * 2016-09-29 2018-04-06 中兴通讯股份有限公司 一种支持远端用户设备移动性的方法及装置
CN110022581A (zh) * 2018-01-10 2019-07-16 维沃移动通信有限公司 一种支持网络承载控制的方法、装置、网络单元及终端
CN112740758A (zh) * 2018-10-09 2021-04-30 联想(北京)有限公司 具有网络信息的切换请求
US20230142031A1 (en) * 2021-02-26 2023-05-11 T-Mobile Usa, Inc. Tdd-to-fdd handover based on service type and uplink quality

Families Citing this family (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US11310290B2 (en) 2016-07-15 2022-04-19 Samsung Electronics Co., Ltd. System and method for establishing first-to-answer call in mission critical push to talk communication
EP3479603A4 (fr) 2016-08-26 2019-05-08 Samsung Electronics Co., Ltd. Procédé destiné à la gestion de demande de prise de parole dans un système de communication essentielle à la mission
WO2018040005A1 (fr) 2016-08-31 2018-03-08 深圳市大疆创新科技有限公司 Procédé, appareil et système de traitement de connexion de communication
EP3823354B1 (fr) * 2017-05-05 2023-09-06 Sony Group Corporation Dispositif de communication, équipement d'infrastructure, réseau de communication sans fil et procédés
CN110662267B (zh) * 2017-08-11 2020-12-08 华为技术有限公司 一种传输方法和网络设备
KR102416644B1 (ko) * 2020-10-26 2022-07-05 주식회사 케이티 음성 서비스를 제공하는 방법, 사용자 단말 및 컴퓨터 프로그램

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20130095786A (ko) * 2010-11-05 2013-08-28 인터디지탈 패튼 홀딩스, 인크 릴레이 노드 인터페이스 관련 레이어 ２ 측정과 네트워크 부하 밸런싱에서의 릴레이 노드 처리
KR20130119791A (ko) * 2012-04-24 2013-11-01 주식회사 케이티 이동성 관리장치, 기지국, 그리고 이들의 부하 조절 방법
KR20130139685A (ko) * 2012-06-13 2013-12-23 주식회사 케이티 서비스별 네트워크 접속 방법 및 네트워크 제공 시스템
US8638753B2 (en) * 2008-04-21 2014-01-28 Telefonaktiebolaget L M Ericsson (Publ) QCI mapping at roaming and handover

Family Cites Families (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR102002155B1 (ko) * 2012-06-20 2019-07-19 엘지전자 주식회사 무선 통신 시스템에서 핸드오버를 수행하는 방법 및 장치
KR20140016713A (ko) * 2012-07-31 2014-02-10 주식회사 케이티 무선 접속 기술 변경 시 베어러의 처리를 위한 방법 및 그 장치

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US8638753B2 (en) * 2008-04-21 2014-01-28 Telefonaktiebolaget L M Ericsson (Publ) QCI mapping at roaming and handover
KR20130095786A (ko) * 2010-11-05 2013-08-28 인터디지탈 패튼 홀딩스, 인크 릴레이 노드 인터페이스 관련 레이어 ２ 측정과 네트워크 부하 밸런싱에서의 릴레이 노드 처리
KR20130119791A (ko) * 2012-04-24 2013-11-01 주식회사 케이티 이동성 관리장치, 기지국, 그리고 이들의 부하 조절 방법
KR20130139685A (ko) * 2012-06-13 2013-12-23 주식회사 케이티 서비스별 네트워크 접속 방법 및 네트워크 제공 시스템

Cited By (8)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2018028295A1 (fr) * 2016-08-12 2018-02-15 电信科学技术研究院 Dispositif et procédé destinés au traitement de paramètre de qos dans un scénario de commutation
US10959133B2 (en) 2016-08-12 2021-03-23 China Academy Of Telecommunications Technology Method and device for processing quality of service parameter in handover scenario
CN107889080A (zh) * 2016-09-29 2018-04-06 中兴通讯股份有限公司 一种支持远端用户设备移动性的方法及装置
CN107889080B (zh) * 2016-09-29 2023-06-06 中兴通讯股份有限公司 一种支持远端用户设备移动性的方法及装置
CN110022581A (zh) * 2018-01-10 2019-07-16 维沃移动通信有限公司 一种支持网络承载控制的方法、装置、网络单元及终端
CN112740758A (zh) * 2018-10-09 2021-04-30 联想(北京)有限公司 具有网络信息的切换请求
CN112740758B (zh) * 2018-10-09 2022-11-15 联想(北京)有限公司 具有网络信息的切换请求
US20230142031A1 (en) * 2021-02-26 2023-05-11 T-Mobile Usa, Inc. Tdd-to-fdd handover based on service type and uplink quality

Also Published As

Publication number Publication date
KR20160002150A (ko) 2016-01-07
KR102232787B1 (ko) 2021-03-26

Similar Documents

Publication Publication Date Title
WO2016003113A1 (fr) Procédé et système pour commander une continuité de service dans un système de communication sans fil
RU2668071C1 (ru) Способ и устройство оптимизации сигнализации
WO2021029649A1 (fr) Procédé et appareil pour la gestion d'un transfert conditionnel dans un réseau de communication sans fil
EP3051876B1 (fr) Procédé de commutation de petite cellule, enb et support de stockage informatique
WO2017052266A1 (fr) Procédé et appareil d'amélioration de la mobilité dans un système de communications sans fil
US11129054B2 (en) Methods, systems and devices for supporting local breakout in small cell architecture
WO2014129783A1 (fr) Procédé et système pour réaliser une connectivité simultanée entre de multiples nœuds b évolués et un équipement utilisateur
WO2013147499A1 (fr) Procédé et dispositif pour la préservation de données de mobilité lors d'une transition d'état d'un terminal, et pour un nouvel accès réussi dans un réseau cellulaire hétérogène dans un système de communication mobile
US11412563B2 (en) Multi-connectivity communication method and device
JP6442038B2 (ja) ユーザ機器及び基地局のデュアルコネクティビティにおけるハンドオーバのための方法及び装置
WO2016161759A1 (fr) Procédé et dispositif de transmission de données
US9642045B2 (en) Method and device for releasing context-related resource of user equipment
WO2014116063A1 (fr) Procédé et appareil de commande de la mobilité pour une cellule ayant une zone de desserte de petites cellules dans un système de communication mobile
WO2015174804A1 (fr) Procédé et dispositif pour continuité de service d'un terminal
WO2020167087A1 (fr) Procédé et dispositif pour transmettre des données dans un système de communication sans fil
WO2014177090A1 (fr) Procédé de transfert, station de base maître et station de base esclave
EP2843991B1 (fr) Procédé d'accès, station de base, point d'accès et équipement utilisateur
JP2017503415A (ja) セルハンドオーバ方法、基地局、およびシステム
KR20120000859A (ko) 무선 통신 시스템 및 그 시스템에서 핸드오버 수행 방법
WO2018126462A1 (fr) Procédé de communication, dispositif associé, et système
US20160242081A1 (en) Reducing signaling load to the corenetwork caused by frequent cell changes of an user equipment among small cells
WO2013189310A1 (fr) Procédé de contrôle pour un système de radio cognitive, station de base, et relation de voisinage
WO2016021306A1 (fr) Station de base, système de communications sans fil et procédé de communications
JP2022043218A (ja) 通信方法、セカンダリネットワークノード及び端末
WO2014023254A1 (fr) Procédé et dispositif de rapport de mesure et de jugement de séparation de support ou de commutateur

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: 15815814

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 15815814

Country of ref document: EP

Kind code of ref document: A1