[go: up one dir, main page]

WO2015060695A1 - Procédé et appareil de délestage de trafic dans un système de communication sans fil - Google Patents

Procédé et appareil de délestage de trafic dans un système de communication sans fil Download PDF

Info

Publication number
WO2015060695A1
WO2015060695A1 PCT/KR2014/010103 KR2014010103W WO2015060695A1 WO 2015060695 A1 WO2015060695 A1 WO 2015060695A1 KR 2014010103 W KR2014010103 W KR 2014010103W WO 2015060695 A1 WO2015060695 A1 WO 2015060695A1
Authority
WO
WIPO (PCT)
Prior art keywords
bearer
offload
backhaul
flag
sipto
Prior art date
Legal status (The legal status 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 status listed.)
Ceased
Application number
PCT/KR2014/010103
Other languages
English (en)
Korean (ko)
Inventor
프랜클린안토니
박중신
손영문
이철기
Current Assignee (The listed assignees may be inaccurate. Google has not performed a legal analysis and makes no representation or warranty as to the accuracy of the list.)
Samsung Electronics Co Ltd
Original Assignee
Samsung Electronics Co Ltd
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 Samsung Electronics Co Ltd filed Critical Samsung Electronics Co Ltd
Publication of WO2015060695A1 publication Critical patent/WO2015060695A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W24/00—Supervisory, monitoring or testing arrangements
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W28/00—Network traffic management; Network resource management
    • H04W28/02—Traffic management, e.g. flow control or congestion control
    • H04W28/0289—Congestion control
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management

Definitions

  • the present invention relates to a wireless communication system, and more particularly, to a method and apparatus for offloading a traffic in a wireless communication system.
  • mobile communication systems have been developed to provide voice services while guaranteeing user activity.
  • mobile communication systems are gradually expanding to not only voice but also data services, and now they have developed to the extent that they can provide high-speed data services.
  • a shortage of resources and users demand faster services, and thus, a more advanced mobile communication system is required.
  • the SIPTO refers to a technology in which an operator offloads traffic to a node such as a home base station (Home (e) NB) without passing the traffic through the core network.
  • Home (e) NB home base station
  • SIPTOs there are two types of SIPTOs: a SIPTO for a single Packet Data Network (PDN) and a SIPTO for multiple PDNs.
  • PDN Packet Data Network
  • SIPTO for multiple PDNs the offload decision is made at the flow level, and there is a problem that the complexity increases when the offload decision is made at the flow level.
  • the terminal should be instructed to select a specific PDN connection while determining a flow for offloading, but most terminals do not support the above functions.
  • the present invention has been made to solve the above problems, and an object thereof is to provide a method and apparatus for offloading traffic in a wireless communication system.
  • the present invention provides a method and apparatus for mapping at least one bearer to a core network or to a SIPTO according to bearer related parameters and channel conditions for the bearer. The purpose.
  • the traffic offload method of the offload management apparatus checks the bearer-related parameters for any bearer, the channel status for the backhaul of the wireless communication system And determining whether to offload any bearer based on the identified bearer related parameters and the channel state for the backhaul.
  • the offload management apparatus for managing traffic offload in the wireless communication system of the present invention is a backhaul measuring unit for measuring the channel state for the backhaul of the wireless communication system, and bearer-related parameters for any bearer, And an offload manager for checking the channel state of the backhaul of the wireless communication system and determining whether to offload the bearer based on the identified bearer-related parameters and the channel state of the backhaul. .
  • FIG. 1 is a diagram illustrating a traffic offload method according to an embodiment of the present invention.
  • FIG. 2 is a block diagram showing an internal structure of the offload management apparatus 200 according to the embodiment of the present invention.
  • FIG. 3 is a flowchart illustrating a process of determining a bearer mapping by the offload management apparatus 200 according to an embodiment of the present invention.
  • FIG. 4 is a flowchart illustrating a process of changing bearer mapping according to a change in a backhaul channel state according to an embodiment of the present invention.
  • FIG. 5 is a flowchart illustrating a process in a case where a change occurs in a bearer parameter due to a change in an operator policy or user subscription information according to an embodiment of the present invention.
  • FIG. 6A is a flowchart illustrating a process in which bearer related parameters determined by an operator policy are directly set to a bearer according to an embodiment of the present invention.
  • FIG. 6B is a flowchart illustrating a process of transmitting bearer related parameters determined by an operator policy to an offload management apparatus according to an embodiment of the present invention.
  • FIG. 7 is a flowchart illustrating a process of delivering the change when a change occurs in a bearer related parameter according to an embodiment of the present invention.
  • FIG. 8 is a flowchart illustrating a process of deactivating a bearer according to an embodiment of the present invention.
  • FIG. 9 is a flow chart illustrating a process of deactivating a bearer according to one embodiment of the present invention.
  • FIG. 10 is a flowchart illustrating a procedure of initiating a bearer modification procedure according to a change of subscriber information according to an embodiment of the present invention.
  • FIG. 1 is a diagram illustrating a traffic offload method according to an embodiment of the present invention.
  • a wireless communication network includes a terminal 110, a base station 120, a home network 130, a back haul 140, an internet 150, and a core network 160. It may be configured to include).
  • the terminal 110 may be connected to the base station 120 through a wireless channel.
  • the base station 120 may include both small base stations such as macro base stations, femto or pico base stations. As will be described later, according to an embodiment of the present invention, the base station 120 may be a home base station (Home (e) NB).
  • Home (e) NB home base station
  • Traffic transmitted by the terminal 110 to the network may be delivered to the Internet 150 or the core network 160 via the base station 120 and the backhaul 140.
  • Such a transmission path may be referred to as a general path.
  • the base station 120 transmits the traffic transmitted from the terminal 110 to the home network 130 instead of transferring the traffic transmitted from the terminal 110 to the backhaul 140. This may be referred to as traffic offload.
  • the operator may determine whether to perform SIPTO for both traffic of Best Effort and traffic for which QoS should be guaranteed in accordance with the implementation of the present invention described below.
  • an operator policy as a factor for determining traffic offload, an operator policy, a session continuity support of the flows, and a current congestion state of the backhaul network congestion in the backhaul network).
  • the operator policy may be determined by user subscription information, an application type, an application service provider, and the like. The operator may determine whether to offload the bearer based on the above information. In an embodiment of the present invention, the operator policy may be set through a SIPTO flag parameter. If the SIPTO flag is set to Yes (On), the bearer may be set to map to the possible SIPTO.
  • Session continuity support of a flow may be determined by information such as application type, application provider, and the like.
  • session continuity support of the flow may be determined by operator policy.
  • any flow may move from any one node to another node via IP tunneling, where the continuity of the session may not be guaranteed if the nodes belong to different anchors. If session continuity is to be guaranteed, session continuity support of the flow may be set to Yes.
  • the current congestion situation in the backhaul network can be a very important factor for offloading traffic.
  • the congestion situation of the backhaul network may be measured periodically or aperiodically by the offload management apparatus.
  • the improved SIPTO mechanism may be performed in a home base station (Home (e) NB) or the like.
  • the QoS of flows is considered for SIPTO offload determination, it is possible to implement a bearer level offload mechanism.
  • the bearer level offload mechanism can reduce the complexity than conventional packet level or PDN level offload.
  • FIG. 2 is a block diagram illustrating an internal structure of the offload management apparatus 200 according to an embodiment of the present invention.
  • the offload management apparatus 200 may be a home base station (H (e) NB).
  • the offload management apparatus 200 may include a backhaul measurement unit 210 and an offload manager 220.
  • the backhaul measuring unit 210 measures the state of the backhaul periodically or aperiodically.
  • the state of the backhaul may mean a congestion level of the backhaul.
  • the state of the backhaul may mean a QoS level that can be supported according to the state of the current backhaul.
  • the backhaul measuring unit 210 may measure end-to-end delay and loss rate.
  • the backhaul measuring unit 210 may determine quality control information (QCI) that can be supported by the backhaul based on the measurement result.
  • QCI quality control information
  • the determined QCI may be used as a parameter for determining whether each bearer is mapped to CN or SIPTO.
  • the backhaul measurement unit 210 measures the state of the backhaul periodically or aperiodically, and if the current measurement result is different from the previous measurement result, may report it to the offload manager 220. .
  • the offload manager 220 reports the backhaul measurement result from the backhaul measurement unit 210.
  • the offload manager 220 may receive a measurement result from the backhaul measurement unit 210 periodically or aperiodically, or may request that the backhaul measurement unit 210 measure and report a channel state of the backhaul.
  • the offload manager 220 may map each bearer to a CN or SIPTO based on operator policy, session continuity support of the flow, and channel state of the backhaul, as described above.
  • the operator policy may be set whether or not the flow is offloaded based on user subscription information.
  • the operator policy may be set through a SIPTO flag in an embodiment of the present invention.
  • the session continuity support of the player may be determined by information such as an operator policy, an application type, an application provider, and the like.
  • the continuity support of the flow may be set through a session continuity flag in an embodiment of the present invention.
  • the bearer is set only by QoS parameters such as QCI, Guaranteed Bitrates (ARP), Guaranteed Bitrates (GBR), Maximum Bit Rate (MBR), and the like. ) May also be set by the Session Continuity Flag.
  • QCI Guaranteed Bitrates
  • GRR Guaranteed Bitrates
  • MRR Maximum Bit Rate
  • the SIPTO flag and the session continuity flag may be referred to as bearer related parameters.
  • the bearer related parameter may include conventional QCI information, in addition to a SIPTO flag and a session continuity flag.
  • the SIPTO flag when the SIPTO flag is set to 1 (or Yes), this may mean that the operator policy has decided to offload the flow through the SIPTO if possible.
  • the Session Continuity Flag when the Session Continuity Flag is set to 1 (or Yes), this may mean that the operator policy has determined that session continuity for the corresponding flow should be guaranteed.
  • a SIPTO flag and a session continuity flag may be added as additional parameters for forming any bearer, and the offload manager 220 may be based on the parameters.
  • the mapping relationship of bearers can be determined.
  • the bearer is mapped to the CN. According to an embodiment of the present invention, even if the SIPTO flag is set to 1, the bearer may be offloaded only when the backhaul state guarantees a certain level of quality of service without unloading the bearer unconditionally. have.
  • the bearer may be mapped to the SIPTO. .
  • the bearer can guarantee that the backhaul It may be mapped to SIPTO or CN depending on the level of QoS. For example, if a QoS level that can be guaranteed by the backhaul is less than a preset threshold, that bearer can be mapped to a CN. Can be.
  • the offload manager 220 of the offload management apparatus 200 transfers any bearer to either the CN or CIPTO network based on the bearer related parameter and the channel state of the backhaul. You can decide whether to map.
  • the offload manager 220 may determine the bearer mapping relationship according to the QoS current state (level) in the backhaul or mobility support for SIPTO traffic handling.
  • FIG. 3 is a flowchart illustrating a process of determining bearer mapping by the offload management apparatus 200 according to an embodiment of the present invention.
  • the offload management apparatus 200 establishes at least one bearer in operation S310.
  • the bearers may be classified according to at least one of QCI or bearer related parameters. For example, bearers with different QCIs can be distinguished from each other. Further, even if the QCIs are the same, bearers having different bearer related parameters may be distinguished from each other.
  • the bearer related parameter may include at least one of a SIPTO flag or a session continuity flag.
  • the offload management apparatus 200 determines whether a SIPTO flag is set to On (Yes) among bearer-related parameters for an arbitrary bearer. If the SIPTO flag is not set to On (Yes), the offload management apparatus 200 proceeds to step S350 to map the bearer to CN. In other words, the offload management apparatus 200 does not offload the bearer and maps it to the core network.
  • the offload management apparatus 200 proceeds to step S330 to determine whether the QCI is supported by the SIPTO.
  • the offload management apparatus 200 may compare the channel measurement state of the backhaul with the QCI to be guaranteed for the bearer and determine whether the channel state of the backhaul can support the QCI set for the bearer. .
  • the offload management apparatus 200 proceeds to step S350 to map the bearer to CN. In other words, the offload management apparatus 200 does not offload the bearer and maps it to the core network.
  • the offload management device 200 proceeds to step S340 to determine whether the mobility support is set to On (Yes). If not set, the offload management apparatus 200 proceeds to step S360 to map the bearer to SIPTO. In other words, the offload management apparatus 200 offloads the bearer.
  • the offload management apparatus 200 may proceed to step S370 to map the bearer to the SIPTO or CN according to the level of QoS that the backhaul can guarantee. For example, when the QoS level that can be guaranteed by the backhaul is less than a preset threshold, the offload management device 200 may map the bearer to the CN, or the threshold that the QoS level that the backhaul can guarantee is preset. If the value is greater than or equal to the value, the offload management apparatus 200 may map the bearer to the SIPTO.
  • FIG. 4 is a flowchart illustrating a process of changing bearer mapping according to a change in a backhaul channel state according to an embodiment of the present invention.
  • the offload management apparatus 200 may continuously monitor a change in QoS level support in the backhaul. When a change in QoS level support is detected in the backhaul, the offload management apparatus 200 may determine whether there is a change in the offload determination for the bearer according to the criteria illustrated in Table 1 above.
  • the first is when a bearer mapped to (or determined to be mapped to) a CN changes to being mapped to a SIPTO, and the second is when a bearer mapped to (or determined to be mapped) changes to being mapped to a CN. to be.
  • the bearer mapped to the SIPTO is mapped to the CN, for example, the channel state of the core network is improved.
  • the bearer may be released.
  • bearer mapping When bearer mapping is changed from CN to SIPTO, it may be desirable to maintain a bearer mapping state to CN.
  • traffic transmission from the P-GW to the home base station may be possible.
  • bearer mapping is changed from SIPTO to CN, it may not be desirable to use IP tunneling between SIPTO and CN because degraded QoS may not be improved in SIPTO. Accordingly, the bearer (traffic) can maintain the bearer mapping state to the SIPTO with degraded QoS. Alternatively, according to an embodiment of the present invention, the bearer may be released.
  • the offload management apparatus 200 determines whether a change is detected in the SIPTO QCI in step S410. If a change is detected, the offload management apparatus 200 starts a determination as to whether it is necessary to change the mapping setting for each bearer in step S420.
  • the offload management apparatus 200 evaluates the offload determination in step S430. As a result of the evaluation, if it is determined that a change has occurred in the offload determination in step S440, the offload management apparatus 200 determines whether the session continuity flag is set to Yes (On) in step S450. .
  • step S460 the offload management apparatus 200 proceeds to step S460 to release the bearer.
  • the offload management apparatus 200 proceeds to step S470, and whether the offload decision change is a change from SIPTO to CN or from CN to SIPTO. Determine whether or not.
  • the offload management apparatus 200 may proceed to step S480 to maintain the mapping setting to the SIPTO.
  • the offload management apparatus 200 may release the bearer.
  • the offload management apparatus 200 may proceed to step S490 to maintain the mapping setting to the CN.
  • the offload management apparatus 200 may repeat the above process for the next bearer.
  • FIG. 5 is a flowchart illustrating a process in a case where a change is made in a bearer parameter due to a change in an operator policy or user subscription information according to an embodiment of the present invention.
  • the bearer mapping relationship may be changed according to the channel state of the backhaul (described in FIG. 4), the bearer mapping relationship may also be changed by changing an operator policy or user subscription information according to an embodiment of the present invention.
  • the offload management apparatus 200 may monitor the bearer modification matter periodically or aperiodically.
  • the offload decision may be evaluated and maintained or changed according to the monitoring result. This will be described in detail with reference to the flowchart of FIG. 5.
  • the offload management apparatus 200 determines whether a bear modification has occurred for each bearer in operation S510.
  • the offload management apparatus 200 When the occurrence is detected, the offload management apparatus 200 starts evaluating the offload determination previously performed in order to determine whether it is necessary to change the offload determination for each bearer in operation S520.
  • the offload management apparatus 200 determines whether the session continuity flag is set to Yes (On) in step S540. .
  • step S550 the offload management apparatus 200 proceeds to step S550 to release the bearer.
  • the offload management apparatus 200 proceeds to step S560, whether the offload decision change is a change from SIPTO to CN or from CN to SIPTO. Determine whether or not.
  • the offload management apparatus 200 may proceed to step S570 to maintain mapping setting to SIPTO.
  • the offload management apparatus 200 may release the bearer.
  • the offload management apparatus 200 may proceed to step S580 to maintain the mapping setting to the CN.
  • the offload management apparatus 200 may proceed to step S590 to repeat the above process for the next bearer.
  • FIG. 6A is a flowchart illustrating a process of delivering the parameter so that a bearer may be directly set based on a bearer related parameter determined by an operator policy according to an embodiment of the present invention.
  • a bearer related parameter including at least one of a SIPTO Flag and a Session Continuity Flag set in the PCRF 650 is transferred to the PDN GW 640.
  • the PDN GW 640 generates a bearer by including a SIPTO Flag and a Session Continuity Flag parameter as bearer configuration values when initial bearer creation.
  • the S-GW 630 and the eNB 610 generate a bearer including a SIPTO Flag and a Session Continuity Flag parameter as bearer setting values when the bearer is generated.
  • the application function (AF) 660 may transmit a service notification message to the policy charging and rules function (650 PCRF) 650 in operation S680. Then, the PCRF 650 forwards the IP-CAN session modification message to the PDG GW 640 in step S681. Subsequently, the PCRF 640 may deliver a Policy and Charging Rule Provisioning message to the PDG GW 640 in step S682.
  • the policy and charging rule preparation message may include a bearer related parameter, for example, a SIPTO flag and a session continuity flag.
  • the PDN GW 640 may transmit a Create Bearer Request message to the Serving GW 630.
  • the bearer creation request message instructs to create a bearer by including a SIPTO Flag and a Session Continuity Flag parameter as a bearer configuration value upon initial bearer creation.
  • the Serving GW 630 may transmit a Create Bearer Request message to the MME 620 in step S684.
  • the MME 620 may transmit a bearer setup request message and / or a session management request message to the base station 610.
  • the base station 610 transmits an RRC connection reconfiguration message to the terminal 600 in step S686.
  • the terminal 600 transmits an RRC connection reconfiguration complete message to the base station 610.
  • the base station 610 transmits a bearer setup response message to the MME 620 in step S688.
  • the terminal 600 transmits a direct transfer message to the base station 610 in step S689. Then, the base station 610 transmits a session management response message to the MME 620 in step S690. Then, the MME 620 transmits a bearer response message to the Serving GW 630 in step S691.
  • the serving GW 630 transmits a bearer create response message to the PDN GW 640. Then, the PDN GW 640 forwards the IP-CAN session modification message to the PCRF 650 in step S692.
  • the PDN GW 640 may generate a bearer including a SIPTO Flag and a Session Continuity Flag parameter as bearer configuration values when initial bearer creation.
  • FIG. 6B is a flowchart illustrating a process of maintaining a legacy bearer system according to an embodiment of the present invention, and transmitting bearer related parameters determined by an operator policy as a message to an offload management apparatus.
  • FIG. 6 illustrates a process in which bearer related parameters are delivered in a dedicated bearer activation process.
  • the offload management apparatus may be a home base station (HeNB) or a base station (eNB).
  • HeNB home base station
  • eNB base station
  • the bearer related parameter may include at least one of a SIPTO flag and a session continuity flag.
  • the bearer related parameter may be delivered to the home base station or the base station as additional information during the bearer set up process.
  • the bearer related parameters are delivered to a Mobility Management Entity (MME) during bearer activation or modification, and the MME sends the bearer related parameters to a home base station or base station. You can pass it to the offload manager.
  • MME Mobility Management Entity
  • the bearer related parameters may be passed to a target base station.
  • the application function (AF) 660 may transmit a service notification message to the policy charging and rules function 650 in step S605. Then, the PCRF 650 transmits the IP-CAN session modification message to the PDN GW 640 in step S610. Subsequently, the PCRF 650 may deliver a Policy and Charging Rule Provisioning message to the PDG GW 640 in step S615.
  • the policy and charging rule preparation message may include a bearer related parameter, for example, a SIPTO flag and a session continuity flag.
  • the PDN GW 640 may transmit a Create Bearer Request message to the Serving GW 630.
  • the bearer creation request message may include a SIPTO flag and a session continuity flag.
  • the Serving GW 630 may transmit a Create Bearer Request message to the MME 620 in step S625.
  • the bearer creation request message may include a SIPTO flag and a session continuity flag.
  • the MME 620 may store the received SIPTO flag and session continuity flag.
  • the MME 620 may transmit a bearer setup request message and / or a session management request message to the base station 610.
  • the bearer establishment request message or session management request message may include a received SIPTO flag and a session continuity flag.
  • the base station 610 transmits an RRC connection reconfiguration message to the terminal 600 in step S640.
  • the terminal 600 transmits an RRC connection reconfiguration complete message to the base station 610 in step S645.
  • the base station 610 transmits a bearer setup response message to the MME 620 in step S650.
  • the terminal 600 transmits a direct transfer message to the base station 610 in step S655. Then, the base station 610 transmits a session management response message to the MME 620 in step S660. Then, the MME 620 delivers a bearer response message to the Serving GW 630 in step S665.
  • the Serving GW 630 transmits a bearer create response message to the PDN GW 640. Then, the PDN GW 640 forwards the IP-CAN session modification message to the PCRF 650 in step S675.
  • the bearer related parameters may be delivered to the base station 610 including the offload management apparatus through the MME 620 in the dedicated bearer activation process.
  • FIG. 7 is a flowchart illustrating a process of delivering the change when a change occurs in a bearer related parameter according to an embodiment of the present invention.
  • the PCRF may provide a PCC rule to the updated bearer.
  • an application function (AF) 760 may deliver a service notification message to a policy charging and rules function 750 in step S705. Then, the PCRF 750 transmits the IP-CAN session modification message to the PDG GW 740 in step S710. In step S715, the PCRF 750 may deliver a policy and charging rule provisioning message to the PDG GW 740.
  • the policy and charging rule preparation message may include a bearer related parameter, for example, a SIPTO flag and a session continuity flag.
  • the PDN GW 740 may transmit a bearer update request message to the Serving GW 730.
  • the Serving GW 730 may transmit a bearer update request message to the MME 720 in step S725.
  • the MME 720 may transmit a bearer modification request message and / or a session management request message to the base station 710.
  • the base station 710 transmits an RRC connection reconfiguration message to the terminal 700 in step S735.
  • the terminal 700 transmits an RRC connection reconfiguration complete message to the base station 710 in step S740.
  • the base station 710 transmits a bearer modify response message to the MME 720 in step S745.
  • the terminal 700 transmits a direct transfer message to the base station 710 in step S750.
  • the base station 7610 transmits a session management response message to the MME 720 in step S755.
  • the MME 720 transmits a bearer update response (Update Bearer Response) message to the Serving GW 730 in step S760.
  • a bearer update response Update Bearer Response
  • the Serving GW 730 transmits a bearer update response message to the PDN GW 740. Then, the PDN GW 740 forwards the IP-CAN session modification message to the PCRF 750 in step S70.
  • FIG. 8 is a flowchart illustrating a process of deactivating a bearer according to an embodiment of the present invention.
  • the PCRF may determine to delete (or release) a bearer due to a change in an operator policy or the like. After a plurality of bearers are formed for the SIPTO or CN, if all flows are moved to the SIPTO / non-SIPTO, other bearers may be deleted using the bearer deactivation procedure.
  • the PCRF 860 may transmit an IP-CAN session modification message to the PDN GW 850. Then, the PGDN GW 850 transmits a bearer deletion request message to the Serving GW 840 in step S810.
  • the serving GW 840 may transmit a bearer deletion request message to the MME 820 and the SGSN 830, respectively, in steps S815 and S850.
  • the MME 820 may transmit a Detach Request message to the terminal 800 in step S825.
  • the MME 820 initiates a trigger for reactivation in the ECM-IDLE.
  • the MME 820 may transmit a bearer deactivation request message to the base station 810 in step S835. Then, the base station 810 transmits an RRC connection reset message to the terminal 800 in step S840, and the terminal 800 transmits an RRC connection reset complete message to the base station 810 in step S845.
  • the base station 810 may transmit a bearer deactivation response message to the MME 820 in step S850.
  • the terminal 800 transmits a direct transmission message to the base station 810 in step S855, and the base station 810 transmits an EPS bearer context inactivation acceptance message to the MME 820 in step S860. Thereafter, the terminal 800 may transmit a connection accept message to the MME 820 in step S865.
  • the MME 820 may transmit a bearer deletion response message to the Serving GW 840 in operation S870, and the SGSN 830 may transmit a bearer deletion response message to the Serving GW 840 in operation S875.
  • step S880 the Serving GW 840 transmits a bearer deletion response message to the PDN GW 850, and the PDN GW 850 transmits an IP-CAN session modification message to the PCRF 860 in step S8850.
  • the terminal 800 may release the signaling connection through signaling between the base station 810 and the MME 820.
  • 9 is a flowchart illustrating a process of deactivating a bearer according to an embodiment of the present invention. 9 is a flow chart for how the MME initiates bearer deactivation.
  • the base station When determining whether to offload, if any bearer should be released, the base station will trigger the release of the bearer, the bearer release may be initiated by the MME.
  • the terminal 900 may transmit a radio bearer release message to the base station 900 in step S905. Then, the base station 910 may transmit a bearer release indicator to the MME 920 in step S910. Then, the MME 920 may transmit a bearer delete command to the Serving GW 930 in operation S915.
  • the Serving GW 930 may transmit a bearer delete command to the PDN GW 940 in operation S920, and the PDN GW 940 exchanges an IP-CAN session modification message with the PCRF 950 in operation S925. .
  • the PDN GW 940 transmits a bearer deletion request message to the Serving GW 930. Then, the Serving GW 930 transmits a bearer deletion request message to the MME 920 in step S935. Then, a bearer deactivation procedure may be performed in step S940.
  • the MME 920 may transmit a bearer deletion response message to the Serving GW 930, and the Serving GW 930 may transmit a bearer deletion response message to the PDN GW 940 in operation S950.
  • FIG. 10 is a flowchart illustrating a procedure of starting a bearer modification procedure according to a change of subscriber information according to an embodiment of the present invention.
  • a home subscriber server transmits a subscriber data insertion message to the MME 1030 in step S1005. Then, the MME delivers the subscriber data insertion confirmation message to the HSS 1070 in step S1010.
  • the MME 1030 updates the context information of the UE in step S1015, and transmits a bearer modification command message to the Serving GW 1040 in step S1020. Then, the Serving GW 1040 transmits a bearer modification command message to the PDN GW 1050 in step S1025. Then, the PDN GW 1050 exchanges the IP-CAN session modification message with the PCRF 1060 in step S1030.
  • the PCRF 1060 transmits the policy and charging rule preparation message to the PDN GW 1050 in step S1035.
  • the policy and charging rule preparation message may include a SIPTO flag and a session continuity flag according to an embodiment of the present invention.
  • the PDN GW 1050 may deliver a bearer update request message to the Serving GW 1040.
  • the Serving GW 1040 may transmit a bearer update response message to the PDN GW 1050 in step S1050, and the PDN GW 1050 may transmit a confirmation message to the PRCF 1060 in step S1055.
  • 11 is a diagram showing the difference between the prior art and the present invention.
  • FIG. 11A is a diagram showing a SIPTO according to the prior art. 11A illustrates a SIPTO situation for multiple PDNs.
  • the plurality of IP sessions 1100 and 1110 may each include at least one EPS bearer.
  • the initially created bearers are called default EPS bearers 1101 and 1111, and the bearers created afterwards are called dedicated EPS bearers.
  • the quality of service (QoS) of each bearer is different.
  • whether each bearer is mapped to the core network or to the L-GW is predetermined at the time of bearer creation, and bearers included in the same IP session are all mapped to the core network or the L-GW in the same manner.
  • all bearers 1101, 1102, 1103, 1104 belonging to IP session 1100 are all mapped to the core network
  • all bearers 1111, 1112, 1113, 1114 belonging to IP session 111 are L. Mapped to GW.
  • the bearer 1102 belonging to the IP thin line 1100 may not be mapped to the L-GW.
  • 11B is a diagram illustrating a SIPTO according to an embodiment of the present invention.
  • the QoS value of each bearer may be the same.
  • the element determining the bearer's characteristics may further include bearer related parameters (SIPTO Flag, Session Continuity Flag, etc.) in addition to QoS.
  • each bearer included in the same IP session may be selectively mapped to the core network or the L-GW by factors such as bearer related parameters. For example, even though bearers belonging to the same IP session 1120, the bearer 1121 and the bearer 1122 may be mapped to the core network, and the bearer 1122 and the bearer 1124 may be mapped to the L-GW. .

Landscapes

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

Abstract

La présente invention concerne un procédé et un appareil de délestage de trafic dans un système de communication sans fil. Le procédé de délestage de trafic dans un appareil de gestion de délestage dans un système de communication sans fil, selon la présente invention, comporte les étapes consistant : à confirmer un paramètre associé à une porteuse par rapport à une porteuse aléatoire ; à confirmer l'état de canal de liaison terrestre du système de communication sans fil ; et à décider du délestage de la porteuse aléatoire en fonction du paramètre confirmé associé à la porteuse et de l'état de canal confirmé de la liaison terrestre.
PCT/KR2014/010103 2013-10-25 2014-10-27 Procédé et appareil de délestage de trafic dans un système de communication sans fil Ceased WO2015060695A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
KR10-2013-0127705 2013-10-25
KR1020130127705A KR20150047801A (ko) 2013-10-25 2013-10-25 무선 통신 시스템에서 트래픽 오프로드 방법 및 장치

Publications (1)

Publication Number Publication Date
WO2015060695A1 true WO2015060695A1 (fr) 2015-04-30

Family

ID=52993204

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/KR2014/010103 Ceased WO2015060695A1 (fr) 2013-10-25 2014-10-27 Procédé et appareil de délestage de trafic dans un système de communication sans fil

Country Status (2)

Country Link
KR (1) KR20150047801A (fr)
WO (1) WO2015060695A1 (fr)

Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090075876A (ko) * 2006-11-01 2009-07-09 콸콤 인코포레이티드 간섭 관리를 위한 셀간 전력 제어
US8103310B1 (en) * 2009-08-07 2012-01-24 Sprint Spectrum L.P. Methods and systems for using femtocells to address macro-network backhaul congestion
KR20120043082A (ko) * 2009-09-18 2012-05-03 닛본 덴끼 가부시끼가이샤 통신 시스템과 통신 제어 방법
JP2013046344A (ja) * 2011-08-26 2013-03-04 Nec Corp 通信システム、パケット中継装置、ユーザ端末及び通信方法
WO2013142361A1 (fr) * 2012-03-22 2013-09-26 Interdigital Patent Holdings, Inc. Procédé et appareil de décharge de trafic acheminé par le réseau terrestre

Patent Citations (5)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
KR20090075876A (ko) * 2006-11-01 2009-07-09 콸콤 인코포레이티드 간섭 관리를 위한 셀간 전력 제어
US8103310B1 (en) * 2009-08-07 2012-01-24 Sprint Spectrum L.P. Methods and systems for using femtocells to address macro-network backhaul congestion
KR20120043082A (ko) * 2009-09-18 2012-05-03 닛본 덴끼 가부시끼가이샤 통신 시스템과 통신 제어 방법
JP2013046344A (ja) * 2011-08-26 2013-03-04 Nec Corp 通信システム、パケット中継装置、ユーザ端末及び通信方法
WO2013142361A1 (fr) * 2012-03-22 2013-09-26 Interdigital Patent Holdings, Inc. Procédé et appareil de décharge de trafic acheminé par le réseau terrestre

Also Published As

Publication number Publication date
KR20150047801A (ko) 2015-05-06

Similar Documents

Publication Publication Date Title
WO2011142567A2 (fr) Procédé de transfert intercellulaire prenant en charge une mobilité de terminal
WO2011021876A2 (fr) Serveur pour plan de commande au niveau d'un réseau de communication mobile et procédé de commande de session basée sur sipto
WO2016006969A1 (fr) Procédé et dispositif de transfert intercellulaire entre des nœuds menb dans un système à petites cellules
WO2014046431A2 (fr) Procédé pour établir correctement un service d'accès ip local
WO2013009053A2 (fr) Procédé et appareil de prise en charge de mobilité d'équipement utilisateur
WO2019022342A1 (fr) Station de base et procédé de commande de qos de section sans fil
WO2015065062A1 (fr) Procédé et système de transfert intercellulaire
WO2017030399A1 (fr) Procédé et appareil d'accès d'ue
WO2016117979A1 (fr) Procédé et appareil prenant en charge un décrochage local dans une architecture à connectivité double
WO2013005992A2 (fr) Procédé permettant d'éviter l'échec du transfert intercellulaire
WO2015137787A1 (fr) Procédé pour supporter une commande d'accès d'ue
WO2012138099A2 (fr) Serveur destiné à se charger d'un plan de commande dans un réseau de communication mobile et procédé pour prendre en charge une mobilité par service de détournement de trafic dans le même serveur
WO2011136617A2 (fr) Serveur responsable du plan de commande dans un réseau de communication mobile et procédé destiné à commander un service sur un serveur
WO2014003455A1 (fr) Procédé de détermination de contrôle d'accès
WO2013051845A2 (fr) Procédé et appareil pour commander l'accès d'un équipement d'utilisateur dans un système de communication mobile
WO2017176013A1 (fr) Procédé pour traiter une requête d'accès provenant d'un équipement utilisateur (ue), et nœud de réseau
WO2015030557A1 (fr) Procédé et appareil de commutation de chemin de données dans un système de communication sans fil prenant en charge une communication de dispositif à dispositif
WO2012108660A2 (fr) Serveur pour plan de commande dans un réseau de communication mobile et procédé pour permettre au serveur de commander un service
WO2018038412A1 (fr) Procédé et équipement utilisateur permettant la connexion au moyen d'une pluralité d'accès dans un réseau de nouvelle génération
WO2009134064A2 (fr) Procédé et dispositif pour permettre l'interfonctionnement entre un système 3g et un système sae
WO2016021773A1 (fr) Procédé et système de flux vidéo à qs garantie, et serveur de transmission
WO2018052172A2 (fr) Appareil station de base, appareil terminal et procédé de commande de qos
WO2017026801A1 (fr) Procédé et dispositif de commande d'agrégation wlan
WO2015057035A1 (fr) Dispositif de réseau servant à soutenir une variation de passerelle dans un système de communication mobile et procédé d'activation de celui-ci
WO2014021581A1 (fr) Procédé permettant à un rn de prendre en charge une pluralité de systèmes d'accès sans fil

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

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

Country of ref document: EP

Kind code of ref document: A1