WO2014125777A1 - Système de communication mobile, procédé de commande de communication et support lisible par ordinateur non transitoire - Google Patents

Système de communication mobile, procédé de commande de communication et support lisible par ordinateur non transitoire Download PDF

Info

Publication number
WO2014125777A1
WO2014125777A1 PCT/JP2014/000453 JP2014000453W WO2014125777A1 WO 2014125777 A1 WO2014125777 A1 WO 2014125777A1 JP 2014000453 W JP2014000453 W JP 2014000453W WO 2014125777 A1 WO2014125777 A1 WO 2014125777A1
Authority
WO
WIPO (PCT)
Prior art keywords
mobile terminal
shared
cnb
bearer
mobility management
Prior art date
Application number
PCT/JP2014/000453
Other languages
English (en)
Japanese (ja)
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 WO2014125777A1 publication Critical patent/WO2014125777A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H04W76/12—Setup of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04L—TRANSMISSION OF DIGITAL INFORMATION, e.g. TELEGRAPHIC COMMUNICATION
    • H04L61/00—Network arrangements, protocols or services for addressing or naming
    • H04L61/50—Address allocation
    • H04L61/5007—Internet protocol [IP] addresses
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W60/00—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration
    • H04W60/04—Affiliation to network, e.g. registration; Terminating affiliation with the network, e.g. de-registration using triggered events
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/20—Manipulation of established connections
    • H04W76/22—Manipulation of transport tunnels
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/186—Processing of subscriber group data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/18—Processing of user or subscriber data, e.g. subscribed services, user preferences or user profiles; Transfer of user or subscriber data
    • H04W8/20—Transfer of user or subscriber data
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W8/00—Network data management
    • H04W8/26—Network addressing or numbering for mobility support
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/16—Interfaces between hierarchically similar devices
    • H04W92/24—Interfaces between hierarchically similar devices between backbone network devices

Definitions

  • This application relates to a mobile communication system, for example, communication control for user packet transfer.
  • a multiple access mobile communication system shares wireless resources including at least one of time, frequency, and transmission power among multiple mobile terminals, so that multiple mobile terminals can perform wireless communication substantially simultaneously. It is possible to do.
  • Typical multiple access schemes are TDMA (Time Division Multiple Access), FDMA (Frequency Division Multiple Access), CDMA (Code Division Multiple Access), OFDMA (Orthogonal Frequency Division Multiple Access), or a combination thereof.
  • the term mobile communication system used in this specification means a multiple access mobile communication system unless otherwise specified.
  • the mobile communication system includes a mobile terminal and a network.
  • the network includes a radio access network (Radio Access RA Network (RAN)) and a core network (Mobile Core Network (CN)).
  • the mobile terminal communicates with an external network (for example, the Internet, a packet data network, Public Switched Telephone Network (PSTN)) via the RAN and the CN.
  • the mobile communication system is, for example, Universal Mobile Telecommunications System (UMTS) or Evolved Packet System (EPS) of 3rd Generation Partnership Project (3GPP).
  • UMTS Universal Mobile Telecommunications System
  • EPS Evolved Packet System
  • RAN is, for example, Universal Terrestrial Radio Access Network (UTRAN) or Evolved UTRAN (E-UTRAN).
  • the CN is, for example, General Packet Radio Service (GPRS) packet core or Evolved Packet Core (EPC).
  • GPRS General Packet Radio Service
  • a mobile communication system needs to create a data bearer for transferring user packets between an external network and a mobile terminal for each mobile terminal. This is because quick switching / relocation of packet transfer routes is required to provide mobility for mobile terminals.
  • the data bearer is, for example, a UMTS bearer (General Packet Radio Service (GPRS) bearer) or an EPS bearer.
  • the data bearer includes a core network bearer (hereinafter referred to as CNB) set in the CN and a radio access bearer (hereinafter referred to as RAB) set in the RAN.
  • CNB core network bearer
  • RAB radio access bearer
  • the CNB is a tunnel set between an external gateway and a forwarding node arranged in CN, that is, a logical transmission path.
  • the external gateway is a gateway node arranged at the boundary with the external network.
  • the forwarding node is a node arranged at the boundary with the RAN.
  • the CNB is, for example, a UMTS CNB (ie, a GPRS Tunneling Protocol (GTP) tunnel) or an EPS S5 / S8 bearer (ie, a GTP tunnel).
  • the external gateway is, for example, GatewayGateGPRS Support Node (GGSN) or Packet Data Network Gateway (P-GW).
  • the forwarding node is, for example, a user plane function of Serving GPRS Support Node (SGSN) or Serving Gateway (S-GW).
  • RAB is a bearer set between a CN forwarding node and a mobile terminal.
  • the RAB includes a bearer set between the RAN and the CN and a radio bearer.
  • the bearer set between the RAN and the CN is set between the RAN node responsible for Radio Link Control (RLC) and Radio Resource Control (RRC) and the CN forwarding node.
  • the radio bearer is set between the above-described RAN node and the mobile terminal in the RAN.
  • the RAN node responsible for RLC and RRC is, for example, a RadioSNetwork Controller (RNC) of UMTS or an EPS base station (evolved NodeB (eNB)).
  • RNC RadioSNetwork Controller
  • eNB evolved NodeB
  • the bearer set between the RAN and the CN is, for example, a UMTS Iu bearer (that is, a GTP tunnel) or an EPS S1 bearer (that is, a GTP tunnel).
  • the radio bearer is, for example, a UMTS Uu bearer or an EPS LTE-Uu bearer.
  • the forwarding node needs to establish a CNB for each mobile terminal.
  • the forwarding node must store and manage a tunnel identifier (tunnel endpoint identifier), an external gateway user plane address (e.g. Internet Protocol (IP) address), and the like as tunnel settings for the CNB.
  • IP Internet Protocol
  • the external gateway assigns a user plane address (eg IP address) for connecting to the external network to a mobile terminal attached to the CN, as well as tunnel setting related to the CNB, charging control, and Quality of ⁇ ⁇ ⁇ ⁇ Service (QoS) Control etc.
  • IP Internet Protocol
  • Non-Patent Document 1 establishes and restores a data bearer (that is, an EPS bearer) for transferring a user packet of a mobile terminal in response to an attachment of the mobile terminal to a CN or a service request in EPS. The procedure is described.
  • a data bearer that is, an EPS bearer
  • the CN must generate a CNB for each mobile terminal and manage them.
  • the external gateway and the forwarding node are required to have a capability to cope with an increase in processing such as tunnel setting / management and IP address allocation. Specifically, it is necessary to increase the performance of the forwarding node or to additionally install it.
  • the present inventor in the past two Japanese patent applications, Japanese Patent Application No. 2011-217383 and Japanese Patent Application No. 2012-2114050, uses one CNB for user packet transfer of a plurality of mobile terminals. We propose an architecture and method that can share the same.
  • This application provides an improvement of the architecture and method proposed in Japanese Patent Application No. 2011-217383 and Japanese Patent Application No. 2012-2114050.
  • one of the objects shown in the present application is to contribute to the improvement of the utilization efficiency of the shared CNB in an architecture in which one CNB is shared for user packet transfer of a plurality of mobile terminals.
  • Another object presented in the present application is to enable a plurality of mobile terminals belonging to different mobility management nodes to use one shared CNB in an architecture in which one CNB is shared for user packet transfer of a plurality of mobile terminals.
  • the mobile communication system includes a core network including a mobility management node, a plurality of forwarding nodes, and an external gateway.
  • the mobility management node is configured to manage a shared core network bearer (CNB) shared for user packet transfer of a plurality of mobile terminals belonging to a mobile terminal group.
  • the management of the shared CNB is a first mobile terminal belonging to the mobile terminal group while the shared CNB is already set between a first transfer node of the plurality of transfer nodes and the external gateway. Selecting the first forwarding node for the first mobile terminal when a new bearer establishment request is received from.
  • the mobile communication system includes a core network including a subscriber server, a mobility management node, a forwarding node, and an external gateway.
  • the subscriber server notifies the mobility management node of the user plane address of each mobile terminal belonging to the mobile terminal group.
  • the mobility management node controls the setting of the shared CNB so that a user packet corresponding to the user plane address is transferred in a shared core network bearer (CNB).
  • the shared CNB is set between the forwarding node and the external gateway, and is shared for user packet forwarding of a plurality of mobile terminals belonging to the mobile terminal group.
  • the mobile communication system includes a core network including a mobility management node, a forwarding node, and an external gateway.
  • the mobility management node In response to a request from a first mobile terminal belonging to a mobile terminal group, the mobility management node sends a request message to the forwarding node to set up a shared core network bearer (CNB) for the first mobile terminal.
  • the shared CNB is a core network bearer shared for user packet transfer of a plurality of mobile terminals belonging to the mobile terminal group.
  • the external gateway receives a control message based on the request message from the forwarding node, assigns a user plane address to the first mobile terminal, and transmits a user packet with the user plane address specified as a destination. Set the packet filter to flow to the shared CNB.
  • the mobile communication system includes a core network including a subscriber server, a mobility management node, a forwarding node, and an external gateway.
  • the forwarding node and the external gateway set between the forwarding node and the external gateway a shared core network bearer (CNB) that is shared for user packet transfer of a plurality of mobile terminals belonging to the mobile terminal group.
  • the subscriber server transmits a notification indicating whether the shared CNB is used for any mobile terminal belonging to the mobile terminal group to the mobility management node.
  • the mobility management node receives the notification and controls bearer configuration for a first mobile terminal belonging to the mobile terminal group.
  • the mobile communication system includes a core network including a mobility management node, a forwarding node, and an external gateway.
  • the forwarding node and the external gateway set between the forwarding node and the external gateway a shared core network bearer (CNB) that is shared for user packet transfer of a plurality of mobile terminals belonging to the mobile terminal group.
  • the forwarding node transmits a notification indicating whether the shared CNB is used for any mobile terminal belonging to the mobile terminal group to the mobility management node.
  • the mobility management node receives the notification and controls bearer configuration for a first mobile terminal belonging to the mobile terminal group.
  • the first aspect described above can contribute to an improvement in utilization efficiency of the shared CNB in an architecture in which one CNB is shared for user packet transfer of a plurality of mobile terminals. Further, in the second to fifth aspects described above, in the architecture in which one CNB is shared for user packet transfer of a plurality of mobile terminals, a plurality of mobile terminals belonging to different mobility management nodes share one shared CNB. Improvements can be provided to make it available.
  • FIG. 3 is a block diagram showing a configuration example of a mobile communication system according to an embodiment (improved B-1).
  • FIG. 2 is a block diagram showing a configuration example of a mobile communication system according to an embodiment (improved B-2).
  • FIG. 3 is a block diagram showing a configuration example of a mobile communication system according to an embodiment (improved B-3).
  • FIG. 4 is a block diagram showing a configuration example of a mobile communication system according to an embodiment (improved B-4). It is a sequence diagram which shows an example of the bearer establishment procedure which concerns on embodiment (improvement B-1, the first mobile terminal).
  • FIG. 6 is a sequence diagram showing an example of the bearer establishment procedure which concerns on embodiment (improvement B-1, the first mobile terminal).
  • FIG. 6 is a sequence diagram showing an example of a bearer establishment procedure according to the embodiment (improved B-1, second and subsequent mobile terminals).
  • FIG. 6 is a sequence diagram showing an example of a bearer establishment procedure according to the embodiment (improved B-1, second and subsequent mobile terminals).
  • It is a sequence diagram which shows an example of the bearer restoration procedure which concerns on embodiment (improvement B-1).
  • FIG. 6 is a sequence diagram showing an example of a bearer establishment procedure according to the embodiment (improved B-2, second and subsequent mobile terminals).
  • FIG. 6 is a sequence diagram showing an example of a bearer establishment procedure according to the embodiment (improved B-2, second and subsequent mobile terminals). It is a sequence diagram which shows an example of the bearer restoration procedure which concerns on embodiment (improvement B-2). It is a sequence diagram which shows an example of the bearer establishment procedure which concerns on embodiment (improvement B-3, the first mobile terminal). It is a sequence diagram which shows an example of the bearer establishment procedure which concerns on embodiment (improvement B-3, the first mobile terminal).
  • FIG. 7 is a sequence diagram showing an example of a bearer establishment procedure according to the embodiment (improved B-3, second and subsequent mobile terminals).
  • FIG. 7 is a sequence diagram showing an example of a bearer establishment procedure according to the embodiment (improved B-3, second and subsequent mobile terminals).
  • FIG. 6 is a sequence diagram showing an example of a bearer establishment procedure according to the embodiment (improved B-4, second and subsequent mobile terminals).
  • FIG. 6 is a sequence diagram showing an example of a bearer establishment procedure according to the embodiment (improved B-4, second and subsequent mobile terminals).
  • FIG. 1 shows a configuration example of a mobile communication system according to some embodiments including this embodiment.
  • the mobile communication system includes a RAN 10 and a CN 20.
  • the RAN 10 includes a base station 2.
  • the base station 2 is connected to a mobile terminal (UE) 1 by radio access technology.
  • the mobile terminal 1 has a radio interface, is connected to the base station 2 by radio access technology, and is connected to the CN 20 via the RAN 10.
  • the mobile terminal 1 communicates with the external network 9 via the RAN 10 and the CN 20.
  • the external network 9 is the Internet, a packet data network or PSTN, or a combination thereof.
  • the RAN 10 is, for example, UTRAN, E-UTRAN, or a combination thereof.
  • the base station 2 corresponds to NodeB and RNC.
  • E-UTRAN the base station 2 corresponds to an eNB.
  • the base station 2 establishes a radio bearer 50 with the mobile terminal 1 and establishes a bearer 40 with the transfer node 4 for the user packet transfer of the mobile terminal 1.
  • the bearer 40 corresponds to the Iu bearer in UTRAN, and corresponds to the S1 bearer in E-UTRAN.
  • the combination of the bearer 40 and the radio bearer 50 corresponds to a radio access bearer (RAB).
  • RAB radio access bearer
  • the CN 20 is a network managed mainly by an operator who provides mobile communication services.
  • the CN 20 includes a Packet-Switched (PS) core.
  • PS Packet-Switched
  • the CN 20 is, for example, an EPC or GPRS packet core, or a combination thereof.
  • the CN 20 includes a mobility management node 3, a forwarding node 4, an external gateway 5, and a subscriber information database 6.
  • the CN 20 may include a communication management unit 7.
  • the mobility management node 3 is a control plane node that performs mobility management (e.g. location registration), bearer management (e.g. bearer establishment, bearer configuration change, bearer release) and the like of the mobile terminal 1.
  • the control unit 301 controls the core network 20 and the base station 2 at least for bearer management.
  • the mobility management node 3 includes an SGSN control plane function.
  • the mobility management node 3 includes an MME.
  • the mobility management node 3 transmits / receives a control message (e.g. S1AP message) to / from the base station 2 and transmits / receives a Non-Access Stratum (NAS) message to / from the mobile terminal 1.
  • NAS Non-Access Stratum
  • the NAS message is a control message that is not terminated at the RAN 10 and is transparently transmitted and received between the mobile terminal 1 and the CN 20 without depending on the radio access scheme of the RAN 10.
  • the NAS message sent from the mobile terminal 1 to the CN 20 includes NAS request messages such as an attach request, a bearer establishment request, a bearer recovery request, and a location update request.
  • NAS request messages from the mobile terminal 1 are Attach Request, Service Request, PDN connectivity request, Bearer Resource Allocation Request, Bearer Resource Modification Request, TAU (Tracking Area Update) Request, and RAU (Routing Area Update ) Including Request.
  • the attach request (Attach Request) in EPS causes not only connection of the mobile terminal 1 to the CN 20 but also establishment of a default bearer. Therefore, it can be said that an attach request (Attach Request) in EPS includes a bearer establishment request.
  • the forwarding node 4 forwards the user packet of the mobile terminal 1 between the RAN 10 (specifically, the base station 2) and the external gateway 5.
  • the transfer node 4 establishes a bearer with the base station 2 and establishes a core network bearer (CNB) 30 with the external gateway 5 for the user packet transfer of the mobile terminal 1.
  • the control unit 401 exchanges control messages with the mobility management node 3 and the external gateway 5, and performs bearer setting with the base station 2 and CNB 30 setting.
  • the forwarding node 4 (control unit 401) may issue a user plane address (e.g. IP address) to be assigned to the mobile terminal 1.
  • the forwarding node 4 includes a user plane function of SGSN.
  • the forwarding node 4 includes S-GW.
  • the CNB 30 corresponds to, for example, a CNB in UMTS or an S5 / S8 bearer in EPS.
  • the CNB 30 in the present embodiment is shared for user packet transfer of a plurality of mobile terminals 1.
  • the CNB 30 is referred to as a “shared CNB” in order to distinguish it from a normal CNB that is set in units of mobile terminals (or used only for one mobile terminal).
  • the plurality of mobile terminals 1 sharing the shared CNB 30 may be referred to as “mobile terminal group”.
  • the shared CNB 30 may be shared among a plurality of mobile terminals 1 connected to one base station 2 or may be shared between a plurality of mobile terminals 1 connected to a plurality of base stations 2. .
  • the external gateway 5 transfers the user packet of the mobile terminal 1 between the transfer node 4 and the external network 9.
  • the external gateway 5 establishes a shared CNB 30 with the forwarding node 4.
  • the control unit 501 exchanges control messages with the forwarding node 4 and sets the shared CNB 30.
  • the external gateway 5 (the control unit 501) may issue a user plane address (e.g. IP address) to be given to the mobile terminal 1.
  • the external gateway 5 includes a GGSN.
  • the external gateway 5 includes a P-GW.
  • the subscriber information database 6 is a database that holds subscriber information of the mobile terminal 1, and corresponds to Home Subscriber Server (HSS) or Home Location Server (HLR), for example.
  • the subscriber information database 6 has a function of providing subscriber information to the mobility management node 3 or the like.
  • the subscriber information database 6 can also be called a subscriber server.
  • the management unit 601 transmits subscriber information to the mobility management node 3 in response to a request from the mobility management node 3.
  • the subscriber information database 6 (management unit 601) may issue a user plane address (e.g. IP address) to be assigned to the mobile terminal 1.
  • a user plane address e.g. IP address
  • Reference Examples 1 to 5 including the CNB shared architecture and method devised by the present inventors as the premise of the present embodiment will be described with reference to FIGS.
  • Reference examples 1 and 2 are described in Japanese Patent Application No. 2011-217383 in the past of the present inventors.
  • Reference Examples 3 to 5 are described in Japanese Patent Application No. 2012-2114050 of the present inventors.
  • Reference Examples 1 to 5 are not known at the time of filing the application, but are technical ideas owned by the inventor.
  • Reference Example 1 the CN 20 sets between the forwarding node 4 and the external gateway 5 a shared CNB 30 that is shared for user packet forwarding of a plurality of mobile terminals 1 connected to one or a plurality of base stations 2.
  • the plurality of mobile terminals 1 can communicate simultaneously using the shared CNB 30. Therefore, in Reference Example 1, the forwarding node 4 censors the destination of the downlink user packet obtained from the shared CNB 30 and downlinks to the radio access bearer (RAB) corresponding to the mobile terminal 1 designated as the destination. Transfer user packets. That is, the forwarding node 4 associates one shared CNB 30 with a plurality of RABs.
  • RAB radio access bearer
  • the external gateway 5 issues a user plane address band to a plurality of mobile terminals 1 (that is, a terminal group) sharing one shared CNB 40, and transfers the authority to issue a user plane address to each mobile terminal 1. Transfer to node 4.
  • the forwarding node 4 pays out the user plane address to each mobile terminal 1 from the user plane address band designated by the external gateway 5.
  • the user plane address depends on the user plane protocol, but is typically an IP address.
  • the user plane address is an IP address will be described as an example.
  • the forwarding node 4 has an upper limit number of mobile terminals 1 (including mobile terminals 1 in an idle state) associated with one shared CNB 30 in order to guarantee a Quality of service (QoS) such as guaranteed bit rate (GBR). Or you may set the upper limit number of the mobile terminals 1 which communicate simultaneously in one common CNB30, or both. When any of these upper limit numbers is exceeded, the forwarding node 4 may additionally set a new shared CNB 30 or may reject bearer establishment or bearer recovery.
  • QoS Quality of service
  • GLR guaranteed bit rate
  • FIG. 2 shows an example of the bearer management table of the external gateway 5 in Reference Example 1.
  • the information for identifying the shared CNB 30 (that is, the IP address of the forwarding node 4 and the CNB identifier) is not the IP address paid to the mobile terminal 1, but the IP address paid to the mobile terminal group.
  • the IP address bands of the two mobile terminal groups shown in FIG. 2 are represented by IPv6 addresses, and indicate subnet numbers having a prefix length of 60 bits. For example, all of the user packets of the plurality of mobile terminals 1 to which the IPv6 address included in the address band indicated by the subnet number “2001: DB8: 1 :: / 60” is assigned are all IPv4 addresses “10.0. 0.1 "and the CNB identifier" 00001 "are transferred to the shared CNB 30.
  • FIG. 3 shows an example of the bearer management table of the forwarding node 4 in Reference Example 1.
  • the bearer management table of the forwarding node 4 is used for associating the CNB with the RAB, and further used for associating the IP address of each mobile terminal 1 with the RAB.
  • the IPv6 addresses “2001: DB8: 1: 1: / 64”, “2001: DB8: 1: 2: / 64”, and “2001: DB8: 1: 3: / 64” of the three mobile terminals 1 are And the same shared CNB 30 specified by the IPv4 address “10.1.0.1” of the external gateway 5 and the CNB identifier “00001”.
  • the IPv6 addresses “2001: DB8: 1: 1: / 64”, “2001: DB8: 1: 2: / 64”, and “2001: DB8: 1: 3: / 64” of the three mobile terminals 1 are associated with different RABs.
  • the forwarding node 4 uses the IPv4 address “10.0.1.1” and the RAB identifier “00001” of the base station 2 for the downlink user packet whose destination is “2001: DB8: 1: 1: / 64”. Forward to identified bearer 40.
  • the term “data bearer” in this specification means a communication path set between the external gateway 5 and the mobile terminal 1 for user data transfer.
  • the data bearer is, for example, a UMTS bearer or an EPS bearer.
  • “establishment” of the data bearer means that the correct bearer context is not held in any node of the RAN 10 and the CN 20, and the data bearer is set first.
  • “recovery” of the data bearer means reconfiguration of the data bearer set in the past, particularly reconfiguration of the RAB.
  • Mobile communication systems such as UMTS and EPS have a preservation function, and release RAB according to the transition of the mobile terminal 1 to the IDLE state (for example, ECM-IDLE).
  • the nodes that is, the mobility management node 3, the forwarding node 4, and the external gateway 5) maintain the data bearer context. Therefore, in the recovery of the data bearer, the RAB is reconfigured based on the bearer context maintained by the preservation function.
  • step S101 the mobile terminal 1 transmits a bearer establishment request.
  • step S102 the base station 2 transfers the bearer establishment request received from the mobile terminal 1 to the mobility management node 3.
  • the bearer establishment request is, for example, Attach Request in EPS or Activate PDP Context Request in UMTS.
  • step S103 the mobility management node 3 activates the authentication process of the mobile terminal 1 in response to receiving the bearer establishment request.
  • the authentication process includes access to the subscriber information database 6.
  • the mobility management node 3 transmits the identifier (e.g. International Mobile Subscriber Identity (IMSI)) of the transmission source terminal of the bearer establishment request to the database 6 and receives the subscriber information of the mobile terminal 1 from the database 6.
  • the subscriber information includes terminal group information.
  • the terminal group information indicates that the terminal belongs to a mobile terminal group that has a bearer establishment request transmission source terminal.
  • the terminal group information includes, for example, the identifier of the mobile terminal group to which the mobile terminal 1 belongs, the number of group accommodation terminals (the number of necessary IP addresses or the necessary IP address bandwidth), the maximum number of simultaneous use of the shared CNB, and the like.
  • the mobility management node 3 determines whether or not the data bearer sharing of the mobile terminal 1 is necessary based on the terminal group information. When bearer sharing is performed, the mobility management node 3 transmits a bearer establishment request indicating that bearer sharing is necessary to the transfer node 4 (step S104).
  • the mobility management node 3 may include bearer sharing information in a normal bearer establishment request, for example.
  • the normal bearer establishment request sent to the forwarding node 4 is, for example, Create Session Request in EPS or Create PDP Context Request in UMTS.
  • Bearer shared information indicates that a shared bearer needs to be established.
  • the forwarding node 4 and the external gateway 5 can recognize that the shared CNB needs to be set by including the bearer sharing information in the bearer establishment request.
  • the bearer shared information may indicate information necessary for determining the number of IP addresses necessary for the terminal group, for example.
  • the bearer sharing information may be a mobile terminal group identifier and the number of group accommodating terminals (required IP address number or necessary IP address bandwidth).
  • step S105 in response to receiving the bearer establishment request from the mobility management node 3, the forwarding node 4 generates an entry related to a new data bearer in the bearer management table, and generates a bearer establishment request (including bearer sharing information). Transmit to the external gateway 5.
  • step S106 the external gateway 5 pays out an address band satisfying the necessary number of IP addresses for the mobile terminal group in response to the reception of the bearer establishment request including the bearer sharing information. Further, the external gateway 5 sets the QoS corresponding to the mobile terminal group in the shared CNB 30 as necessary.
  • the external gateway 5 generates an entry related to the new shared CNB 30 in the bearer management table based on the tunnel endpoint identifier on the transfer node 4 side received from the transfer node 4 and the IP address bandwidth assigned to the mobile terminal group. Thereafter, in step S107, the external gateway 5 transmits a bearer establishment response to the forwarding node 4.
  • This bearer establishment response includes the IP address band and the tunnel endpoint identifier on the external gateway 5 side. Further, the bearer establishment response may include additional information such as data bearer QoS.
  • the bearer establishment response is, for example, Create Session Response in EPS or Create PDP Context Response in UMTS.
  • step S108 the forwarding node 4 determines an IP address to be assigned to the mobile terminal 1 from the IP address band indicated by the bearer establishment response from the external gateway 5. Further, in step S108, the forwarding node 4 updates the information of the shared CNB 30 in the bearer management table in response to receiving the bearer establishment response from the external gateway 5.
  • step S109 the forwarding node 4 transmits a bearer establishment response to the mobility management node 3.
  • This bearer establishment response includes a tunnel endpoint identifier on the forwarding node 4 side of the RAB (including bearer 40) associated with the shared CNB 30 in the forwarding node 4. Further, the bearer establishment response indicates the IP address assigned to the mobile terminal 1.
  • the bearer establishment response in step S109 corresponds to an internal message in the SGSN.
  • step S110 the mobility management node 3 receives the bearer establishment response from the forwarding node 4, and updates the bearer context related to the mobile terminal 1. Furthermore, in step S110, the mobility management node 3 transmits a control message including a bearer establishment response to the base station 2.
  • the bearer establishment response in step S110 is information notified to the mobile terminal 1, and includes an IP address assigned to the mobile terminal 1, a data bearer identifier, and the like. Further, the control message including the bearer establishment response in step S110 includes the tunnel endpoint identifier on the forwarding node 4 side of the bearer 40, the data bearer QoS, and the like.
  • the bearer establishment response in step S110 is, for example, Attach Accept in EPS or Activate PDP Context Accept in UMTS. Further, the control message including the bearer establishment response is, for example, an S1-AP message (specifically, Initial Context Setup Request) in EPS.
  • the base station 2 transfers a bearer establishment response to the mobile terminal 1 and executes a process of establishing a radio link (that is, the radio bearer 50) for the mobile terminal 1.
  • the base station 2 transmits a bearer establishment completion notification to the mobility management node 3.
  • the bearer establishment completion notification indicates completion of bearer setting in the base station 2 and completion of bearer setting in the mobile terminal 1.
  • the bearer establishment completion notification may be transmitted in two messages.
  • the bearer establishment completion notification may be Initial Context Response and Attach Complete in EPS.
  • the mobility management node 3 transmits a bearer update request to the transfer node 4 in response to receiving the bearer establishment completion notification.
  • the bearer update request includes a tunnel endpoint identifier on the base station 2 side of the bearer 40.
  • the forwarding node 4 updates the bearer management table based on the bearer update request.
  • the bearer update request is, for example, Modify Bearer Request in EPS.
  • the bearer update request in step S114 corresponds to an internal message in the SGSN.
  • the forwarding node 4 transmits a bearer update response to the mobility management node 3.
  • the bearer update response is, for example, Modify Bearer Response in EPS or Update PDP Context Response in UMTS.
  • 5A and 5B are sequence diagrams illustrating an example of a processing procedure of a bearer establishment request from the second and subsequent mobile terminals 1.
  • the processing in steps S201 to S204 is the same as the processing in steps S101 to S104 in FIG. 4A.
  • step S205 the forwarding node 4 recognizes that the shared CNB 30 has been established based on bearer shared information (for example, an identifier of the mobile terminal group) included in the bearer establishment request from the mobility management node 3, An IP address to be assigned to the second and subsequent mobile terminals 1 is determined from the IP address band that has been paid out from the external gateway 5.
  • the processing in steps S206 to S212 is the same as the processing in steps S109 to S115 in FIGS. 4A and 4B.
  • the forwarding node 4 may check the number of group accommodation terminals. When the number of mobile terminals 1 aggregated in one shared CNB 30 exceeds the upper limit number, for example, the forwarding node 4 performs a new shared according to the shared CNB establishment procedure for the first mobile terminal 1 shown in FIGS. 4A and 4B. The CNB 30 may be established. Alternatively, the forwarding node 4 may establish a normal CNB that is not a shared CNB. Further, even when the upper limit number of mobile terminals 1 communicating simultaneously in one shared CNB 30 is exceeded, the forwarding node 4 may establish a new aggregated bearer or a normal CMB, The bearer establishment may be refused.
  • step S301 in FIG. 6 the mobile terminal 1 transmits a bearer recovery request.
  • step S ⁇ b> 302 the base station 2 transfers the bearer restoration request received from the mobile terminal 1 to the mobility management node 3.
  • the bearer recovery request is, for example, a Service request in EPS or a Service request in UMTS.
  • RAB (bearer 40 and radio bearer 50) is established. That is, the mobility management node 3 transmits a RAB establishment request to the base station 2 (step S303).
  • the RAB establishment request is, for example, S1-AP Initial Context Setup Request in EPS or Radio Access Bearer Assignment Request in UMTS.
  • the base station 2 establishes a radio link (radio bearer 50) with the mobile terminal 1.
  • the base station 2 transmits to the mobility management node 3 a RAB establishment completion notification indicating completion of setting of the RAB (bearer 40 and radio bearer 50).
  • the RAB establishment completion notification is, for example, S1-AP Initial Context Setup Complete in EPS or RadioRadAccess Bearer Assignment Response in UMTS.
  • step S306 the mobility management node 3 transmits a bearer update request to the transfer node 4 in response to receiving the bearer establishment completion notification.
  • the bearer update request includes a tunnel endpoint identifier on the base station 2 side of the bearer 40.
  • step S307 the forwarding node 4 checks whether the number of mobile terminals 1 that are simultaneously communicating in the shared CNB 30 does not exceed the upper limit number.
  • the forwarding node 4 updates the bearer management table based on the bearer update request and transmits a bearer update response to the mobile management node 3 (step S308). ).
  • a negative response indicating rejection of bearer recovery may be transmitted to the mobility management node 3.
  • the mobility management node 3 or the base station 2 may transmit a back-off notification to the mobile terminal 1.
  • the back-off notification includes, for example, a back-off timer value.
  • the mobile terminal 1 may wait for transmission of the next attach request, bearer establishment request, or bearer recovery request during the back-off timer value or the randomly determined back-off time.
  • the architecture and method according to Reference Example 1 share the shared CNB 30 for user packet transfer related to a plurality of mobile terminals 1.
  • the end point setting of the shared CNB 30 is commonly used for user packet transfer of a plurality of mobile terminals 1.
  • the number of bearer contexts to be managed by the external gateway 5 is particularly small. That is, the external gateway 5 only needs to maintain a context regarding one shared CNB 30 for the plurality of mobile terminals 1. Therefore, the architecture and method according to Reference Example 1 can reduce the processing load required for bearer maintenance, particularly in the external gateway 5.
  • the CN 20 associates the shared CNB 30 with the RAB (specifically, the bearer 40) in the transfer node 4 on a one-to-one basis.
  • the CN 20 uses the shared CNB 30 and the bearer 40 for the arbitrary one. That is, in Reference Example 2, the number of mobile terminals that can simultaneously communicate in the shared CNB 30 is limited to one.
  • the mobility management node 3 makes a bearer establishment request (eg Attach Request) and a bearer restoration request (eg Service Request) from a plurality of mobile terminals 1 so that the plurality of mobile terminals 1 do not use the shared CNB 30 at the same time.
  • the external gateway 5 appropriately sets a packet filter (eg traffic flow template (TFT)) of the shared CNB 30 so that user data regarding a plurality of mobile terminals 1 does not flow into the shared CNB 30.
  • TFT traffic flow template
  • the shared CNB 30 can be used for transferring user packets of a plurality of mobile terminals 1 without the forwarding node 4 performing a special operation.
  • the forwarding node 4 has only to manage the correspondence relationship between one shared CNB 30 and one bearer 40 for transferring user packets of a plurality of mobile terminals 1, and users per mobile terminal 1 There is no need to distribute packets. Therefore, the capacity of the bearer management table to be managed by the forwarding node 4 can be reduced, and the processing amount of the forwarding node 4 can be reduced. Further, similarly to the reference example 1, the number of CNBs handled by the external gateway 5 is also reduced, so that the capacity of the bearer management table to be managed by the external gateway 5 can be reduced.
  • FIG. 7 shows an example of the bearer management table of the external gateway 5 in the reference example 2.
  • the bearer management table of FIG. 7 is the same as the bearer management table of Reference Example 1 shown in FIG.
  • FIG. 8 shows an example of the bearer management table of the forwarding node 4 in Reference Example 2.
  • the bearer management table of the forwarding node 4 is used for associating the CNB and the RAB.
  • the shared CNB 30 specified by the IPv4 address “10.1.0.1” and the CNB identifier “00001” of the external gateway 5 is the bearer 40 specified by the IPv4 address “10.0.1.1” and the RAB identifier “00001” of the base station 2. Is associated.
  • the bearer management table of FIG. 8 is the same as the general management table possessed by the forwarding node 4 (e.g. SGSN, S-GW).
  • FIGS. 9A and 9B show a data bearer including a shared CNB 30 in response to a request from one of the mobile terminals 1 (first mobile terminal) belonging to the mobile terminal group when the shared CNB 30 is not set. Shows the procedure to establish.
  • the processing in steps S401 to S407 is the same as the processing in steps S101 to S107 shown in FIG. 4A.
  • step S408 in response to receiving the bearer establishment response from the external gateway 5, the forwarding node 4 updates the information on the shared CNB 30 in the bearer management table and transmits the bearer establishment response to the mobility management node 3.
  • This bearer establishment response includes a tunnel endpoint identifier on the forwarding node 4 side of the RAB (including bearer 40) associated with the shared CNB 30 in the forwarding node 4. Further, the bearer establishment response indicates the IP address band assigned to the terminal group.
  • the bearer establishment response in step S408 corresponds to an internal message in the SGSN.
  • step S409 the mobility management node 3 receives a bearer establishment response from the forwarding node 4. Then, the mobility management node 3 determines one IP address to be allocated to the mobile terminal 1 from the IP address band assigned to the mobile terminal group by the external gateway 5.
  • step S410 the mobility management node 3 transmits a bearer update request to the transfer node 4 in response to receiving the bearer establishment completion notification.
  • the bearer update request includes a tunnel endpoint identifier on the base station 2 side of the bearer 40.
  • the forwarding node 4 updates the bearer management table based on the bearer update request.
  • the bearer update request is, for example, Modify Bearer Request in EPS.
  • the bearer update request in step S114 corresponds to an internal message in the SGSN.
  • step S414 the forwarding node 4 transmits a bearer update request to the external gateway 5 in order to update the packet filter of the external gateway 5.
  • This bearer update request requests the external gateway 5 to set in the shared CNB 30 a packet filter that discards user packets destined for addresses other than the IP address assigned to the mobile terminal 1 by the mobility management node 3. To do.
  • the bearer update request sent from the forwarding node 4 to the external gateway 5 is, for example, Modify Bearer Request in EPS or Update PDP Context Request in UMTS.
  • step S415 the external gateway 5 updates the packet filter applied to the shared CNB 30.
  • the external gateway 5 transfers the user packet related to only one of the plurality of mobile terminals 1 belonging to the mobile terminal group that actually communicates by the shared CNB 30.
  • step S416 the external gateway 5 transmits a bearer update response to the forwarding node 4, and the forwarding node 4 transmits a bearer update response to the mobility management node 3.
  • the bearer update response is, for example, Modify Bearer Response in EPS or Update PDP Context Response in UMTS.
  • FIG. 10A and 10B and FIG. 11 are sequence diagrams illustrating an example of a processing procedure of a bearer establishment request from the second and subsequent mobile terminals 1.
  • 10A and 10B show a processing procedure when there is no mobile terminal 1 in communication in the shared CNB 30.
  • FIG. 11 shows a processing procedure when there is a mobile terminal 1 in communication in the shared CNB 30.
  • step S504 the mobility management node 3 determines whether the data bearer sharing of the mobile terminal 1 is necessary based on the terminal group information. Then, the mobility management node 3 confirms whether there is a mobile terminal 1 that is currently in communication with respect to the mobile terminal group to which the mobile terminal 1 that has transmitted the bearer establishment request belongs. This confirmation may be performed based on the bearer context held by the mobility management node 3. Further, this confirmation may be performed by inquiring the communication management unit 7. In the example of FIG.
  • the mobility management node 3 determines that there is no mobile terminal 1 that is currently in communication, and the mobility management node 3 has a pooled IP with respect to the second and subsequent mobile terminals 1. An IP address is assigned from the address band.
  • the processing in steps S506 to S512 is the same as the processing in steps S410 to S416 shown in FIG. 9B.
  • step S604 in FIG. 11 the mobility management node 3 determines that there is a mobile terminal 1 currently in communication with respect to the mobile terminal group to which the mobile terminal 1 that has transmitted the bearer establishment request belongs.
  • the mobility management node 3 transmits a bearer establishment rejection response to the mobile terminal 1 via the base station 2 (steps S606 and S607).
  • the bearer establishment rejection response includes the IP address assigned to the mobile terminal 1. Therefore, the mobile terminal 1 that has received the bearer establishment rejection response may transition to the IDLE state in which the RAB is released but registered in the CN 20 instead of returning to the detached state. Further, the mobility management node 3 may include a back-off notification requesting the mobile terminal 1 to back off transmission of the next bearer establishment request (or bearer recovery request) in the bearer establishment rejection response.
  • the back-off notification includes, for example, a back-off timer value. In this case, the mobile terminal 1 may wait for transmission of the next bearer establishment request (or bearer recovery request) during the back-off timer value or during the randomly determined back-off time.
  • FIG. 12 shows a processing procedure when there is no mobile terminal 1 in communication in the shared CNB 30.
  • FIG. 13 shows a processing procedure when there is a mobile terminal 1 in communication in the shared CNB 30.
  • the mobile terminal 1 transmits a bearer recovery request.
  • the base station 2 transfers the bearer recovery request received from the mobile terminal 1 to the mobility management node 3.
  • the bearer recovery request is, for example, a Service request in EPS or a Service request in UMTS.
  • step S703 the mobility management node 3 determines whether or not the mobile terminal 1 belonging to the same mobile terminal group as the transmission source of the bearer restoration request and connected to the same base station 2 is communicating, that is, already shared. It is confirmed whether the CNB 30 and the bearer 40 are in use. This confirmation may be performed by making an inquiry to the communication management unit 7 as shown in step S704.
  • step S703 If it is determined in step S703 that there is no mobile terminal 1 currently communicating, the mobility management node 3 executes a procedure for establishing RAB (bearer 40 and radio bearer 50) (steps S705 to S707). That is, the mobility management node 3 transmits a RAB establishment request to the base station 2 (step S705).
  • the RAB establishment request is, for example, S1-AP Initial Context Setup Request in EPS or Radio Access Bearer Assignment Request in UMTS.
  • step S706 the base station 2 establishes a radio link (radio bearer 50) with the mobile terminal 1.
  • step S707 the base station 2 transmits to the mobility management node 3 a RAB establishment completion notification indicating completion of setting of the RAB (bearer 40 and radio bearer 50).
  • the RAB establishment completion notification is, for example, S1-AP Initial Context Setup Complete in EPS or RadioRadAccess Bearer Assignment Response in UMTS.
  • steps S708 to S710 is the same as steps S414 to S416 in FIG. 9B or steps S510 to S512 in FIG. 10B. That is, in steps S708 to S710, the forwarding node 4 updates the endpoint identifier on the base station side of the bearer 40. In step S ⁇ b> 709, the external gateway 5 updates the packet filter (e.g. ⁇ ⁇ TFT) so that packets addressed to other mobile terminals 1 other than the mobile terminal 1 that transits during communication do not flow through the shared CNB 30.
  • the packet filter e.g. ⁇ ⁇ TFT
  • step S803 in FIG. 13 it is determined that there is a mobile terminal 1 currently in communication.
  • a plurality of terminals 1 in the same mobile terminal group connected to the same base station 2 cannot perform simultaneous communication.
  • the mobility management node 3 transmits a bearer recovery rejection response to the mobile terminal 1 via the base station 2 (steps S805 and S806).
  • the bearer recovery rejection response is, for example, Service ⁇ ⁇ ⁇ Reject in EPS or service reject in UMTS.
  • the mobility management node 3 may include a notification for back-off transmission of the next bearer recovery request of the mobile terminal 1 in the bearer recovery rejection response.
  • the mobile terminal 1 suppresses transmission of the next bearer recovery request during a predetermined or randomly determined backoff time.
  • the architecture and method according to the reference example 2 share the shared CNB 30 for user packet transfer related to a plurality of mobile terminals 1. Furthermore, not only the end point setting of the shared CNB 30 but also the end point setting of the bearer 40 managed by the transfer node 4 is commonly used for user packet transfer of a plurality of mobile terminals 1. For this reason, the number of bearer contexts to be managed by the forwarding node 4 and the external gateway 5 is small. That is, typically, the forwarding node 4 and the external gateway 5 may maintain a context regarding one shared CNB 30 for a plurality of mobile terminals 1. Therefore, the architecture and method according to Reference Example 2 can reduce the processing load required for bearer maintenance in the forwarding node 4 and the external gateway 5.
  • the CNB shared architecture and method according to Reference Example 2 cannot allow multiple mobile terminals 1 in the same mobile terminal group connected to the same base station 2 to perform simultaneous communication.
  • the mobility management node 3 establishes bearers from a plurality of mobile terminals 1 so as not to allocate a shared CNB 30 to a plurality of mobile terminals 1 in the same mobile terminal group connected to the same base station 2 at the same time.
  • the fact that simultaneous communication cannot be performed means that (a) the communication frequency of a plurality of mobile terminals 1 belonging to the mobile terminal group is low, (b) the communication time of the mobile terminal 1 is short, or (c) the mobile terminal 1 communicates.
  • delay it is allowed, it is not considered to be a problem. Therefore, it is considered that the architecture and method according to Reference Example 2 have a remarkable effect in application to applications having such communication characteristics, for example, some Machine ⁇ TypeMCommunication (MTC) applications.
  • MTC Machine ⁇ TypeMCommunication
  • Reference examples 3 to 5 described below show improvements for suppressing the occurrence of call loss in an architecture that uses a shared CNB 30 for user packet transfer of a plurality of mobile terminals 1.
  • FIG. 14 is a diagram illustrating a network and bearer configuration during simultaneous communication according to Reference Example 3.
  • the operation of the mobile communication system according to Reference Example 3 is the same as that of Reference Example 2. That is, the mobile communication system according to Reference Example 3 can perform data packet transfer using only the shared CNB 30 as long as communication timings of two or more mobile terminals 1 do not overlap.
  • the mobile communication system according to Reference Example 3 can perform data packet transfer using only the shared CNB 30 as long as communication timings of two or more mobile terminals 1 do not overlap.
  • the endpoint setting of the shared CNB 30 managed by the external gateway 5 and the forwarding node 4 not only the endpoint setting of the bearer 40 managed by the forwarding node 4 Commonly used for. For this reason, the number of bearer contexts to be managed by the forwarding node 4 and the external gateway 5 is small, and the processing load required for bearer maintenance is reduced.
  • the CN 20 according to Reference Example 3 adds an additional data bearer (ie additional CNB 31, additional bearer 41, and additional) for each of the second and subsequent mobile terminals 1.
  • the additional data bearer may be a normal data bearer that does not use the shared CNB 30. That is, when the communication timings of two or more mobile terminals 1 in the same mobile terminal group coincide with each other, the mobile communication system according to Reference Example 3 temporarily generates a normal data bearer to cope with it. To do. Thereby, since the mobile communication system according to Reference Example 3 can enable simultaneous communication of a plurality of mobile terminals 1 belonging to the same mobile terminal group, occurrence of call loss can be suppressed.
  • the CN 20 according to the reference example 3 releases the setting in the CN 20 regarding the additional data bearer (additional CNB31, additional bearer 41, and additional radio bearer 51) according to the end of communication of each of the second and subsequent mobile terminals 1. Good. More specifically, in the normal preservation function, the bearer context is maintained in the CN 20, whereas in the CN 20 according to the reference example 3, each of the second and subsequent mobile terminals 1 terminates the communication and transmits the IDLE. At the time of transition to the state, the setting in the CN 20 regarding the additional data bearer may be released. In the next communication of the mobile terminal 1 that has transitioned to the IDLE state, if the shared CNB 30 is unused, the shared CNB 30 is used.
  • FIG. 15 is a flowchart illustrating an operation example of the mobility management node 3 according to the reference example 3.
  • the mobility management node 3 receives a bearer establishment request or a bearer recovery request from the mobile terminals 1 belonging to the terminal group for which the shared CNB 30 has been set.
  • the mobility management node 3 determines whether or not the mobile terminal (UE) 1 belonging to the same mobile terminal group as the transmission source terminal of the bearer recovery request and connected to the same base station 2 is communicating. Determine whether.
  • the mobility management node 3 determines that the shared CNB 30 that has been set is the same as in FIG. 10A, FIG. 10B, or FIG.
  • the mobile terminal 1, the base station 2, and the forwarding node 4 are controlled so as to generate an associated RAB and assign it to the mobile terminal 1 (step S13).
  • the mobility management node 3 executes a bearer establishment procedure to perform additional data bearers (CNB 31, bearer 41, and radio bearer 51). ) Is newly created, and the mobile terminal 1, the base station 2, the forwarding node 4, and the external gateway 5 are controlled so as to allocate this additional data bearer to the mobile terminal 1 (step S14).
  • FIG. 16 shows an example of the bearer management table of the external gateway 5 according to Reference Example 3.
  • the external gateway 5 sends a user packet addressed to the IP address assigned to the second mobile terminal 1 to the additional CNB 31 (and bearer management table). Modify packet filter based on management table. That is, the external gateway 5 adds an entry related to the added CNB 31 to the bearer management table.
  • the management table of FIG. 16 includes a third entry relating to the additional CNB 31. In the third entry of FIG.
  • the IPv6 address “2001: DB8: 3: 1 :: / 64” is the additional CNB 31 specified by the IPv4 address “10.0.0.1” of the forwarding node 4 and the CNB identifier “00003”. It is associated.
  • the IPv6 address “2001: DB8: 1: 1 :: / 64” is not a subnet number as an address band but an IPv6 address assigned to one mobile terminal 1.
  • the external gateway 5 may determine the CNB that distributes user packets by performing longest matching using the management table of FIG. As a result, the external gateway 5 can distribute the user packet of the second mobile terminal 1 to which the IPv6 address “2001: DB8: 1: 1 :: / 64” is assigned to the additional CNB 31 instead of the shared CNB 30.
  • FIG. 17 shows an example of the bearer management table of the forwarding node 4 according to Reference Example 3.
  • a third entry indicating the correspondence between the additional CNB 31 and the additional bearer 41 is added.
  • the additional bearer 41 is specified by the IP address “10.0.1.1” of the base station 2 and the RAB identifier “00002”.
  • FIG. 18A and FIG. 18B are sequence diagrams illustrating a processing example of a bearer establishment request from the second and subsequent mobile terminals 1 in the same mobile terminal group connected to the base station 2, and there is a mobile terminal 1 in communication This shows the processing procedure for doing this. If there is no mobile terminal 1 in communication, the bearer establishment request may be processed in the same procedure as the sequence according to the reference example shown in FIGS. 10A and 10B.
  • step S904 in FIG. 18A the mobility management node 3 determines that there is a mobile terminal 1 currently in communication with respect to the terminal group to which the mobile terminal 1 that has transmitted the bearer establishment request belongs. Thereafter, in the reference example 2 shown in FIG. 11, the mobility management node 3 rejects the bearer establishment. On the other hand, in the reference example 3 shown in FIG. 18A, the mobility management node 3 transmits a bearer establishment request to the transfer node 4 in order to generate an additional bearer (step S906).
  • the bearer establishment request in step S906 is a message for establishing a data bearer using a normal CNB instead of a shared CNB. Therefore, the bearer establishment request in step S906 includes the IP address issued by the mobility management node 3 to the mobile terminal 1, but does not include bearer sharing information.
  • step S907 in response to receiving the bearer establishment request, the forwarding node 4 adds an entry related to the new data bearer to the bearer management table, and sends the bearer establishment request (including the IP address of the mobile terminal 1) to the external gateway 5.
  • the external gateway 5 sets a normal CNB (that is, an additional CNB) for the IP address of the mobile terminal 1 specified in the bearer establishment request, and adds a new entry to the bearer management table. Then, the external gateway 5 transmits a bearer establishment response to the transfer node 4.
  • the subsequent processing in steps S909 to S915 may be the same as the normal data bearer establishment procedure, for example, the procedure described in Section 5.3.1 “Attach” procedure ”of Non-Patent Document 1.
  • step S1003 in FIG. 19 the mobility management node 3 confirms that another mobile terminal 1 that is connected to the same base station 2 as the mobile terminal 1 that has transmitted the bearer recovery request and belongs to the same mobile terminal group is communicating. judge. Thereafter, in Reference Example 2 shown in FIG. 13, the mobility management node 3 rejects bearer recovery. On the other hand, in Reference Example 3 shown in FIG.
  • the mobility management node 3 rejects bearer recovery and requests the mobile terminal 1 to detach (that is, disconnection from the CN 20) (steps S1004 and S1005).
  • the bearer recovery rejection message transmitted in steps S1004 and S1005 of FIG. 19 includes a detach request.
  • the mobility management node 3 sets an additional data bearer according to the sequence shown in FIGS. 18A and 18B in response to the reception of the attach request ( Step S1006).
  • the procedure in FIG. 19 is merely an example.
  • the CN 20 and the RAN 10 execute a procedure similar to the bearer establishment procedure or the bearer addition procedure instead of the bearer restoration procedure.
  • An additional data bearer may be established.
  • the CN 20 and the RAN 10 may perform the same processing as that of steps S906 to S915 in the bearer establishment procedure shown in FIGS. 18A and 18B after step S1003 of FIG.
  • “addition” of a data bearer means that an individual data bearer is additionally set in the same connection (e.g. Packet Data Network (PDN) connection) as an existing data bearer.
  • PDN Packet Data Network
  • the procedure for adding a data bearer to an existing connection is described, for example, in Section 5.4.5 “UE requested bearer resource modification” of Non-Patent Document 1.
  • the CN 20 and the RAN 10 may release the additional data bearer generated according to the procedure of FIG. 18A, FIG. 18B, or FIG. 19 in response to the end of the communication of the mobile terminal 1.
  • the mobility management node 3 transfers the base station 2 and the transfer so that not only the additional RAB (bearer 41 and radio bearer 51) but also the setting of the additional CNB 31 is deleted.
  • the node 4 and the external gateway 5 may be controlled.
  • Reference Example 4 In the reference example 3, one of the improved architecture and method capable of suppressing the occurrence of call loss when the shared CNB 30 is used for transferring user packets of a plurality of mobile terminals 1 has been described. Reference Example 4 describes another improved architecture and method.
  • FIG. 20 is a diagram showing a network and bearer configuration during simultaneous communication according to Reference Example 4.
  • the CN 20 sets a plurality of shared CNBs between the forwarding node 4 and the external gateway 5 for transferring user packets of a plurality of mobile terminals 1 in the same mobile terminal group connected to the base station 2.
  • the CN 20 associates each of the plurality of shared CNBs with the RAB on a one-to-one basis.
  • first and second shared CNBs 30 and 32 are set, and these are associated with the first RAB (bearer 40 and radio bearer 50) and the second RAB (bearer 42 and radio bearer 52), respectively. .
  • the CN 20 uses the first shared CNB 30 for one of the two arbitrary devices, and uses the second shared CNB 32 for the other. use.
  • the mobile communication system according to Reference Example 4 can enable simultaneous communication of a plurality of mobile terminals 1 belonging to the same mobile terminal group, occurrence of call loss can be suppressed.
  • the shared CNBs 30 and 32 are used for user packet transfer of a plurality of mobile terminals 1 as described in the reference example 2.
  • two mobile terminals 1 can communicate simultaneously using the shared CNBs 30 and 32.
  • the mobility management node 3 assigns shared CNBs 30 and 32 to the two mobile terminals 1, and while these two units are communicating,
  • the bearer establishment request and the bearer restoration request from the third and subsequent mobile terminals 1 are arbitrated so that the shared CNBs 30 and 32 are not allocated to the third and subsequent mobile terminals 1.
  • the mobile terminal 1 attached to the CN 20 maintains a bearer context regarding at least two data bearers.
  • the function in which the mobile terminal 1 maintains a plurality of data bearers is already known as a multiple PDN function in EPS, for example.
  • the mobile terminal 1 may maintain a plurality of PDN connections that pass through the same external gateway 5.
  • the plurality of PDN connections may be associated with the same Access Point Name (APN) or may be associated with different APNs.
  • APN Access Point Name
  • FIG. 21 is a sequence diagram illustrating an example of a bearer establishment procedure according to Reference Example 4.
  • the mobile terminal 1 transmits a first bearer establishment request.
  • the first bearer establishment request triggers the CN 20 to generate the first PDN connection.
  • the mobility management node 3 responds to the first bearer establishment request to establish a data bearer that uses the first shared CNB 30, so that the mobile terminal 1, the base station 2, the forwarding node 4, and the external gateway 5 is controlled.
  • the processing in step S1102 may be similar to the data bearer establishment procedure (FIGS. 9A and 9B) using the shared CNB according to the reference example 2.
  • the mobile terminal 1 transmits a second bearer establishment request.
  • the second bearer establishment request triggers the CN 20 to generate a second PDN connection.
  • the mobility management node 3 in response to the second bearer establishment request, the mobility management node 3 establishes a data bearer that uses the second shared CNB 32, and the mobile terminal 1, the base station 2, the forwarding node 4, and the external gateway 5 is controlled.
  • the first and second data bearers generated by the procedure of FIG. 21 may be associated with different APNs or may be associated with the same APN.
  • FIG. 21 shows an example in which the mobile terminal 1 generates a plurality of data bearers by explicitly transmitting two bearer establishment requests.
  • the CN 20 may activate a procedure for generating a plurality of data bearers in response to one bearer establishment request transmitted from the mobile terminal 1.
  • the mobility management node 3 may perform control to generate a plurality of PDN connections that pass through the same external gateway 5 in response to one bearer establishment request.
  • the sequence diagram of FIG. 22 shows an example of a procedure for generating first and second data bearers (first and second PDN connections) associated with different APNs in response to one bearer establishment request. .
  • the processes in steps S1201 and S1202 in FIG. 22 are the same as steps S401 and S402 shown in FIG. 9A or steps S501 and S502 shown in FIG. 10A.
  • the mobility management node 3 acquires the subscriber information regarding the mobile terminal 1 that is the transmission source of the bearer establishment request from the subscriber information database 6.
  • the subscriber information includes terminal group information and first and second APNs.
  • the mobility management node 3 generates each of the two PDN connections related to the first and second APNs by using the shared CNB by referring to the terminal group information and the first and second APNs. That is, in step S1204, the mobility management node 3 controls the mobile terminal 1, the base station 2, the forwarding node 4, and the external gateway 5 so as to establish a data bearer that uses the first shared CNB 30 with respect to the first APN. . In step S1205, the mobility management node 3 controls the mobile terminal 1, the base station 2, the forwarding node 4, and the external gateway 5 so as to establish a data bearer using the second shared CNB 32 with respect to the second APN.
  • the sequence diagram of FIG. 23 shows an example of a procedure for generating first and second data bearers (first and second PDN connections) associated with the same APN in response to one bearer establishment request. .
  • the processes in steps S1301 and S1302 in FIG. 23 are the same as steps S401 and S402 shown in FIG. 9A or steps S501 and S502 shown in FIG. 10A.
  • the mobility management node 3 acquires subscriber information related to the mobile terminal 1 from the subscriber information database 6.
  • the subscriber information includes first and second terminal group information. That is, the subscriber information indicates that the mobile terminal 1 belongs to a plurality of terminal groups.
  • the mobility management node 3 refers to the first and second terminal group information, and generates the first and second PDN connections associated with the first and second terminal groups, respectively, using the shared CNB. . That is, in step S1304, the mobility management node 3 controls the mobile terminal 1, the base station 2, the forwarding node 4, and the external gateway 5 so as to establish a data bearer using the first shared CNB 30 with respect to the first terminal group. To do. In step S 1305, the mobility management node 3 controls the mobile terminal 1, the base station 2, the forwarding node 4, and the external gateway 5 so as to establish a data bearer that uses the second shared CNB 32 for the second terminal group.
  • FIG. 24 shows an example of the bearer management table of the external gateway 5 according to Reference Example 4.
  • the external gateway 5 generates a plurality of shared CNBs 30 and 32 for one mobile terminal 1 in response to a request from the mobility management node 3 received via the forwarding node 4. That is, the external gateway 5 adds entries related to the two shared CNBs 30 and 32 to the bearer management table.
  • the management table of FIG. 24 includes a third entry relating to the second shared CNB 32. In the third entry of FIG.
  • the subnet number “2001: DB8: 3 :: / 60” as the IPv6 address band is specified by the IPv4 address “10.0.0.1” of the forwarding node 4 and the CNB identifier “00003”.
  • the second shared CNB 32 Corresponding to the second shared CNB 32.
  • FIG. 25 shows an example of the bearer management table of the forwarding node 4 according to Reference Example 4.
  • a third entry indicating the correspondence between the second shared CNB 32 and the bearer 42 is added.
  • the bearer 42 is specified by the IP address “10.0.1.1” of the base station 2 and the RAB identifier “00002”.
  • FIG. 26 is a flowchart showing an operation example when the mobile terminal 1 according to Reference Example 4 starts communication.
  • FIG. 26 illustrates an operation in which the mobile terminal 1 that is attached to the CN 20 and in the IDLE state transmits a service recovery request.
  • the mobile terminal 1 transmits a bearer recovery request regarding the first data bearer using the shared CNB 30.
  • step S22 when the recovery of the first data bearer is rejected (YES in step S22), the mobile terminal 1 transmits a bearer recovery request regarding the second data bearer using the shared CNB 32 (step S23).
  • step S22 it is determined whether the recovery request for the second data bearer has been rejected by the mobility management node 3.
  • the mobile terminal 1 performs communication using the second data bearer.
  • the recovery of the second data bearer is also rejected (YES in step S24)
  • the mobile terminal 1 may return to step S21 and repeat the process.
  • the mobility management node 3 may transmit a back-off notification requesting the mobile terminal 1 to back off transmission of the next bearer establishment request (or bearer recovery request) together with the bearer recovery rejection message.
  • Reference Example 5 describes still another architecture and method capable of suppressing the occurrence of a call loss when the shared CNB 30 is used for transferring user packets of a plurality of mobile terminals 1.
  • FIG. 27 is a diagram showing a network and bearer configuration during simultaneous communication according to Reference Example 5.
  • the operation of the mobile communication system according to Reference Example 5 is the same as that of Reference Example 2. That is, the mobile communication system according to Reference Example 5 performs data packet transfer using only the first RAB (bearer 40 and radio bearer 50) and the shared CNB 30 unless the communication timings of two or more mobile terminals 1 overlap. It can be carried out.
  • the mobile communication system according to Reference Example 5 performs data packet transfer using only the first RAB (bearer 40 and radio bearer 50) and the shared CNB 30 unless the communication timings of two or more mobile terminals 1 overlap. It can be carried out.
  • the endpoint setting of the shared CNB 30 managed by the external gateway 5 and the forwarding node 4 not only the endpoint setting of the bearer 40 managed by the forwarding node 4 Commonly used for. For this reason, the number of bearer contexts to be managed by the forwarding node 4 and the external gateway 5 is small, and the processing load required for bear
  • the CN 20 according to Reference Example 5 adds an additional second RAB (bearer 43 and radio bearer 53) for each of the second and subsequent mobile terminals 1.
  • the second RAB is associated with the shared CNB 30 in addition to the first RAB (bearer 40 and radio bearer 50). This association may be performed by updating the bearer correspondence table of the forwarding node 4.
  • the CN 20 according to Reference Example 5 uses the first RAB (bearer 40 and radio bearer 50) and the shared CNB 30 for the first mobile terminal 1, and uses the first RAB for the second mobile terminal 1. 2 RABs (bearer 43 and radio bearer 53) and shared CNB 30 are used.
  • the forwarding node 4 refers to the destination address of the user packet received via the shared CNB 30 and transfers the user packet addressed to the first mobile terminal 1 to the first RAB (that is, the bearer 40). Distribution of user packets addressed to the second mobile terminal 1 to the second RAB (that is, bearer 43). That is, when the communication timings of two or more mobile terminals 1 are accidentally overlapped, the mobile communication system according to Reference Example 5 temporarily generates an additional RAB, and the transfer node 4 performs the user packet unit. This sort process is executed. Thereby, the mobile communication system according to Reference Example 5 can suppress an increase in processing load required for bearer maintenance in the forwarding node 4 and the external gateway 5 while suppressing occurrence of call loss.
  • the architecture and method according to Reference Example 5 are such that when two or more mobile terminals 1 belonging to the same mobile terminal group perform simultaneous communication, setting change of the shared CNB 30, addition of CNB, and packet filter in the external gateway 5 No change of (TFT) is required. This is because the forwarding node 4 copes with simultaneous communication by adding a second RAB and sorting in units of user packets. Therefore, the architecture and method according to Reference Example 5 can suppress an increase in the CNB context to be managed by the external gateway 5 and reduce the processing load on the external gateway 5 when two or more mobile terminals 1 perform simultaneous communication. it can.
  • the CN 20 according to the reference example 5 sets the second RAB (bearer 43 and radio bearer 53) in the CN 20 according to the end of communication of the second and subsequent mobile terminals 1, for example, the mobility management node 3 and the forwarding node.
  • the bearer context held by 4 may be released. More specifically, in the normal reservation function, the bearer context is maintained in the CN 20, whereas in the CN 20 according to the reference example 5, each of the second and subsequent mobile terminals 1 terminates the communication and transmits the IDLE.
  • the setting in the CN 20 regarding the second RAB may be released.
  • the context regarding the shared CNB 30 is maintained in the CN 20.
  • the first RAB (bearer 40 and radio bearer 50) and the shared CNB 30 are used if there are no other terminals in communication.
  • FIG. 28 is a flowchart illustrating an operation example of the mobility management node according to the reference example 5.
  • the processing in steps S31 to S33 is the same as steps S11 to S13 related to the reference example 3 shown in FIG.
  • the mobility management node 3 executes a bearer establishment procedure to newly create a second RAB (bearer 43 and radio bearer 53), and assign this additional data bearer to the mobile terminal 1,
  • the base station 2, the transfer node 4, and the external gateway 5 are controlled (step S34).
  • FIG. 29 shows an example of the bearer management table of the external gateway 5 according to Reference Example 5.
  • the bearer management table of FIG. 29 is the same as the bearer management table according to Reference Example 2 shown in FIG.
  • the only additional bearer when two mobile terminals 1 communicate simultaneously is the second RAB (bearer 43 and radio bearer 53), and the addition of CNB is not necessary. Therefore, it is not necessary to update the bearer management table of the external gateway 5.
  • FIG. 30 shows an example of the bearer management table of the forwarding node 4 according to Reference Example 5.
  • a column indicating a terminal IP address or a terminal group IP address band is added to identify a user packet flow (also referred to as Service Data Flow (SDF)) flowing through the shared CNB 30.
  • SDF Service Data Flow
  • the user packet flow is specified by the terminal IP address (or terminal group IP address band), the IP address of the external gateway 5, and the CNB identifier.
  • a third entry indicating a correspondence relationship between the packet flow related to the second mobile terminal 1 and the second RAB (bearer 43 and radio bearer 53) is added.
  • IPv6 address “2001: DB8: 1: 1 :: / 64” of the second mobile terminal 1 the IPv4 address “10.0.0.1” of the external gateway 5, and the CNB identifier “00001”.
  • the user packet flow is associated with the second RAB (bearer 42) specified by the IPv4 address “10.0.1.1” of the base station 2 and the RAB identifier “0002”.
  • the forwarding node 4 may determine the RAB to which the user packet is distributed by performing longest matching using the management table of FIG. As a result, the forwarding node 4 transmits the user packet of the second mobile terminal 1 assigned the IPv6 address “2001: DB8: 1: 1 :: / 64” to the first RAB (bearer 40 and radio bearer 50). Instead of the second RAB (bearer 43 and radio bearer 53).
  • FIGS. 31A and 31B illustrate an example in which a second RAB is generated in response to a bearer establishment request from the second and subsequent mobile terminals 1.
  • the processes in steps S1401 to S1405 in FIG. 31A are the same as steps S601 to S605 shown in FIG.
  • the mobility management node 3 determines that there is a mobile terminal 1 currently in communication with respect to the mobile terminal group to which the mobile terminal 1 that has transmitted the bearer establishment request belongs. Thereafter, in the reference example illustrated in FIG. 11, the mobility management node 3 rejects bearer establishment.
  • the mobility management node 3 transmits a bearer establishment request to the transfer node 4 in order to generate an additional second RAB (bearer 43 and radio bearer 53) (step S1406). ).
  • the bearer establishment request in step S1406 requests the transfer node 4 to additionally generate the bearer 43 and requests the transfer node 4 to manage the user packet flow related to the second mobile terminal and the bearer 43 in association with each other. Therefore, the bearer establishment request in step S1406 may include the IP address assigned to the second mobile terminal 1 and bearer sharing information.
  • the bearer shared information here may be, for example, an identifier of the shared CNB 30.
  • step S1407 in response to receiving the bearer establishment request, the forwarding node 4 adds an entry related to the second RAB (bearer 43 and radio bearer 53) to the bearer management table, and is transferred by the shared CNB 30.
  • the second RAB is associated with the packet flow of the mobile terminal 1.
  • the forwarding node 4 returns a bearer establishment response to the mobility management node 3.
  • the subsequent processing in steps S1408 to S1413 may be the same as the normal data bearer establishment procedure, for example, the procedure described in Section 5.3.1 “Attach” procedure ”of Non-Patent Document 1.
  • step S1503 of FIG. 32A the mobility management node 3 determines that another mobile terminal connected to the same base station 2 as the source mobile terminal 1 of the bearer recovery request and belonging to the same mobile terminal group is communicating. To do. Thereafter, in Reference Example 2 shown in FIG. 13, the mobility management node 3 rejects bearer recovery. On the other hand, in Reference Example 5 shown in FIGS.
  • the mobility management node 3 transmits a bearer establishment request to the transfer node 4 (step S1504).
  • the bearer establishment request in step S1504 plays the same role as the bearer establishment request in step S1406 of FIG. 31 described above.
  • the bearer establishment request in step S1504 may include the IP address assigned to the second mobile terminal 1 and bearer sharing information.
  • the bearer shared information here may be, for example, an identifier of the shared CNB 30.
  • step S1505 in response to the reception of the bearer establishment request, the forwarding node 4 adds an entry relating to the second RAB (bearer 43 and radio bearer 53) to the bearer management table, and is transferred by the shared CNB 30.
  • the second RAB is associated with the packet flow of the mobile terminal 1.
  • the forwarding node 4 returns a bearer establishment response to the mobility management node 3.
  • the subsequent processing in steps S1506 to S1510 may be the same as the normal bearer restoration procedure, for example, the procedure described in Section 5.3.4 “Service Request” procedure of Non-Patent Document 1.
  • Improvement A relates to Reference Examples 1 to 5 described above.
  • the configuration example of the mobile communication system according to the improvement A is the same as the configuration examples of the reference examples 1 to 5 shown in FIG. 1, FIG. 14, FIG. 20, and FIG.
  • the mobility management node 3 (control unit 301), as described in the reference examples 1 to 5, shares the shared CNB 30 that is shared for user packet transfer of the plurality of mobile terminals 1 belonging to the mobile terminal group. Manage.
  • the mobile communication system generally includes a plurality of forwarding nodes 4.
  • a bearer establishment request attach.request in e.g. EPS, Activate PDP Context Request in UMTS
  • the mobility management node 3 selects a forwarding node to establish a bearer.
  • the shared CNB 30 is already set in any of the transfer nodes 4, if the mobility management node 3 selects another transfer node 4, the use effect of the shared CNB 30 is reduced.
  • the mobility management node 3 (the control unit 301) according to the improvement A has the mobile terminal group while the shared CNB 30 is already set between the first forwarding node of the plurality of forwarding nodes 4 and the external gateway 5.
  • the operation is performed to select the first forwarding node for which the shared CNB has already been set for the first mobile terminal.
  • the mobility management node 3 After selecting the first forwarding node 4, the mobility management node 3 performs the bearer establishment procedure or the bearer modification procedure for the second and subsequent mobile terminals 1 in the same mobile terminal group described in Reference Examples 1 to 5 ( For example, FIGS. 5A and 5B or FIGS. 10A and 10B) may be executed.
  • the transfer node 4 for which the shared CNB 30 has been set is preferentially selected by the mobility management node 3. Therefore, the improvement A can contribute to the improvement of the use effect of the shared CNB 30.
  • FIG. 33 is a flowchart showing an example of the forwarding node selection operation of the mobility management node 3 according to the improvement A.
  • the mobility management node 3 receives a bearer establishment request from the mobile terminals 1 belonging to the mobile terminal group in which the shared CNB 30 has been set.
  • the mobility management node 3 selects the forwarding node 4 that terminates (sets) the set shared CNB 30.
  • the mobility management node 3 transmits a control message indicating a CNB establishment request or a shared CNB 30 modification request to the forwarding node 4 selected in step S42.
  • the selection of the forwarding node 4 by the mobility management node 3 may be performed using a domain name system (DNS).
  • DNS domain name system
  • a DNS entry that associates the IP address of the forwarding node 4 with a Fully Qualified Domain Name (FQDN) including a mobile terminal group identifier may be set.
  • the mobility management node 3 can select the same forwarding node 4 for one mobile terminal group by querying the DNS for the FQDN including the mobile terminal group identifier.
  • the improvement B relates to the reference examples 2 to 5 described above.
  • the configuration example of the mobile communication system according to the improvement B is the same as the configuration examples of the reference examples 2 to 5 shown in FIG. 1, FIG. 14, FIG. 20, and FIG.
  • the mobile communication system generally includes a plurality of mobility management nodes 3. Therefore, the improvement B provides an architecture and a method in which a plurality of mobile terminals 1 belonging to different mobility management nodes 3 can use one shared CNB 30.
  • the external gateway 5 issues a user plane address band to a mobile terminal group, and the mobility management node 3 assigns a user plane address (eg IP address) to each mobile terminal 1 Adopted architecture.
  • Reference examples 2 to 5 show architectures in which the mobility management node 3 manages the usage status of the shared CNB.
  • the IP address management of the mobile terminal group and the usage status management of the shared CNB 30 are arranged.
  • four examples ie, improved B-1, improved B-2, improved B-3, and improved B-4) related to IP address management and shared CNB 30 management arrangement will be described.
  • FIG. 34 is a configuration example showing an arrangement of IP address management and shared CNB 30 management according to the improved B-1.
  • a plurality of mobile terminals 1 belonging to one mobile terminal group are connected to the CN 20 via a plurality of base stations 2A and 2B.
  • the mobility management nodes 3A and 3B manage one shared CNB 30 related to one mobile terminal group.
  • the mobile management node 3A and 3B when the mobility management nodes 3A and 3B receive a bearer establishment request or a bearer recovery request from the mobile terminal 1, the mobile management node 3A and 3B allocates an IP address to the mobile terminal 1 and any mobile terminal 1 communicates in the shared CNB 30. It communicates with the subscriber information database 6 to inquire whether it is in the middle.
  • FIG. 35 is a configuration example showing an arrangement of IP address management and shared CNB 30 management according to the improvement B-2.
  • the mobility management nodes 3A and 3B receive the bearer establishment request from the mobile terminal 1, they communicate with the subscriber information database 6 in order to assign an IP address to the mobile terminal 1.
  • the mobility management nodes 3A and 3B receive a bearer establishment request or a bearer recovery request from the mobile terminal 1, the mobile management nodes 3A and 3B perform transfer to inquire about which mobile terminal 1 is communicating in the shared CNB 30. Communicate with node 4.
  • FIG. 36 is a configuration example showing an arrangement of IP address management and shared CNB 30 management according to the improvement B-3.
  • the mobility management nodes 3A and 3B receive the bearer establishment request from the mobile terminal 1, the mobility management nodes 3A and 3B communicate with the external gateway 5 via the forwarding node 4 to assign an IP address to the mobile terminal 1.
  • the mobility management nodes 3A and 3B receive a bearer establishment request or a bearer recovery request from the mobile terminal 1, the mobile management nodes 3A and 3B perform transfer to inquire about which mobile terminal 1 is communicating in the shared CNB 30. Communicate with node 4.
  • FIG. 37 is a configuration example showing an arrangement of IP address management and shared CNB 30 management according to the improvement B-2.
  • the mobility management nodes 3A and 3B receive the bearer establishment request from the mobile terminal 1, the mobility management nodes 3A and 3B communicate with the external gateway 5 via the forwarding node 4 to assign an IP address to the mobile terminal 1.
  • the mobility management nodes 3A and 3B receive a bearer establishment request or a bearer recovery request from the mobile terminal 1, the mobile management nodes 3A and 3B join in order to inquire about which mobile terminal 1 is communicating in the shared CNB 30. Communicate with the person information database 6.
  • one or a plurality of nodes that is, the subscriber information database 6, the plurality of mobility management nodes 3 that can be accessed together directly or indirectly through other nodes.
  • the mobility management node 3 duplicately assigns the IP address already allocated to the mobile terminal 1 belonging to the other mobility management node 3 (for example, the node 3B) to the mobile terminal 1 belonging to itself. Can avoid the problem.
  • the mobility management node 3 (for example, the node 3A) can avoid a problem that the mobile terminal 1 belonging to another mobility management node 3 (for example, the node 3B) cannot grasp whether the shared CNB 30 is communicating.
  • the improvement B-1 has an advantage that the setting and correction processing of the shared CNB 30 in the forwarding node 4 and the external gateway 5 can be performed with a simple procedure. Because the subscriber information database 6 manages the IP address management of the mobile terminal group and the usage status management of the shared CNB 30, the forwarding node 4 and the external gateway 5 do not need to perform these managements. This is because it is not necessary to send a signal for inquiring about the use status to the transfer node 4 or the external gateway 5.
  • the improved B-2 and the improved B-3 are for managing the shared CNB 30 as compared to the mode of managing the usage status of the shared CNB 30 in the subscriber information database 6 (improved B-1 and improved B-4).
  • the improved B-3 and the improved B-4 are different from those in which the IP address of the mobile terminal group is managed in the subscriber information database 6 (improved B-1 and improved B-2). Etc., that is, an architecture in which the external gateway 5 issues an IP address can be approached.
  • the sequence diagrams of FIGS. 38A and 38B relate to the improvement B-1 and establish a data bearer including the shared CNB 30 in response to a request from the first mobile terminal 1 in the mobile terminal group when the shared CNB 30 is not set.
  • the procedure to do is shown.
  • the mobile terminal 1 transmits a bearer establishment request.
  • the base station 2 transfers the bearer establishment request received from the mobile terminal 1 to the mobility management node 3.
  • the bearer establishment request is, for example, Attach Request in EPS or Activate PDP Context Request in UMTS.
  • the mobility management node 3 activates the authentication process of the mobile terminal 1 in response to receiving the bearer establishment request.
  • the authentication process includes access to the subscriber information database 6. That is, the mobility management node 3 transmits the identifier (e.g. International Mobile Subscriber Identity (IMSI)) of the transmission source terminal of the bearer establishment request to the database 6.
  • IMSI International Mobile Subscriber Identity
  • the subscriber information database 6 manages the IP address of the mobile terminal group. Therefore, the subscriber information database 6 determines that the terminal belongs to a specific mobile terminal group based on the identifier (eg IMSI) of the source terminal of the bearer establishment request, and sets the IP address bandwidth for the mobile terminal group. Paying out and paying out the IP address to the mobile terminal 1. Then, the subscriber information database 6 transmits the subscriber information to the mobility management node 3.
  • the subscriber information includes terminal group information, an IP address band, and the IP address of the mobile terminal 1.
  • the subscriber information database 6 does not have to pay out the IP address band in step S1603.
  • the subscriber information in step S1603 may not indicate the IP address band. That is, the subscriber information database 6 only needs to be able to notify the mobility management node 3 whether or not the shared CNB 30 has already been set. Therefore, the subscriber information in step S1603 only needs to include some information element indicating whether or not the shared CNB 30 has already been set.
  • An example of the information element is IP address bandwidth information assigned to the mobile terminal group, but is not limited thereto.
  • the subscriber information in step S1603 may indicate whether any mobile terminal 1 belonging to the mobile terminal group has already been attached to the CN 20.
  • step S1604 the mobility management node 3 determines whether the data bearer sharing of the mobile terminal 1 is necessary based on the terminal group information.
  • the mobility management node 3 transmits a bearer establishment request indicating that bearer sharing is necessary to the transfer node 4 (step S1604).
  • the bearer establishment request is, for example, Create Session Request in EPS or Create PDP Context Request in UMTS.
  • This bearer establishment request includes bearer shared information and the IP address of the mobile terminal 1 notified from the subscriber information database 6.
  • requirement may show the IP address band allocated to the terminal group.
  • the external gateway 5 can manage the shared CNB 30 in units of mobile terminal groups (in units of IP address bands), and can reduce the number of entries in the bearer management table in the same way as the bearer management table shown in FIG.
  • step S1605 in response to receiving the bearer establishment request from the mobility management node 3, the forwarding node 4 generates an entry for a new data bearer in the bearer management table, and generates a bearer establishment request (including bearer sharing information). Transmit to the external gateway 5.
  • the external gateway 5 responds to the reception of the bearer establishment request including the bearer sharing information based on the tunnel endpoint identifier on the transfer node 4 side received from the transfer node 4, the IP address band of the mobile terminal group, and the like. Then, an entry related to the new shared CNB 30 is generated in the bearer management table. Further, the external gateway 5 updates the packet filter (e.g. TFT) applied to the shared CNB 30.
  • TFT packet filter
  • the external gateway 5 flows only the downlink user packet in which the IP address of one mobile terminal 1 that performs communication is designated as the destination to the shared CNB 30, and the downlink gateway in which the other IP address is designated as the destination.
  • the packet filter may be updated so as to discard the user packet.
  • the external gateway 5 transfers the user packet related to only one of the plurality of mobile terminals 1 belonging to the mobile terminal group that actually communicates by the shared CNB 30.
  • the external gateway 5 transmits a bearer establishment response to the transfer node 4.
  • This bearer establishment response includes the IP address band and the tunnel endpoint identifier on the external gateway 5 side. Further, the bearer establishment response may include additional information such as data bearer QoS.
  • the bearer establishment response is, for example, Create Session Response in EPS or Create PDP Context Response in UMTS.
  • the mobility management node 3 informs the subscriber information database 6 that the shared CNB 30 has been set for the mobile terminal group and started to be used for managing the usage status of the shared CNB 30 in the subscriber information database 6. Notice.
  • the usage notification of the shared CNB 30 may be transmitted from the mobility management node 3 to the subscriber information database 6 after step S1605, for example.
  • the subsequent processing in steps S1609 to S1615 may be the same as the normal data bearer establishment procedure, for example, the procedure described in Section 5.3.1 “Attach” procedure ”of Non-Patent Document 1.
  • FIG. 39A and FIG. 39B show the processing procedure of the bearer establishment request from the second and subsequent mobile terminals 1 in the mobile terminal group with respect to the improvement B-1.
  • the processing in steps S1701 and S1702 is the same as the processing in steps S1601 and S1602 in FIG. 38A.
  • the subscriber information database 6 determines that the terminal belongs to a specific mobile terminal group based on the identifier (eg IMSI) of the source terminal of the bearer establishment request, and issues an IP address to the mobile terminal 1.
  • the identifier eg IMSI
  • the subscriber information database 6 transmits the subscriber information to the mobility management node 3.
  • the subscriber information includes the terminal group information, the IP address of the mobile terminal 1, and the usage status of the shared CNB 30.
  • Whether or not the shared CNB 30 has been set for the mobile terminal group may be determined based on, for example, whether or not at least one mobile terminal 1 belonging to the mobile terminal group has been attached. Whether the shared CNB 30 is in use for any mobile terminal 1 belonging to the mobile terminal group, in other words, whether any mobile terminal 1 belonging to the mobile terminal group is communicating, for example, Alternatively, it may be determined whether or not the mobile terminal 1 in the CONNECTED state (eg ECM-CONNECTED) exists in the mobile terminal group instead of the IDLE state (eg ECM-IDLE).
  • CONNECTED state eg ECM-CONNECTED
  • IDLE eg ECM-IDLE
  • the mobility management node 3 determines the occurrence of this state transition as subscriber information.
  • the database 6 may be notified.
  • the mobility management node 3 sends a notification to the subscriber information database 6 indicating that the use of the shared CNB 30 is started in order to manage the usage status of the shared CNB 30 in the subscriber information database 6. Send.
  • the mobility management node 3 may confirm the usage status of the shared CNB 30 notified from the subscriber information database 6 and continue the bearer establishment procedure using the shared CNB 30 if the shared CNB 30 is not used. On the other hand, when the shared CNB 30 is in use, the mobility management node 3 may, for example, reject bearer establishment (similar to Reference Example 2 or Reference Example 4 described above) or set an additional normal bearer. Alternatively, user packets may be distributed at the forwarding node by associating an additional RAB with the shared CNB 40 (similar to the above-described reference example 3) (similar to the above-described reference example 5). Steps S1705 to S1711 in FIG. 39B show a procedure when the shared CNB 30 is unused. The processing in steps S1705 to S1711 in FIG. 39B is the same as the processing in steps S506 to S512 shown in FIG.
  • FIG. 40 The sequence diagram of FIG. 40 shows the data bearer recovery procedure for the improved B-1.
  • the mobile terminal 1 transmits a bearer recovery request.
  • the base station 2 transfers the bearer recovery request received from the mobile terminal 1 to the mobility management node 3.
  • the bearer recovery request is, for example, a Service request in EPS or a Service request in UMTS.
  • the mobility management node 3 refers to the bearer context managed by itself regarding the mobile terminal 1 that is the source of the bearer recovery request, and is shared when the source mobile terminal 1 is associated with the shared CNB 30.
  • the subscriber information database 6 is inquired about the usage status of the CNB 30.
  • the mobility management node 3 may confirm the usage status of the shared CNB 30 notified from the subscriber information database 6 and continue the bearer recovery procedure using the shared CNB 30 if the shared CNB 30 is not used.
  • the mobility management node 3 may, for example, reject bearer recovery (similar to the above-described Reference Example 2 or Reference Example 4), or set an additional normal bearer.
  • user packets may be distributed at the forwarding node by associating an additional RAB with the shared CNB 40 (similar to the above-described reference example 3) (similar to the above-described reference example 5).
  • step S1804 the mobility management node 3 sends a notification indicating that the use of the shared CNB 30 is started to the subscriber information database 6 in order to manage the usage status of the shared CNB 30 in the subscriber information database 6.
  • Steps S1805 to S1810 in FIG. 40 show a bearer recovery procedure when the shared CNB 30 is unused.
  • the processing in steps S1805 to S1810 in FIG. 40 is the same as the processing in steps S705 to S710 shown in FIG.
  • the procedure for establishing the data bearer including the shared CNB 30 in response to the request from the first mobile terminal 1 in the mobile terminal group in the improved B-2 is the improved B- described with reference to the sequence diagrams of FIGS. 38A and 38B. This is the same as the procedure of No. 1.
  • step S1901 and S1902 in FIG. 41A are the same as the processes in steps S1701 and S1702 in FIG. 39A.
  • step S1903 the subscriber information database 6 determines that the terminal belongs to a specific mobile terminal group based on the identifier (eg IMSI) of the transmission source terminal of the bearer establishment request, and is shared for this mobile terminal group. It is determined that the CNB 30 has been set. Then, the subscriber information database 6 transmits the subscriber information to the mobility management node 3.
  • the subscriber information includes terminal group information and the IP address of the mobile terminal 1.
  • the mobility management node 3 confirms the terminal group information notified from the subscriber information database 6 and inquires of the forwarding node 4 whether or not the shared CNB 30 is in use (step S1904).
  • the forwarding node 4 transmits to the mobility management node 3 a notification indicating whether or not the shared CNB 30 is used for any mobile terminal 1 belonging to the mobile terminal group.
  • the mobility management node 3 receives a notification indicating the usage status of the shared CNB 30 and controls bearer settings for the mobile terminal 1. That is, the mobility management node 3 may continue the bearer establishment procedure using the shared CNB 30 if the shared CNB 30 is not used.
  • the mobility management node 3 may, for example, reject bearer establishment (similar to Reference Example 2 or Reference Example 4 described above) or set an additional normal bearer.
  • user packets may be distributed at the forwarding node by associating an additional RAB with the shared CNB 40 (similar to the above-described reference example 3) (similar to the above-described reference example 5).
  • Steps S1906 to S1912 in FIG. 41B show a procedure when the shared CNB 30 is unused.
  • the processing in steps S1906 to S1912 in FIG. 41B is the same as the processing in steps S506 to S510 shown in FIG.
  • FIG. 42 The sequence diagram of FIG. 42 shows the data bearer recovery procedure for the improved B-2.
  • the improvement B-2 is different from the improvement B-1 (FIG. 40) in the step of confirming the usage status of the shared CNB 30.
  • the processes in steps S2001 and S2002 in FIG. 42 are the same as the processes in steps S1801 and S1802 in FIG.
  • the mobility management node 3 refers to the bearer context managed by itself regarding the mobile terminal 1 that is the transmission source of the bearer recovery request, and is shared when the mobile terminal 1 that is the transmission source is associated with the shared CNB 30.
  • the transfer node 4 is inquired about the usage status of the CNB 30.
  • the forwarding node 4 transmits a notification indicating the usage status of the shared CNB 30 to the mobility management node 3 (step S2004).
  • the mobility management node 3 may confirm the usage status of the shared CNB 30 notified from the forwarding node 4 and continue the bearer recovery procedure using the shared CNB 30 if the shared CNB 30 is not used.
  • the mobility management node 3 may, for example, reject bearer recovery (similar to the above-described Reference Example 2 or Reference Example 4), or set an additional normal bearer.
  • user packets may be distributed at the forwarding node by associating an additional RAB with the shared CNB 40 (similar to the above-described reference example 3) (similar to the above-described reference example 5).
  • Steps S2005 to S2010 in FIG. 42 show a bearer recovery procedure when the shared CNB 30 is unused.
  • the processes in steps S2005 to S2010 in FIG. 42 are the same as the processes in steps S705 to S710 shown in FIG.
  • FIGS. 43A and 43B relate to the improvement B-3 and establish a data bearer including the shared CNB 30 in response to a request from the first mobile terminal 1 in the mobile terminal group when the shared CNB 30 is not set.
  • the procedure to do is shown.
  • Steps S2101 to S2106 in FIG. 43A are the same as steps S401 to S406 in FIG.
  • step S2107 the external gateway 5 determines one IP address to be assigned to the mobile terminal 1 from the IP address band assigned to the mobile terminal group. Then, the external gateway 5 creates a new shared address based on the tunnel endpoint identifier on the transfer node 4 side received from the transfer node 4, the IP address band assigned to the mobile terminal group, the IP address assigned to the mobile terminal 1, and the like. An entry related to the CNB 30 is generated in the bearer management table. In step S2108, the external gateway 5 updates the packet filter (e.g. TFT) applied to the shared CNB 30.
  • TFT packet filter
  • the external gateway 5 flows only the downlink user packet in which the IP address of one mobile terminal 1 that performs communication is designated as the destination to the shared CNB 30, and the downlink gateway in which the other IP address is designated as the destination.
  • the packet filter may be updated so as to discard the user packet.
  • the external gateway 5 transfers the user packet related to only one of the plurality of mobile terminals 1 belonging to the mobile terminal group that actually communicates by the shared CNB 30.
  • the external gateway 5 transmits a bearer establishment response to the transfer node 4.
  • This bearer establishment response includes the IP address issued to the mobile terminal 1 and the tunnel endpoint identifier on the external gateway 5 side. Further, the bearer establishment response may include additional information such as data bearer QoS.
  • the bearer establishment response is, for example, Create Session Response in EPS or Create PDP Context Response in UMTS.
  • the subsequent processing in steps S2110 to S2116 may be the same as the normal data bearer establishment procedure, for example, the procedure described in Section 5.3.1 “Attach” procedure ”of Non-Patent Document 1.
  • FIG. 44A and FIG. 44B show the processing procedure of the bearer establishment request from the second and subsequent mobile terminals 1 in the mobile terminal group, regarding the improvement B-3.
  • the processing in steps S2201 to S2204 is the same as the processing in steps S2101 to S2104 in FIG. 43A.
  • the forwarding node 4 determines that the shared CNB 30 has already been set for this mobile terminal group based on the bearer sharing information, and for any mobile terminal 1 belonging to the mobile terminal group. It is determined whether the shared CNB 30 is in use.
  • the shared CNB 30 is in use, in other words, whether or not any mobile terminal 1 belonging to the mobile terminal group is communicating, for example, the shared CNB 30 is valid in the bearer management table of the forwarding node 4.
  • the mobility management node 3 detects the occurrence of this state transition when the mobile terminal 1 in the mobile terminal group transitions from the CONNECTED state (eg ECM-CONNECTED) to the IDLE state (eg ECM-IDLE). Can be notified.
  • the CONNECTED state eg ECM-CONNECTED
  • IDLE eg ECM-IDLE
  • the forwarding node 4 may continue the bearer establishment procedure using the shared CNB 30 if the shared CNB 30 is unused. On the other hand, when the shared CNB 30 is in use, the forwarding node 4 may return, for example, a bearer establishment rejection to the mobility management node 3 (similar to Reference Example 2 or Reference Example 4 described above) or additional A normal CNB may be set (similar to the above-described reference example 3), or an additional RAB may be associated with the shared CNB 40 to perform user packet distribution at the forwarding node (similar to the above-described reference example 5). . Steps S2206 to S2216 in FIGS. 44A and 44B show a procedure when the shared CNB 30 is unused.
  • step S2206 the forwarding node 4 transmits a bearer establishment request including bearer sharing information to the external gateway 5. Since the shared CNB 30 has already been set, if there is no change in the context of the shared CNB 30 (eg TEID, bearer QoS), the information element indicating these contexts may be omitted from the bearer establishment request in step S2206. . Instead, the bearer establishment request in step S2206 may indicate a request for issuing an IP address to the mobile terminal 1.
  • the bearer establishment request in step S2206 may indicate a request for issuing an IP address to the mobile terminal 1.
  • the external gateway 5 determines one IP address to be assigned to the mobile terminal 1 from the IP address band assigned to the mobile terminal group.
  • the external gateway 5 updates the packet filter (e.g. TFT) applied to the shared CNB 30.
  • the packet filter e.g. TFT
  • the external gateway 5 flows only the downlink user packet in which the IP address of one mobile terminal 1 that performs communication is designated as the destination to the shared CNB 30, and the downlink gateway in which the other IP address is designated as the destination.
  • the packet filter may be updated so as to discard the user packet.
  • the processing in steps S2209 to S2216 in FIG. 44B is the same as the processing in steps S2209 to S2216 in FIG. 43B.
  • the data bearer recovery procedure in the improved B-3 is the same as the data bearer recovery procedure in the improved B-2 described with reference to the sequence diagram of FIG.
  • the procedure for establishing the data bearer including the shared CNB 30 in response to the request from the first mobile terminal 1 in the mobile terminal group in the improved B-4 is the improved B- described with reference to the sequence diagrams of FIGS. 43A and 43B. This is the same as the procedure of No. 1.
  • step S2303 the subscriber information database 6 determines that the terminal belongs to a specific mobile terminal group based on the identifier (eg IMSI) of the source terminal of the bearer establishment request, and is shared for this mobile terminal group. It is determined that the CNB 30 has been set, and further, it is determined whether the shared CNB 30 is in use for any mobile terminal 1 belonging to the mobile terminal group. Then, the subscriber information database 6 transmits the subscriber information to the mobility management node 3.
  • the subscriber information includes terminal group information and usage status of the shared CNB 30.
  • the mobility management node 3 may confirm the usage status of the shared CNB 30 notified from the subscriber information database 6 and continue the bearer establishment procedure using the shared CNB 30 if the shared CNB 30 is not used. On the other hand, when the shared CNB 30 is in use, the mobility management node 3 may, for example, reject bearer establishment (similar to Reference Example 2 or Reference Example 4 described above) or set an additional normal bearer. Alternatively, user packets may be distributed at the forwarding node by associating an additional RAB with the shared CNB 40 (similar to the above-described reference example 3) (similar to the above-described reference example 5).
  • steps S2304 to S2316 show a procedure when the shared CNB 30 is not used.
  • the mobility management node 3 transmits a bearer establishment request including bearer sharing information to the transfer node 4.
  • the forwarding node 4 transmits a bearer establishment request to the external gateway 5.
  • the processes in steps S2306 to S2309 and S2311 to S2316 are the same as the processes in steps S2207 to S2216 shown in FIGS. 44A and 44B regarding the improvement B-3.
  • step S2310 of FIG. 45B the mobility management node 3 transmits a notification indicating that the use of the shared CNB 30 is started to the subscriber information database 6 in order to manage the usage status of the shared CNB 30 in the subscriber information database 6.
  • the data bearer recovery procedure in the improved B-4 is the same as the data bearer recovery procedure in the improved B-1 described with reference to the sequence diagram of FIG.
  • the IP address management of the mobile terminal group may be performed in a server (for example, Remote Authentication Authentication Dial In User Service (RADIUS) server) connected to the external gateway 5.
  • a server for example, Remote Authentication Authentication Dial In User Service (RADIUS) server
  • the external gateway 5 communicates with a server (eg RADIUS server), requests the mobile terminal group to issue an IP address band and issues an IP address to each mobile terminal 1, and sends the IP address band of the mobile terminal group.
  • the IP address to each mobile terminal 1 may be received from the server.
  • the above-described improvements B-1 and B-4 are that the communication management unit 7 described in Reference Examples 2 to 5 is the subscriber information in that the usage status management of the shared CNB 30 is arranged in the subscriber information database 6. It can be said that it is a form arranged in the database 6.
  • the first and second embodiments may be implemented in combination as appropriate.
  • Non-transitory computer readable media include various types of tangible storage media (tangible storage medium). Examples of non-transitory computer-readable media include magnetic recording media (eg flexible disks, magnetic tapes, hard disk drives), magneto-optical recording media (eg magneto-optical discs), CD-ROMs (Read Only Memory), CD-Rs, CD-R / W, semiconductor memory (for example, mask ROM, PROM (Programmable ROM), EPROM (Erasable ROM), flash ROM, RAM (random access memory)) are included.
  • the program may also be supplied to the computer by various types of temporary computer-readable media. Examples of transitory computer readable media include electrical signals, optical signals, and electromagnetic waves.
  • the temporary computer-readable medium can supply the program to the computer via a wired communication path such as an electric wire and an optical fiber, or a wireless communication path.
  • the mobile communication system according to the first and second embodiments may be other mobile communication systems.
  • a core network including a mobility management node, a plurality of forwarding nodes, and an external gateway;
  • the mobility management node is configured to manage a shared core network bearer (CNB) shared for user packet transfer of a plurality of mobile terminals belonging to a mobile terminal group,
  • the management of the shared CNB is a first mobile terminal belonging to the mobile terminal group while the shared CNB is already set between a first transfer node of the plurality of transfer nodes and the external gateway. Selecting the first forwarding node for the first mobile terminal when receiving a new bearer establishment request from Mobile communication system.
  • the appendix A1 further includes the management of the shared CNB further comprising: sending a control message indicating a bearer establishment request for the first mobile terminal or a modification request of the shared CNB to the first forwarding node.
  • the mobile communication system described. (Appendix A3) A mobility management node located in the core network, A control unit for managing a shared core network bearer (CNB) shared for user packet transfer of a plurality of mobile terminals belonging to a mobile terminal group;
  • the management of the shared CNB includes a first belonging to the mobile terminal group while the shared CNB is already set between a first forwarding node of a plurality of forwarding nodes in the core network and an external gateway.
  • CNB shared core network bearer
  • the appendix A3 further includes the management of the shared CNB further comprising: sending a control message indicating a bearer establishment request for the first mobile terminal or a modification request of the shared CNB to the first forwarding node. The control device described.
  • a communication control method in a mobility management node arranged in a core network In response to a bearer establishment request from a first mobile terminal belonging to a mobile terminal group, a shared core network bearer (CNB) shared for user packet transfer of a plurality of mobile terminals belonging to the mobile terminal group, Controlling the core network to be set between a first forwarding node of a plurality of forwarding nodes in the core network and an external gateway, and the shared CNB between the first forwarding node and the external gateway Selecting a first forwarding node for the second mobile terminal when a new bearer establishment request is received from a second mobile terminal belonging to the mobile terminal group while is already set ,
  • a communication control method comprising: (Appendix A6) Further comprising transmitting a control message indicating a bearer establishment request or a shared CNB modification request for the second mobile terminal to the first forwarding node.
  • the communication control method includes: In response to a bearer establishment request from a first mobile terminal belonging to a mobile terminal group, a shared core network bearer (CNB) shared for user packet transfer of a plurality of mobile terminals belonging to the mobile terminal group, Controlling the core network to be set between a first forwarding node of a plurality of forwarding nodes in the core network and an external gateway, and the shared CNB between the first forwarding node and the external gateway Selecting a first forwarding node for the second mobile terminal when a new bearer establishment request is received from a second mobile terminal belonging to the mobile terminal group while is already set , including, program.
  • CNB core network bearer
  • Appendix B1 A core network including a subscriber server, a mobility management node, a forwarding node, and an external gateway;
  • the subscriber server notifies the mobility management node of a user plane address of each mobile terminal belonging to the mobile terminal group;
  • the mobility management node controls the setting of the shared CNB so that a user packet corresponding to the user plane address is forwarded in a shared core network bearer (CNB),
  • the shared CNB is set between the forwarding node and the external gateway, and is shared for user packet forwarding of a plurality of mobile terminals belonging to the mobile terminal group.
  • Mobile communication system Appendix B2 The mobile communication system according to Appendix B1, wherein the subscriber server further notifies the mobility management node whether or not the shared CNB is already set.
  • appendix B3 The mobile communication according to appendix B2, wherein the notification as to whether or not the shared CNB has already been set is performed depending on whether or not to notify the mobility management node of a user plane address band assigned to the mobile terminal group. system.
  • Appendix B4 The notification as to whether or not the shared CNB has already been set is performed by notifying the mobility management node whether or not any mobile terminal belonging to the mobile terminal group has already been attached to the core network.
  • the subscriber server further notifies the mobility management node whether or not the shared CNB is used for any mobile terminal belonging to the mobile terminal group, according to any one of appendices B1 to B6.
  • the mobile communication system described. (Appendix B8) A communication control method in a core network including a subscriber server, a mobility management node, a forwarding node, and an external gateway, The subscriber server notifies the mobility management node of the user plane address of each mobile terminal belonging to the mobile terminal group, and the mobility management node allows a user packet corresponding to the user plane address to be shared core.
  • the shared CNB is set between the forwarding node and the external gateway, and is shared for user packet forwarding of a plurality of mobile terminals belonging to the mobile terminal group.
  • Communication control method (Appendix B9) The communication control method according to appendix B8, further comprising: notifying the mobility management node whether or not the shared CNB has already been set by the subscriber server. (Appendix B10) The communication control method according to attachment B9, wherein the notification of whether or not the shared CNB has already been set is performed depending on whether or not the user plane address band assigned to the mobile terminal group is notified.
  • the controlling includes a user plane address of the first mobile terminal when the attach request is received from the first mobile terminal while the shared CNB is already set up, and the shared
  • the communication control method according to appendix B12 comprising transmitting a control message indicating a CNB correction request from the mobility management node to the forwarding node.
  • Any one of appendices B8 to B13 further comprising: notifying the mobility management node from the subscriber server whether or not the shared CNB is used for any mobile terminal belonging to the mobile terminal group.
  • the communication control method according to the item.
  • Appendix B15 A subscriber server located in a core network, Notifying the mobile management node in the core network of the user plane address of each mobile terminal belonging to the mobile terminal group, and whether any mobile terminal belonging to the mobile terminal group is already attached to the core network An address management unit for notifying the mobility management node of Subscriber server.
  • Appendix B16 Notification of whether any mobile terminal belonging to the mobile terminal group is already attached to the core network is performed depending on whether to notify the user plane address band allocated to the mobile terminal group, The subscriber server according to Appendix B15.
  • Notification of whether any mobile terminal belonging to the mobile terminal group is already attached to the core network is performed by notifying whether a shared core network bearer (CNB) has already been configured,
  • the shared CNB is set between a forwarding node in the core network and an external gateway, and is shared for transferring user packets of a plurality of mobile terminals belonging to the mobile terminal group.
  • the subscriber server according to appendix B15 or B16.
  • the address management unit further notifies the mobility management node whether or not the shared CNB is used for any mobile terminal belonging to the mobile terminal group, according to any one of appendices B15 to B17.
  • (Appendix B19) A communication control method in a subscriber server arranged in a core network, Notifying the mobility management node in the core network of the user plane address of each mobile terminal belonging to the mobile terminal group, and whether any mobile terminal belonging to the mobile terminal group is already attached to the core network Informing the mobility management node of A communication control method comprising: (Appendix B20) Notification of whether any mobile terminal belonging to the mobile terminal group is already attached to the core network is performed depending on whether to notify the user plane address band allocated to the mobile terminal group, The communication control method according to attachment B19.
  • Notification of whether any mobile terminal belonging to the mobile terminal group is already attached to the core network is performed by notifying whether a shared core network bearer (CNB) has already been configured,
  • the shared CNB is set between a forwarding node in the core network and an external gateway, and is shared for transferring user packets of a plurality of mobile terminals belonging to the mobile terminal group.
  • the communication control method according to Appendix B19 or B20.
  • the communication control method includes: Notifying the mobility management node in the core network of the user plane address of each mobile terminal belonging to the mobile terminal group, and whether any mobile terminal belonging to the mobile terminal group is already attached to the core network Informing the mobility management node of including, program.
  • a core network including a mobility management node, a forwarding node, and an external gateway;
  • the mobility management node sends a request message to the forwarding node to set up a shared core network bearer (CNB) for the first mobile terminal.
  • the shared CNB is a core network bearer shared for user packet transfer of a plurality of mobile terminals belonging to the mobile terminal group.
  • the external gateway receives a control message based on the request message from the forwarding node, assigns a user plane address to the first mobile terminal, and transmits a user packet with the user plane address specified as a destination. Set a packet filter to flow to the shared CNB, Mobile communication system.
  • Appendix C2 The mobile communication system according to appendix C1, wherein the external gateway determines the user plane address to be allocated to the first mobile terminal from a user plane address band allocated to the mobile terminal group.
  • Appendix C3 The external gateway determines the user plane address bandwidth for the mobile terminal group and sets the shared CNB when the shared CNB is not set when the control message is received. The mobile communication system described.
  • An external gateway located in the core network A transfer unit that transfers user packets using a shared core network bearer (CNB) shared for user packet transfer of a plurality of mobile terminals belonging to a mobile terminal group; A control unit for controlling the setting of the shared CNB; With The control unit receives a control message indicating a first mobile terminal belonging to the mobile terminal group, assigns a user plane address to the first mobile terminal, and designates the user plane address as a destination Setting a packet filter for flowing user packets to the shared CNB; External gateway. (Appendix C5) The external gateway according to attachment C4, wherein the control unit determines the user plane address to be allocated to the first mobile terminal from a user plane address band associated with the mobile terminal group.
  • CNB shared core network bearer
  • (Appendix C6) If the shared CNB is not set when the control message is received, the control unit determines the user plane address band for the mobile terminal group and sets the shared CNB.
  • the listed external gateway. (Appendix C7) A communication control method in an external gateway arranged in a core network, Receiving a control message indicating a first mobile terminal belonging to a mobile terminal group; Assigning a user plane address to the first mobile terminal; and setting a packet filter for flowing a user packet with the user plane address specified as a destination to a shared core network bearer, the shared CNB, A core network bearer shared for user packet transfer of a plurality of mobile terminals belonging to the mobile terminal group; A communication control method comprising: (Appendix C8) The communication control method according to appendix C7, wherein the assigning includes determining the user plane address to be assigned to the first mobile terminal from a user plane address band associated with the mobile terminal group.
  • the method further comprises determining the user plane address bandwidth for the mobile terminal group and setting the shared CNB.
  • Communication control method A program for causing a computer to perform a communication control method in an external gateway arranged in a core network, The communication control method includes: Receiving a control message indicating a first mobile terminal belonging to a mobile terminal group; Assigning a user plane address to the first mobile terminal, and setting a packet filter for flowing a user packet with the user plane address specified as a destination to a shared core network bearer; Including The shared CNB is a core network bearer shared for user packet transfer of a plurality of mobile terminals belonging to the mobile terminal group. program.
  • a core network including a subscriber server, a mobility management node, a forwarding node, and an external gateway;
  • the forwarding node and the external gateway set between the forwarding node and the external gateway a shared core network bearer (CNB) shared for user packet forwarding of a plurality of mobile terminals belonging to a mobile terminal group,
  • the subscriber server sends a notification to the mobility management node indicating whether the shared CNB is used for any mobile terminal belonging to the mobile terminal group;
  • the mobility management node receives the notification and controls bearer configuration for a first mobile terminal belonging to the mobile terminal group; Mobility management system.
  • Appendix D2 The mobility management system according to attachment D1, wherein the notification indicates whether the shared CNB is used for a mobile terminal connected to another mobility management node different from the mobility management node.
  • Appendix D3 Appendix D1, wherein the mobility management node requests the forwarding node to modify the shared CNB for forwarding the user packet of the first mobile terminal in the shared CNB when the shared CNB is unused Or the movement management system as described in D2.
  • the mobility management node controls the setting of a new core network bearer for transferring the user packet of the first mobile terminal when the shared CNB is in use, any one of appendices D1 to D3 The mobility management system according to item.
  • a subscriber server located in a core network A management unit for transmitting a notification indicating whether a shared core network bearer (CNB) is used for any mobile terminal belonging to the mobile terminal group to the mobility management node in the core network;
  • the shared CNB is set between a forwarding node in the core network and an external gateway, and is shared for transferring user packets of a plurality of mobile terminals belonging to the mobile terminal group.
  • Subscriber server (Appendix D6) The subscriber server according to attachment D5, wherein the notification indicates whether or not the shared CNB is used for a mobile terminal connected to another mobility management node different from the mobility management node.
  • Appendix D7 A communication control method in a subscriber server arranged in a core network, Sending a notification indicating whether a shared core network bearer (CNB) is used for any mobile terminal belonging to the mobile terminal group to the mobility management node in the core network,
  • the shared CNB is set between a forwarding node in the core network and an external gateway, and is shared for transferring user packets of a plurality of mobile terminals belonging to the mobile terminal group.
  • Communication control method (Appendix D8) The communication control method according to attachment D7, wherein the notification indicates whether or not the shared CNB is used for a mobile terminal connected to another mobility management node different from the mobility management node.
  • Appendix D9 A program for causing a computer to perform a communication control method in a subscriber server arranged in a core network, The communication control method transmits a notification indicating whether a shared core network bearer (CNB) is used for any mobile terminal belonging to the mobile terminal group to a mobility management node in the core network.
  • the shared CNB is set between a forwarding node in the core network and an external gateway, and is shared for transferring user packets of a plurality of mobile terminals belonging to the mobile terminal group. program.
  • a core network including a mobility management node, a forwarding node, and an external gateway;
  • the forwarding node and the external gateway set between the forwarding node and the external gateway a shared core network bearer (CNB) shared for user packet forwarding of a plurality of mobile terminals belonging to a mobile terminal group,
  • the forwarding node sends a notification to the mobility management node indicating whether the shared CNB is used for any mobile terminal belonging to the mobile terminal group;
  • the mobility management node receives the notification and controls bearer configuration for a first mobile terminal belonging to the mobile terminal group; Mobility management system.
  • CNB shared core network bearer
  • appendix E2 The mobility management system according to appendix E1, wherein the notification indicates whether the shared CNB is used for a mobile terminal connected to another mobility management node different from the mobility management node.
  • the mobility management node requests the forwarding node to modify the shared CNB for forwarding the user packet of the first mobile terminal in the shared CNB when the shared CNB is unused. Or the mobility management system as described in E2.
  • the mobility management node controls the setting of a new core network bearer for transferring a user packet of the first mobile terminal when the shared CNB is in use, any one of appendix E1 to E3 The mobility management system according to item.
  • a forwarding node located in the core network A transfer unit that transfers user packets using a shared core network bearer (CNB) shared for user packet transfer of a plurality of mobile terminals belonging to a mobile terminal group; A control unit for transmitting a notification indicating whether the shared CNB is used for any mobile terminal belonging to the mobile terminal group to a mobility management node in the core network; With The shared CNB is set between the forwarding node and an external gateway in the core network, and is shared for user packet forwarding of a plurality of mobile terminals belonging to the mobile terminal group. Forwarding node.
  • CNB shared core network bearer
  • (Appendix E6) The forwarding node according to attachment E5, wherein the notification indicates whether or not the shared CNB is used for a mobile terminal connected to another mobility management node different from the mobility management node.
  • (Appendix E7) A communication control method in a forwarding node arranged in a core network, Sending a notification indicating whether a shared core network bearer (CNB) is used for any mobile terminal belonging to the mobile terminal group to the mobility management node in the core network,
  • the shared CNB is set between the forwarding node and an external gateway in the core network, and is shared for user packet forwarding of a plurality of mobile terminals belonging to the mobile terminal group. Forwarding node.
  • Appendix E8 The communication control method according to appendix E7, wherein the notification indicates whether or not the shared CNB is used for a mobile terminal connected to another mobility management node different from the mobility management node.
  • Appendix E9 A program for causing a computer to perform a communication control method in a transfer node arranged in a core network, The communication control method transmits a notification indicating whether a shared core network bearer (CNB) is used for any mobile terminal belonging to the mobile terminal group to a mobility management node in the core network.
  • CNB shared core network bearer
  • the shared CNB is set between the forwarding node and an external gateway in the core network, and is shared for user packet forwarding of a plurality of mobile terminals belonging to the mobile terminal group. program.

Landscapes

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

Abstract

Un serveur d'abonné (6) envoie, à un nœud de gestion de la mobilité (3), une adresse d'un plan utilisateur correspondant à chaque terminal mobile (1) appartenant à un groupe de terminaux mobiles. Le nœud de gestion de la mobilité (3) commande l'établissement d'un support de cœur de réseau partagé (CNB, Core Network Bearer) (30) de manière à ce que des paquets d'utilisateur correspondant aux adresses précitées du plan utilisateur soient réacheminés par ledit CNB partagé (30). Le CNB partagé (30) est établi entre un nœud de réacheminement (4) et une passerelle externe (5) et est partagé dans le but de réacheminer des paquets d'utilisateur vers la pluralité de terminaux mobiles (1) appartenant au groupe précité de terminaux mobiles. Cela permet par exemple à une pluralité de terminaux mobiles associés à différents nœuds de gestion de la mobilité d'utiliser un même support de cœur de réseau partagé.
PCT/JP2014/000453 2013-02-18 2014-01-29 Système de communication mobile, procédé de commande de communication et support lisible par ordinateur non transitoire WO2014125777A1 (fr)

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2013-029512 2013-02-18
JP2013029512 2013-02-18

Publications (1)

Publication Number Publication Date
WO2014125777A1 true WO2014125777A1 (fr) 2014-08-21

Family

ID=51353793

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2014/000453 WO2014125777A1 (fr) 2013-02-18 2014-01-29 Système de communication mobile, procédé de commande de communication et support lisible par ordinateur non transitoire

Country Status (1)

Country Link
WO (1) WO2014125777A1 (fr)

Cited By (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108632944A (zh) * 2017-03-21 2018-10-09 中兴通讯股份有限公司 用户面功能实体的选择方法和装置

Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005229447A (ja) * 2004-02-13 2005-08-25 Nec Corp Ｇｐｒｓネットワークシステム、ｇｐｒｓネットワークの構築方法
WO2010109902A1 (fr) * 2009-03-27 2010-09-30 シャープ株式会社 Systeme de communications mobiles
WO2011060707A1 (fr) * 2009-11-19 2011-05-26 华为技术有限公司 Procédés de traitement de support commun, nœud de réseau et système de communication

Patent Citations (3)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2005229447A (ja) * 2004-02-13 2005-08-25 Nec Corp Ｇｐｒｓネットワークシステム、ｇｐｒｓネットワークの構築方法
WO2010109902A1 (fr) * 2009-03-27 2010-09-30 シャープ株式会社 Systeme de communications mobiles
WO2011060707A1 (fr) * 2009-11-19 2011-05-26 华为技术有限公司 Procédés de traitement de support commun, nœud de réseau et système de communication

Cited By (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
CN108632944A (zh) * 2017-03-21 2018-10-09 中兴通讯股份有限公司 用户面功能实体的选择方法和装置
CN108632944B (zh) * 2017-03-21 2023-07-14 中兴通讯股份有限公司 用户面功能实体的选择方法和装置

Similar Documents

Publication Publication Date Title
JP6164219B2 (ja) 移動通信システム、制御装置、通信制御方法、及びプログラム
CN109392023B (zh) 一种数据流的操作控制的方法及设备
US10200908B2 (en) Methods, apparatus, a system, and a related computer program product for activation and deactivation of bearers
JP7046487B2 (ja) Ｕｅ、コアネットワーク装置及びｕｅの通信制御方法
CN105338655B (zh) 一种用户平面承载建立的方法及装置
WO2017167203A1 (fr) Procédé et un appareil permettant de commander une qualité de service
CN101605353B (zh) 一种数据通讯方法及通讯系统以及相关装置
JP6084035B2 (ja) パケットデータ網ゲートウェイ選択方法
JP5765429B2 (ja) 通信システムと方法と装置
US10588045B2 (en) Method and apparatus for handling data flow in wireless communication networks
CN103533500A (zh) 临近终端的通信方法及装置、系统
WO2011020386A1 (fr) Procédé d'indication, système pour un type de porteur et élément de réseau de dérivation de transmission
WO2013010415A1 (fr) Procédé, système et sgw pour réaliser une notification d'attributs d'adresse ip
WO2011026392A1 (fr) Procédé et système d'acquisition de stratégies d’itinéraire
JPWO2016076255A1 (ja) 端末装置、基地局装置、ｍｍｅおよび通信制御方法
WO2011134320A1 (fr) Procédé, système et dispositif pour demande d'autorisation
CN102014343A (zh) 群组策略与计费规则处理方法、装置以及通信系统
JP2013538470A (ja) Ｍｔｃにおいて生じるグループ変更のための方法
WO2017054611A1 (fr) Procédé et système de rattachement initial d'équipement utilisateur
WO2015120685A1 (fr) Procédé de sélection d'une passerelle de dérivation et contrôleur associé
CN102088795A (zh) 实现sipto的方法、移动管理控制节点设备
CN104427638B (zh) 集群会话承载的建立方法、装置及设备
WO2014125777A1 (fr) Système de communication mobile, procédé de commande de communication et support lisible par ordinateur non transitoire
CN101127610B (zh) 移动通信系统网络环境下的计费负流量的处理方法
WO2014125778A1 (fr) Système de communication mobile, dispositif de commande, terminal mobile, procédé de commande de communication et support pouvant être lu par ordinateur non transitoire

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

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP