[go: up one dir, main page]

WO2018003480A1 - Dispositif de commande de communication, équipement utilisateur, et procédé de commande de communication - Google Patents

Dispositif de commande de communication, équipement utilisateur, et procédé de commande de communication Download PDF

Info

Publication number
WO2018003480A1
WO2018003480A1 PCT/JP2017/021739 JP2017021739W WO2018003480A1 WO 2018003480 A1 WO2018003480 A1 WO 2018003480A1 JP 2017021739 W JP2017021739 W JP 2017021739W WO 2018003480 A1 WO2018003480 A1 WO 2018003480A1
Authority
WO
WIPO (PCT)
Prior art keywords
route
switching point
network
user device
transmitted
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/JP2017/021739
Other languages
English (en)
Japanese (ja)
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.)
NTT Docomo Inc
Original Assignee
NTT Docomo Inc
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 NTT Docomo Inc filed Critical NTT Docomo Inc
Priority to JP2018525025A priority Critical patent/JP6954900B2/ja
Publication of WO2018003480A1 publication Critical patent/WO2018003480A1/fr
Anticipated expiration legal-status Critical
Ceased legal-status Critical Current

Links

Images

Classifications

    • 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/10—Flow control between communication endpoints
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • the present invention relates to a communication control device and a communication control method for controlling a route set between a user device and a core network, and a user device for executing communication using the route.
  • LTE including LTE-Advanced LTE-Advanced
  • LTE Long Term Evolution
  • 5G 5th generation mobile mobile communication systems
  • a local network capable of distributing specific content (for example, moving image content) accessed by the user apparatus (UE) as a form in the content distribution network (CDN) is included in the core network. It is considered to provide.
  • the local network includes a local server that caches the content stored on an external network (typically the Internet) of the core network.
  • the local network is provided at a position close to the radio access network (RAN) in terms of network topology, it is possible to improve responsiveness to content acquisition requests and reduce traffic within the core network (so-called traffic offload).
  • RAN radio access network
  • Non-Patent Document 1 When the content to be accessed is stored on the external network, when the UE starts accessing the content, the route passes through an anchor point (referred to as a central anchor point) provided near the external network. Is used.
  • the UE In order to allow the UE to access the local network that caches the content from such a state, it is an entity in the core network close to the local network, specifically, a communication device that provides a user plane (UP) function.
  • UP user plane
  • a method of branching the route from Serving Gateway (SGW) has been proposed (for example, Non-Patent Document 2).
  • the entity in the core network executes deep packet inspection (DPI) for monitoring the content of the packet transmitted by the UE, and directs the packet to the local network.
  • DPI deep packet inspection
  • the entity located on the route set between the UE and the core network is local in terms of network topology. It is necessary to shorten the routing path from the entity to the local network, which is provided near the network (local server). For this reason, depending on the relationship between the path set between the UE and the core network and the position of the local network, it may not be appropriate to direct the packet to the local network.
  • An object of the present invention is to provide a communication control device, a user device, and a communication control method that can be loaded.
  • the communication control device (CP function 30) includes a first path switching point (anchor point A 1 ) corresponding to an external network (external network 50) provided outside the core network, or the core network.
  • a route for the user apparatus (UE 100) set in the core network is controlled via a second route switching point (anchor point A 2 ) corresponding to the local network (local network 60) provided in the network.
  • the communication control device performs a second operation between the user device and the second route switching point.
  • a setting request transmitting unit that transmits a setting request (for example, Bearer Setup Request and RRC message) that requests the user apparatus and the communication apparatus that constitutes the second path switching point to set a path (Dedicated Bearer)
  • a request transmission unit 320 and an identification information transmission unit (identification information transmission unit 330) that transmits identification information (UL TFT) that can identify traffic to be transmitted to the local network via the second path to the user device.
  • UL TFT identification information
  • a user apparatus is configured to pass through a first path switching point corresponding to an external network provided outside the core network, or a second path switching point corresponding to a local network provided in the core network.
  • To establish a route with the core network In addition to the first route set between the user device and the first route switching point, the user device sets a second route between the user device and the second route switching point.
  • a setting unit route setting unit 130
  • a distribution unit distributed unit 140
  • a communication control method includes a first path switching point corresponding to an external network provided outside a core network, or a second path switching point corresponding to a local network provided in the core network.
  • the path for the user device set in the core network is controlled via the network.
  • the communication control device is configured to perform a first change between the user device and the second route switching point, in addition to the first route set between the user device and the first route switching point.
  • FIG. 1 is an overall schematic configuration diagram of a wireless communication system 10.
  • FIG. 2 is a functional block configuration diagram of the CP function 30.
  • FIG. 3 is a functional block configuration diagram of UE 100.
  • FIG. 4 is a diagram illustrating an entire communication sequence regarding bearer or session setting between the UE 100 and the core network (CP function 30 and UP function 40).
  • FIG. 5 is a diagram illustrating a configuration example of a bearer set between the UE 100 and the core network. 6, (a) and (b), when the local network 60 is installed in the same premises as SGW42 constituting an anchor point A 2, and if the local network 60 is not installed in the same premises as SGW42 It is a figure which shows the structural example of the bearer in.
  • FIG. 7 is an explanatory diagram of the traffic distribution operation by UE 100 to Default Bearer and Dedicated Bearer.
  • FIG. 8 is a diagram illustrating an example of a hardware configuration of the CP function 30 and the UE 100.
  • FIG. 1 is an overall schematic configuration diagram of a radio communication system 10 according to the present embodiment.
  • the radio communication system 10 is a radio communication system according to “5G” which is a successor system of Long Term Evolution (LTE).
  • LTE Long Term Evolution
  • the radio communication system 10 may be called FRA (Future Radio Access) or next-generation system (NextGen).
  • the radio communication system 10 includes a radio access network 20, a core network control plane function 30 (hereinafter, CP function 30), a core network user plane function 40 (hereinafter, UP function 40), and a user device 100 ( Hereinafter, UE100) is included. Further, an external network 50 is connected to the wireless communication system 10, specifically, the UP function 40.
  • CP function 30 core network control plane function 30
  • UP function 40 core network user plane function 40
  • UE100 user device 100
  • an external network 50 is connected to the wireless communication system 10, specifically, the UP function 40.
  • the radio access network 20 is a radio network according to radio access technology (RAT) defined in, for example, the 3rd Generation Partnership Project (3GPP), and includes a radio base station 200 (hereinafter, BS 200).
  • RAT radio access technology
  • 3GPP 3rd Generation Partnership Project
  • the CP function 30 and the UP function 40 are connected to the radio access network 20.
  • the CP function 30 and the UP function 40 form a core network of the wireless communication system 10, and provide a control plane function and a user plane function. That is, in the core network of the radio communication system 10, the control plane function that realizes control of the UE 100 and BS 200 and the user plane function that realizes transmission and reception of user data are clearly separated (CUPS: C / U plane separation) is adopted.
  • CP function 30 and UP function 40 can be configured by Serving Gateway (SGW), PDN Gateway (PGW) and Traffic Detection Function (TDF), respectively.
  • SGW Serving Gateway
  • PGW PDN Gateway
  • TDF Traffic Detection Function
  • the CP function 30 and the UP function 40 may be configured by a communication control device or a communication device (or a combination thereof) expressed by other names.
  • the CP function 30 includes a mobility management of the UE 100 and a control entity (not shown) that controls the route for the UE 100.
  • the UP function 40 includes a PGW 41 (PGW-U) and an SGW 42 (SGW-U).
  • the external network 50 is provided outside the core network and connected to the UP function 40.
  • a typical example of the external network 50 is the Internet, but the type of the external network 50 is not particularly limited, and may be a private network provided by an operator of the wireless communication system 10 or the like.
  • the local network 60 is provided in the core network and connected to the UP function 40.
  • the local network 60 is a network prepared by an operator of the radio communication system 10, and has a function of caching a part of content existing on the external network 50 and providing a specific service to the UE 100. Have.
  • the UE 100 and BS 200 execute wireless communication in accordance with a wireless communication technique defined in 3GPP. Further, the UE 100 sets a route via the anchor point A 1 or the anchor point A 2 provided in the UP function 40 based on the control by the CP function 30.
  • the UE 100 sets a bearer that is a logical communication path via the anchor point A 1 or the anchor point A 2 .
  • the anchor point A 1 (first route switching point) is provided in the core network, specifically, in the PGW 41, and corresponds to the external network 50. That is, when performing communication with an external network 50, bearers are set passing through the anchor point A 1.
  • the anchor point A 2 (second route switching point) is provided in the core network, specifically, in the SGW 42 and corresponds to the local network 60. That is, when performing the communication with the local network 60, bearers are set passing through the anchor point A 2.
  • An external server 51 is provided in the external network 50.
  • Examples of the external server 51 include various servers (mail server, web server, etc.) provided on the Internet.
  • a server holding content such as a moving image is particularly intended.
  • a local server 61 is provided in the local network 60.
  • the local server 61 has a function of providing a specific service by the operator of the radio communication system 10 to the UE 100 and a function of caching content such as a moving image held in the external server 51.
  • the content cached by the local server 61 is selected according to the frequency of content accessed by the UE 100 or the like.
  • FIG. 2 is a functional block configuration diagram of the CP function 30.
  • the CP function 30 includes a path control unit 310, a setting request transmission unit 320, and an identification information transmission unit 330.
  • the CP function 30 constitutes a communication control device.
  • CP function 30 may be called CN-CP (Core Network Control Plane).
  • CP function 30 is a reduced version of a mobile control entity and a network node such as SGW-C / PGW-C. It is a configuration that further pushes the concept of next-generation systems (NextGen) such as CUPS. It has become.
  • NextGen next-generation systems
  • the route control unit 310 controls the route for the UE 100. Specifically, the path control unit 310 controls setting and deletion of bearers that are logical communication paths set between the UE 100 and the core network.
  • the route control unit 310 controls setting and deletion of bearers that pass through the anchor point A 1 or the anchor point A 2 (see FIG. 1), specifically, Default Bearer and Dedicated Bearer.
  • Default Bearer is a bearer set by default, and Dedicated Bearer can be set as necessary.
  • the route control unit 310 instructs the setting request transmission unit 320 to set or delete the bearer based on a handover request from the UE 100 or a communication state of the UE 100.
  • the setting request transmission unit 320 transmits a setting request for requesting to set or delete a bearer to the UE 100 or the UP function 40.
  • the setting request transmission unit 320 transmits a Bearer Setup Request or Session Management Request to the UE 100 based on an instruction from the route control unit 310.
  • the setting request transmission unit 320 transmits Create Bearer Request or Create Session Request to the radio access network 20 based on an instruction from the route control unit 310.
  • the setting request transmission unit 320 transmits a setting request including identification information (UL ⁇ ⁇ TFT) that can identify traffic to be transmitted to the local network 60 based on an instruction from the identification information transmission unit 330, as will be described later. can do.
  • identification information UL ⁇ ⁇ TFT
  • the setting request transmission unit 320 includes a dedicated bearer between the UE 100 and the local network 60 in addition to the default bearer.
  • a setting request for requesting to set (second route) can be transmitted.
  • the setting request transmission unit 320 includes a dedicated bearer (second route) between the UE 100 and the anchor point A 2 in addition to the default bearer (first route) set between the UE 100 and the anchor point A 1. Can be requested to UE100. Similarly, the setting request transmitting section 320 can transmit the setting request to the SGW 42 (communication apparatus) constituting the anchor point A 2.
  • the setting request transmission unit 320 can transmit a setting request including an offload identifier indicating that traffic transmitted / received to / from the external network 50 is offloaded to the local network 60 to the SGW 42.
  • the setting request transmission unit 320 caches (copies) a part of content (such as video content) held by the external server 51 in the local server 61 provided in the local network 60
  • the setting request transmission unit 320 anchors with the UE 100 By setting the dedicated bearer between the point A 2 and the traffic originally transmitted / received to / from the external network 50 can be offloaded to the local network 60.
  • the setting request transmission unit 320 when the anchor point A 2 is not located on the Default Bearer, a setting request for causing the UE 100 to set a new session between the UE 100 and the anchor point A 2 , specifically, The Session Management Request described above can be transmitted.
  • the “session” mentioned here specifically means a “PDU session” described in 3GPP TR23.799, and communication information between the UE 100 and an IP network such as the external network 50. A logical path used for transmission.
  • the setting request transmitting section 320 if the anchor point A 2 on Default Bearer is not positioned against SGW42 constituting an anchor point A 2, sets a new session between the UE100 and the anchor point A 2
  • the setting request to be made specifically, the Create Session Request described above can be transmitted.
  • the identification information transmission unit 330 transmits identification information that can identify traffic to be transmitted to the local network 60 to the UE 100 via the Dedicated Bearer. Specifically, the identification information transmitting unit 330 instructs the setting request transmitting unit 320 to transmit a setting request including UL TFT that is a traffic flow template in the uplink.
  • the traffic flow to be transmitted to the local network 60 for example, the type of content cached in the local server 61 is expressed as a scalar value.
  • the UL-TFT may specifically define the type and content of the traffic flow.
  • the UL TFT is configured by packet filtering information used by the UE 100 to distribute a specific traffic flow, that is, a specific packet to a Dedicated Bearer instead of a Default Bearer.
  • FIG. 3 is a functional block configuration diagram of UE 100. As illustrated in FIG. 3, the UE 100 includes a control message reception unit 110, an identification information reception unit 120, a route setting unit 130, and a distribution unit 140.
  • the control message receiving unit 110 receives a control message transmitted from the radio access network 20. Specifically, control message receiving section 110 receives a message (RRC message) in the radio resource control layer (RRC layer). In particular, in the present embodiment, the control message receiving unit 110 receives RRC messages related to setting and deleting bearers (Default (Bearer and Dedicated Bearer).
  • Bearer Setup Request (or Session Management Request) transmitted from the CP function 30 to the radio access network 20 and an RRC message transmitted from the radio access network 20 (BS200) to the UE100 are transmitted to the UE100.
  • a “setting request” is configured.
  • the identification information receiving unit 120 receives identification information included in the RRC message transmitted from the radio access network 20, specifically, UL-TFT. As described above, the CP function 30 receives an RRC message including the contents of UL TFT expressed by a scalar value or the like.
  • the route setting unit 130 sets a bearer that is a logical communication route between the UE 100 and the core network based on the control message received by the control message receiving unit 110.
  • the route setting unit 130 sets a bearer between the UE 100 and the UP function 40 (PGW 41). More specifically, the route setting unit 130 sets the UE 100, the Default Bearer (first path) between the anchor points A 1.
  • the route setting unit 130 sets a bearer between the UE 100 and the UP function 40 (SGW 42). More specifically, it sets the UE 100, a Dedicated Bearer (second path) between the anchor points A 2.
  • the route setting unit 130 can set a Dedicated Bearer in addition to the Default ⁇ ⁇ ⁇ ⁇ Bearer when the Default Bearer has already been set. Specifically, the route setting unit 130 sets Dedicated Bearer in addition to Default Bearer based on the control message transmitted from the radio access network 20.
  • the distribution unit 140 distributes traffic, specifically packets, that the UE 100 transmits to the core network to either Default Bearer or Dedicated Bearer.
  • the distribution unit 140 identifies traffic to be transmitted via the Dedicated Bearer based on the identification information (UL TFT) received by the identification information receiving unit 120. This makes it possible to identify traffic to be transmitted to the local network 60.
  • identification information UL TFT
  • the distribution unit 140 distributes traffic (packets) to be transmitted via the Dedicated Bearer based on the identification information. That is, the distribution unit 140 distributes traffic to be transmitted via the Dedicated Bearer based on the traffic flow template (UL TFT) transmitted to the local network 60.
  • UL TFT traffic flow template
  • FIG. 4 shows an overall communication sequence regarding bearer or session setting between the UE 100 and the core network (CP function 30 and UP function 40).
  • the UE 100 transmits a PDU Session Establishment Request to the CP function 30 in order to start communication via the core network.
  • the PDU Session Establishment Request includes Data Network Name (DNN) that identifies the type of the external network 50 (S1).
  • DNN Data Network Name
  • the CP function 30 selects an anchor point based on information included in the PDU Session Establishment Request, for example, DNN, subscriber information of the UE 100, or information indicating mobility (S2).
  • the CP function 30 selects the anchor point A 1 (denoted as Anchor-1 in the figure).
  • the CP function 30 generates a session with the PGW 41 constituting the anchor point A 1 and provides the PGW 41 with forwarding rules for the corresponding traffic (IP packet) (S3). Specifically, the CP function 30 provides information on an application or server accessed by the UE 100, a destination IP address, and the like.
  • the CP function 30 transmits a PDU Session Establishment Accept that is a response to the PDU Session Establishment Request to the UE 100 (S4).
  • the UE 100 Upon receiving the PDU Session Establishment Accept, the UE 100 sets a default bearer between the anchor point A 1 and starts transmission / reception of uplink and downlink traffic (IP packets) (S5).
  • IP packets uplink and downlink traffic
  • the anchor point A 1 is an anchor point corresponding to the external network 50, and the Default Bearer is used for transferring IP packets between the UE 100 and the external network 50.
  • the PGW 41 provides information (traffic information) indicating the characteristics of traffic transmitted / received by the UE 100 to the CP function 30 periodically or when an event occurs (S6).
  • the PGW 41 provides the CP function 30 with information related to the destination or server that the UE 100 is accessing.
  • the CP function 30 determines whether or not a bearer using another anchor point should be set based on the traffic information provided from the PGW 41 (S7). Specifically, the CP function 30 determines whether there is content to be passed through an anchor point provided closer to the UE 100 in the network topology in the content accessed by the UE 100. To do.
  • the CP function 30 sends the content not only to the external server 51 on the external network 50 but also to the local server 61 on the local network 60. Determine if it is cached. CP function 30 determines that the content may have also cached in the local server 61, it is necessary to set a bearer via the anchor point A 2 and the corresponding local network 60.
  • the CP function 30 determines that it is necessary to set a bearer via the anchor point A 2 and determines to set a dedicated bearer between the UE 100 and the anchor point A 2 .
  • the CP function 30 transmits a Bearer Setup Request to the radio access network 20 in order to cause the UE 100 to set a Dedicated Bearer (S8).
  • the Bearer Setup Request includes UL TFT.
  • the UL TFT can be expressed as a scalar value, for example, and is associated with traffic to be transmitted via the Dedicated Bearer.
  • CP function 30 instead of the Bearer Setup Request, and transmits the Session Management Request to the radio access network 20.
  • Default anchor point A 2 on Bearer is for setting the Dedicated Bearer when not located, further described below.
  • the radio access network 20 When receiving the Bearer Setup Request (or Session Management Request), the radio access network 20 performs reconfiguration in the RRC layer with the UE 100 to set the Dedicated Bearer (S9). Specifically, the radio access network 20 and the UE 100 change the configuration (bearer setting state) in the RRC layer by transmitting and receiving RRC messages (such as RRC Connection Reconfiguration and RRC Connection Reconfiguration ⁇ ⁇ Complete).
  • RRC messages such as RRC Connection Reconfiguration and RRC Connection Reconfiguration ⁇ ⁇ Complete).
  • the radio access network 20 transmits a Bearer Setup Response that is a response to the Bearer Setup Request to the CP function 30 (S10).
  • UE100 transmits Session Management Response to radio access network 20 ( S11). Further, when receiving the Session Management Response from the UE 100, the wireless access network 20 transfers the Session Management Response to the CP function 30 (S12).
  • CP function 30, based on the determination that it is necessary to set a bearer via the anchor point A 2 at step S7, transmits a the Create Bearer Request to the SGW 42 (S13). Incidentally, if the anchor point A 2 on Default Bearer is not located, CP function 30, instead of the Create Bearer Request, and transmits the the Create Session Request to the SGW 42.
  • Create Bearer Request includes an offload identifier (Offload flag) indicating that traffic destined for the external network 50 is offloaded to the local network 60, and identification information (UL TFT) identifying traffic to be transmitted to the local network 60 It is. Similarly, Create Session Request also includes Offload flag and UL TFT.
  • Offload flag an offload identifier
  • UL TFT identification information
  • SGW42 sets UE100 and Dedicated Bearer based on Create Bearer Request (or Create Session Request) (S14).
  • Dedicated Bearer is established between the UE100 and the anchor point A 2.
  • SGW42 When SGW42 completes the setting of Dedicated Bearer, it sends Create Bearer Response (or Create Session Response) to CP function 30.
  • the UE 100 starts transmission / reception of traffic in the upstream and downstream directions (IP packets) with the local server 61 on the local network 60 via the Dedicated Bearer (S15). Note that other traffic that is not offloaded to the local network 60 is continuously transmitted and received via the Default ⁇ Bearer.
  • FIG. 5 shows a configuration example of a bearer set between the UE 100 and the core network.
  • Default Bearer is set between UE 100 and UP-2 that constitutes UP function 40.
  • the UE 100 transmits and receives IP packets in the uplink direction and the downlink direction with the external server 51.
  • UP-1 to UP-3 shown in FIG. 5 are network nodes (communication devices) constituting the UP function 40.
  • UP-1 to UP-3 may be logical nodes, and may be configured by a plurality of SGWs or PGWs, or a combination of SGW / PGWs.
  • UP-2 may correspond to the above-described PGW 41.
  • IP @ 1 An anchor point provided in UP-2, specifically, an anchor point A1 called a central anchor point, assigns “IP @ 1” as an IP address for the UE.
  • IP @ 1 is shown for convenience of explanation, and an IP address according to IPv4 or IPv6 is actually assigned.
  • Dedicated Bearer is set between UE 100 and UP-3.
  • the Dedicated Bearer is set by transmitting a Bearer Setup Request or Session Management Request to the UE 100. A connection can be used.
  • the IP address addressed to the UE 100 as viewed from the dedicated bearer that is, the anchor point A 2 corresponding to the local network 60, can also maintain “IP @ 1”.
  • 6A and 6B show a bearer when the local network 60 is installed in the same premises as the SGW 42 constituting the anchor point A 2 and when the local network 60 is not installed in the same premises as the SGW 42.
  • the example of a structure is shown.
  • FIG. 6 (a) installed in the same premises as the SGW 42 to the local network 60 constitutes the anchor point A 2, specifically, because the local network 60 is co-The locate in the SGW 42, Dedicated Bearer also, Default Bearer Similarly to SGW42, it is set in SGW42.
  • the local network 60 is not installed in the same premises as SGW42 constituting an anchor point A 2, Dedicated Bearer, in local UP node 43 which is installed in the same premises and the local network 60 Is set.
  • the local UP node 43 is configured by a network node such as SGW.
  • the same premises means a network in which IP packets can be transferred mainly by processing by a lower layer without using a protocol stack such as an S-U interface.
  • FIG. 7 is an explanatory diagram of traffic distribution operation by UE 100 to Default Bearer and Dedicated Bearer. As shown in FIG. 7, the UE 100 holds the UL TFT (see the triangle in the figure) transmitted from the CP function 30 via the radio access network 20 (BS200).
  • BS200 radio access network 20
  • UE100 distributes traffic for local network 60 to Dedicated Bearer based on UL TFT stored in UE100. Specifically, when a specific type of traffic (for example, a content distribution request or control for a specific video content distribution server) is specified by UL ⁇ ⁇ ⁇ ⁇ TFT, the UE 100 filters the IP packet to be transmitted, that is, the IP Monitor packet contents and distribute IP packets related to the corresponding traffic to Dedicated Bearer.
  • a specific type of traffic for example, a content distribution request or control for a specific video content distribution server
  • UE100 distributes IP packets related to traffic not specified by UL ⁇ ⁇ ⁇ ⁇ TFT to Default Bearer.
  • the CP function 30 can cause a dedicated bearer between the UE 100 and the anchor point A 2 in addition to the default bearer.
  • Anchor point A 2 corresponds to the local network 60, UE 100, while maintaining the setting of the Default Bearer for the external network 50, it can be set Dedicated Bearer for the local network 60.
  • the CP function 30 transmits identification information (UL TFT) that can identify traffic to be transmitted to the local network 60 to the UE 100.
  • UL TFT identification information
  • the UE 100 does not need to access the external network 50 via the DefaulterBearer for content cached in the local network 60, and can access the local network 60 provided in the core network. It becomes possible.
  • Non-Patent Document 2 in the core network, basically, Deep Packet Inspection (DPI) is executed for all UEs (called UL-CL). There is a concern that the processing load on the core network will become extremely high.
  • DPI Deep Packet Inspection
  • the dedicated bearer is set using the same IP address (IP @ 1) addressed to the UE 100 by using a session management request or the like.
  • IP @ 1 IP address
  • the network nodes SGW42 to local UP node 43
  • a new IP address is not required when specific traffic is offloaded to the local network 60. That is, in this embodiment, a new PDN connection is not set, and a single UE IP address is used for Default ⁇ Bearer and Dedicated Bearer. Further, since it is not necessary to once release the set PDN connection and set a new PDN connection again, communication between the UE 100 and the core network is not interrupted.
  • the CP function 30 sends a setting request (Create Bearer Request or Create Session Request) including an offload identifier (Offload flag) indicating that traffic transmitted to and received from the external network 50 is offloaded to the local network 60. Can be transmitted to the SGW 42 constituting the anchor point A 2 .
  • the SGW 42 can recognize that the Dedicated Bearer is used to offload specific traffic to the local network 60.
  • SGW42 recognizes such a state, it can be determined that Default Bearer can be used even if a failure occurs in Dedicated Bearer, and IP packet transfer processing related to other traffic such as offload can be continued. It is possible to realize such a response.
  • the CP function 30 causes the UE 100 and the SGW 42 to set a new session (PDU session) between the UE 100 and the SGW 42 when the anchor point A 2 is not located on the Default Bearer ( Session Management Request, Create Session Request) can be transmitted.
  • PDU session a new session between the UE 100 and the SGW 42 when the anchor point A 2 is not located on the Default Bearer ( Session Management Request, Create Session Request) can be transmitted.
  • the dedicated Bearer combined with the set Default Bearer is assigned to the session. Can be set using.
  • the CP function 30 can transmit a traffic flow template (UL TFT) to be transmitted to the local network 60 to the UE 100.
  • UL TFT traffic flow template
  • the UL-TFT is configured by packet filtering information used by the UE 100 to distribute a specific packet to a Dedicated-Bearer.
  • the UE 100 sets Default Bearer and Dedicated Bearer based on the setting request from the CP function 30. Further, the UE 100 distributes traffic to be transmitted via the Dedicated Bearer based on the UL TFT from the CP function 30. Specifically, the UE 100 distributes traffic to be transmitted through the Dedicated Bearer based on the UL-TFT.
  • the UE 100 can appropriately and dynamically select the traffic to be distributed to the Dedicated Bearer based on the communication state of the UE 100 or the type of content held in the local network 60.
  • a setup request including UL TFT (for example, Bearer Setup Request and RRC message) is transmitted.
  • UL TFT may be transmitted as independent information separately from the setting request. Good.
  • the anchor point A 1 is configured by the PGW 41.
  • the anchor point A 1 is not necessarily a PGW as long as it is a communication device that configures the UP function 40.
  • each functional block may be realized by one device physically and / or logically coupled, and two or more devices physically and / or logically separated may be directly and / or indirectly. (For example, wired and / or wireless) and may be realized by the plurality of devices.
  • FIG. 8 is a diagram illustrating an example of a hardware configuration of the CP function 30 and the UE 100.
  • the CP function 30 and the UE 100 may be configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like.
  • Each functional block of the CP function 30 and the UE 100 is realized by any hardware element of the computer device or a combination of the hardware elements.
  • the processor 1001 controls the entire computer by operating an operating system, for example.
  • the processor 1001 may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like.
  • CPU central processing unit
  • the memory 1002 is a computer-readable recording medium, and includes, for example, at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), and the like. May be.
  • the memory 1002 may be called a register, a cache, a main memory (main storage device), or the like.
  • the memory 1002 can store a program (program code) that can execute the method according to the above-described embodiment, a software module, and the like.
  • the storage 1003 is a computer-readable recording medium such as an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disc, a magneto-optical disc (eg a compact disc, a digital versatile disc, a Blu-ray). (Registered trademark) disk, smart card, flash memory (for example, card, stick, key drive), floppy (registered trademark) disk, magnetic strip, and the like.
  • the storage 1003 may be referred to as an auxiliary storage device.
  • the above-described storage medium may be, for example, a database, a server, or other suitable medium including the memory 1002 and / or the storage 1003.
  • the communication device 1004 is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also referred to as a network device, a network controller, a network card, a communication module, or the like.
  • the input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that accepts an input from the outside.
  • the output device 1006 is an output device (for example, a display, a speaker, an LED lamp, or the like) that performs output to the outside. Note that the input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).
  • each device such as the processor 1001 and the memory 1002 is connected by a bus 1007 for communicating information.
  • the bus 1007 may be configured with a single bus or may be configured with different buses between apparatuses.
  • notification of information includes physical layer signaling (eg, DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (eg, RRC signaling, MAC (Medium Access Control) signaling, broadcast information (MIB ( Master (Information Block), SIB (System Information Block)), other signals, or combinations thereof, and RRC signaling may also be referred to as RRC messages, eg, RRC Connection Connection message, RRC It may be a Connection ⁇ ⁇ Reconfiguration message.
  • RRC messages eg, RRC Connection Connection message, RRC It may be a Connection ⁇ ⁇ Reconfiguration message.
  • input / output information may be stored in a specific location (for example, a memory) or may be managed by a management table.
  • the input / output information can be overwritten, updated, or appended.
  • the output information may be deleted.
  • the input information may be transmitted to other devices.
  • the specific operation that is performed by the CP function 30 may be performed by another network node (device). Further, the function of the CP function 30 may be provided by a combination of a plurality of other network nodes.
  • the channel and / or symbol may be a signal.
  • the signal may be a message.
  • system and “network” may be used interchangeably.
  • the parameters described above may be represented by absolute values, may be represented by relative values from predetermined values, or may be represented by other corresponding information.
  • the radio resource may be indicated by an index.
  • BS 200 can accommodate one or a plurality of (for example, three) cells (also called sectors).
  • a base station accommodates multiple cells, the entire coverage area of the base station can be partitioned into multiple smaller areas, each smaller area being a base station subsystem (eg, indoor small base station RRH: Remote Radio Head) can also provide communication services.
  • RRH Remote Radio Head
  • cell refers to part or all of the coverage area of a base station and / or base station subsystem that provides communication services in this coverage.
  • base station eNB
  • cell ector
  • a base station may also be referred to in terms such as a fixed station (fixed station), NodeB, eNodeB (eNB), access point (access point), femto cell, small cell, and the like.
  • UE100 is a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal by those skilled in the art , Remote terminal, handset, user agent, mobile client, client, or some other appropriate terminology.
  • the phrase “based on” does not mean “based only on”, unless expressly specified otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • packets related to specific content are more reliably directed (offloaded) to the local network (local server) while suppressing processing load on the core network. be able to.
  • Wireless communication system 20 Wireless access network 30 CP function 40 UP function 41 PGW 42 SGW 43 Local UP node 50 External network 51 External server 60 Local network 61 Local server 100 UE 110 Control message receiver 120 Identification information receiver 130 Route setting unit 140 Distribution unit 200 BS 310 Route control unit 320 Setting request transmission unit 330 Identification information transmission unit 1001 Processor 1002 Memory 1003 Storage 1004 Communication device 1005 Input device 1006 Output device 1007 Bus A 1 , A 2 Anchor point

Landscapes

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

Abstract

L'invention concerne un dispositif de commande de communication, un équipement utilisateur et un procédé de commande de communication, au moyen desquels des paquets relatifs à un contenu spécifique peuvent être déviés de manière plus fiable (délestés) vers un réseau local (serveur local), tout en réduisant la charge de traitement dans un réseau central. Une fonction CP (30) commande une route pour l'équipement utilisateur (UE) (100) qui a été établie dans un réseau central, ladite commande étant effectuée par l'intermédiaire d'un ancrage -1, qui est un point de commutation de route correspondant à un réseau externe (50), ou d'un ancrage -2, qui est un point de commutation de route correspondant à un réseau local (60). La fonction CP (30) demande à ce que l'UE (100) et une SGW (42) établissent un support dédié entre l'UE (100) et l'ancrage -2, en plus d'un support par défaut établi entre l'UE (10) et l'ancrage -1. En outre, la fonction CP (30) transmet à l'UE (100) un TFT UL capable d'identifier le trafic qui devrait être transmis au réseau local (60).
PCT/JP2017/021739 2016-06-30 2017-06-13 Dispositif de commande de communication, équipement utilisateur, et procédé de commande de communication Ceased WO2018003480A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2018525025A JP6954900B2 (ja) 2016-06-30 2017-06-13 通信制御装置、ユーザ装置及び通信制御方法

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2016-129795 2016-06-30
JP2016129795 2016-06-30

Publications (1)

Publication Number Publication Date
WO2018003480A1 true WO2018003480A1 (fr) 2018-01-04

Family

ID=60785358

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2017/021739 Ceased WO2018003480A1 (fr) 2016-06-30 2017-06-13 Dispositif de commande de communication, équipement utilisateur, et procédé de commande de communication

Country Status (2)

Country Link
JP (1) JP6954900B2 (fr)
WO (1) WO2018003480A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2023534442A (ja) * 2020-07-24 2023-08-09 富士通株式会社 通信ネットワークにおける構成可能なアプリケーション・データ・フィルタリング

Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2015052917A1 (fr) * 2013-10-09 2015-04-16 日本電気株式会社 Système de communication, dispositif de communication, et procédé de contrôle de communication
JP2015084580A (ja) * 2009-06-26 2015-04-30 シャープ株式会社 移動局装置および位置管理装置
JP2015233170A (ja) * 2012-09-28 2015-12-24 シャープ株式会社 移動通信システム、位置管理装置、ホーム基地局装置、移動局装置及び移動通信システムにおける通信方法
JP2016082438A (ja) * 2014-10-17 2016-05-16 日本電気株式会社 通信制御装置、無線通信システム、通信制御方法及び無線基地局

Family Cites Families (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20150215840A1 (en) * 2014-01-30 2015-07-30 Intel IP Corporation Systems, methods and devices for application specific routing in dual connectivity
JP6434055B2 (ja) * 2014-06-11 2018-12-05 コンヴィーダ ワイヤレス， エルエルシー ローカルコンテンツリダイレクトのためのマッピングサービス
WO2016076287A1 (fr) * 2014-11-11 2016-05-19 シャープ株式会社 Dispositif terminal, dispositif de station de base, mme (entité de gestion de mobilité) et procédé de commande de communications

Patent Citations (4)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015084580A (ja) * 2009-06-26 2015-04-30 シャープ株式会社 移動局装置および位置管理装置
JP2015233170A (ja) * 2012-09-28 2015-12-24 シャープ株式会社 移動通信システム、位置管理装置、ホーム基地局装置、移動局装置及び移動通信システムにおける通信方法
WO2015052917A1 (fr) * 2013-10-09 2015-04-16 日本電気株式会社 Système de communication, dispositif de communication, et procédé de contrôle de communication
JP2016082438A (ja) * 2014-10-17 2016-05-16 日本電気株式会社 通信制御装置、無線通信システム、通信制御方法及び無線基地局

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2023534442A (ja) * 2020-07-24 2023-08-09 富士通株式会社 通信ネットワークにおける構成可能なアプリケーション・データ・フィルタリング
JP7444329B2 (ja) 2020-07-24 2024-03-06 富士通株式会社 通信ネットワークにおける構成可能なアプリケーション・データ・フィルタリング

Also Published As

Publication number Publication date
JP6954900B2 (ja) 2021-10-27
JPWO2018003480A1 (ja) 2019-04-18

Similar Documents

Publication Publication Date Title
EP3723416B1 (fr) Procédé et appareil de traitement de session
US11178717B2 (en) Traffic distribution method through multi-access network in a network and network entity performing the same
EP2717538B1 (fr) Procédé et système de communication, dispositif de réseau d'accès et serveur d'application
US11064388B2 (en) Traffic distribution method through multi-access network in a network and network entity performing the same
JP5716975B2 (ja) トラフィックオフロード方法およびコアネットワークデバイス
CN107548127B (zh) 支持数据传输的方法和设备
US20210289390A1 (en) Method for implementing traffic splitting
EP3209043B1 (fr) Procédé, appareil, et système de gestion de mobilité
Nguyen et al. Proposal and evaluation of SDN‐based mobile packet core networks
US10945180B2 (en) Mobility management method, apparatus, and system
JP2019521588A (ja) 通信制御方法および関連するネットワーク要素
US9729456B2 (en) Service data transmission processing method and device and communication system
US20190260857A1 (en) Data Packet Processing Method, Control Plane Network Element, And User Plane Network Element
CN103888959A (zh) 小小区通信的方法、系统及其设备
KR102017167B1 (ko) 무선 통신 시스템에서 데이터 트래픽 분산을 위한 방법 및 장치
JP6166800B2 (ja) 通信方法及びシステム、アクセスネットワーク装置、並びにアプリケーションサーバ
CN105531961A (zh) 虚拟用户特定服务网关的系统和方法
KR102243263B1 (ko) 가상 랜 게이트웨이 시스템, 제어 평면 게이트웨이의 동작 방법 및 mme의 동작 방법
EP3364610B1 (fr) Procédé, dispositif et système permettant de déployer une fonction de transfert de flux de services
JP6954900B2 (ja) 通信制御装置、ユーザ装置及び通信制御方法
JP7300538B2 (ja) アンカーポイント制御装置及びアンカーポイント制御方法
WO2018082517A1 (fr) Procédé, élément de réseau et système de suppression de tunnel de plan utilisateur
EP4354919B1 (fr) Dérivation locale de multidiffusion pour équipement des locaux d'abonné dans une convergence filaire sans fil 5g au niveau d'une fonction de passerelle d'accès
EP2579642B1 (fr) Procédé, dispositif et système de commande d'échange de trafic de localisation dans un réseau à large bande mobile
WO2012129997A1 (fr) Procédé et dispositif pour traiter une connexion d'accès à un réseau local

Legal Events

Date Code Title Description
WWE Wipo information: entry into national phase

Ref document number: 2018525025

Country of ref document: JP

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

Ref document number: 17819844

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

Country of ref document: EP

Kind code of ref document: A1