[go: up one dir, main page]

WO2018131413A1 - Système de communication mobile et procédé de contrôle d'encombrement - Google Patents

Système de communication mobile et procédé de contrôle d'encombrement Download PDF

Info

Publication number
WO2018131413A1
WO2018131413A1 PCT/JP2017/045776 JP2017045776W WO2018131413A1 WO 2018131413 A1 WO2018131413 A1 WO 2018131413A1 JP 2017045776 W JP2017045776 W JP 2017045776W WO 2018131413 A1 WO2018131413 A1 WO 2018131413A1
Authority
WO
WIPO (PCT)
Prior art keywords
slice
mobile communication
unit
session
request
Prior art date
Application number
PCT/JP2017/045776
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 株式会社Ｎｔｔドコモ
Priority to JP2018561892A priority Critical patent/JP7064448B2/ja
Publication of WO2018131413A1 publication Critical patent/WO2018131413A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W76/00—Connection management
    • H04W76/10—Connection setup
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W88/00—Devices specially adapted for wireless communication networks, e.g. terminals, base stations or access point devices
    • H04W88/14—Backbone network devices

Definitions

  • the present invention relates to a mobile communication system and a congestion control method.
  • Non-Patent Document 1 discloses the architecture of the next generation system (NextGen) of the mobile communication system proposed in this standardization project.
  • This architecture is a mobile communication system having functions of MM (Mobility Management), SM (Session Management), and UP (U-Plane), and is an attach request (Attach) from a user terminal UE (User Equipment). Request) allows the UE to connect to DNN (Dedicated Network Name), which is the node to which it is connected, via one MM and multiple slices that are virtual networks configured with multiple SMs and UPs. It is configured to be
  • DNN Dedicated Network Name
  • an embodiment of the present invention is made in view of such problems, and provides a mobile communication system and a congestion control method that realize congestion control in slice units to enable efficient communication.
  • the purpose is
  • a mobile communication system includes a mobility management function unit that manages mobility of a mobile communication terminal, and a plurality of session managements that manage sessions of the mobile communication terminal.
  • a core network including a function unit and a plurality of user data transmission function units for transmitting and receiving user data used for service to a mobile communication terminal, comprising a plurality of session management function units and a plurality of user data transmission function units
  • a mobile communication system in which a plurality of slices, which are a plurality of virtual networks, are assigned to the mobile communication terminal, and a connection establishment request including slice specification information for specifying a slice from the mobile communication terminal is received; Congestion of the slice or congestion of the network to which the slice is connected based on If you comprises a retransmission request transmitting unit that a retransmission request for requesting retransmission of the connection establishment request to the mobile communication terminal.
  • a congestion control method comprising: a mobility management function unit managing mobility of a mobile communication terminal; a plurality of session management function units managing sessions of the mobile communication terminal; It has a core network including a plurality of user data transmission function units that transmit and receive user data used for services to terminals, and a plurality of virtual networks for a plurality of session management function units and a plurality of user data transmission function units
  • a congestion control method in a mobile communication system to which a plurality of slices are allocated comprising: receiving from a mobile communication terminal a connection establishment request including slice specifying information for specifying a slice; and based on the slice specifying information. Congestion of the slice or congestion of the network to which the slice is connected is identified. If a retransmission request for requesting retransmission of the connection establishment request to the mobile communication terminal.
  • congestion control on a slice basis can be realized to improve communication efficiency.
  • FIG. 1 is a diagram showing a system configuration of a mobile communication system 1 according to a preferred embodiment of the present invention. It is a block diagram which shows an example of the hardware constitutions of MM20 of FIG. It is a block diagram which shows the function structure of MM20 of FIG. It is a figure which shows an example of a data structure of the network management information hold
  • FIG. 1 is a diagram showing a system configuration of a mobile communication system 1 according to a preferred embodiment of the present invention.
  • this mobile communication system 1 is a mobile communication system according to the NextGen architecture, and includes MM (mobility management function unit), SM (session management function unit), and UP (user).
  • MM mobility management function unit
  • SM session management function unit
  • UP user
  • a core network including a data transmission function unit is included.
  • the mobile communication system 1 provides a communication function to a user's terminal by a virtual server operating in a virtual machine realized on a physical server.
  • MM is a node (functional unit) that manages the mobility (moving state) of the UE that is the user's mobile communication terminal
  • SM is a node that manages the communication session of the UE
  • UP Is a node that transmits and receives user data used for services between the UE and the core network.
  • a plurality of SMs and UPs can be provided in one mobile communication system 1.
  • two nodes SM 30a and 30b are provided as SM
  • two nodes UP 40a and 40b are provided as UP.
  • a plurality of slices which are a plurality of virtual networks, are allocated in advance to each of a plurality of arbitrary combinations of SM and UP, and different types of services are provided to the UE 10 in units of one or more slices.
  • a “slice” as used herein is a virtual network or service network logically generated on the network infrastructure by virtually separating the link of the network device and the resources of the node, and combining the separated resources. They separate resources and do not interfere with each other.
  • the “service” refers to a service using network resources such as communication service (exclusive line service etc.), application service (moving picture distribution, service using sensor device such as embedded device). For example, in the example illustrated in FIG.
  • the slice SLa is allocated to the SM 30a and the UP 40a
  • the slice SLb is allocated to the SM 30b and the UP 40b.
  • MM20, SM30a, 30b, and UP40a and 40b are explained.
  • the SM 30a and the SM 30b have the same function and may be described as the SM 30.
  • UP 40 a and UP 40 b have the same function and may be described as UP 40.
  • MM20, SM30, and UP40 also have general functions included in each element disclosed in “3GPP TR 23.799” or general documents related to mobile communication systems. It shall have.
  • the MM 20, the SM 30, and the UP 40 also have functions described using the sequence diagrams of FIGS. 6 to 7 and FIGS. 11 to 12 described later.
  • the MM 20 includes, as functional components, a mobility management function unit 21, a request reception unit 22, a congestion state identification unit 23, and an information storage unit (network information storage unit, slice allocation information storage unit) 24. , And a request reply unit (retransmission request transmission unit) 25.
  • each functional block may be realized by one physically and / or logically coupled device, or directly and / or indirectly two or more physically and / or logically separated devices. It may be connected by (for example, wired and / or wireless) and realized by the plurality of devices.
  • the MM 20 may function as a computer that performs the processing of the MM 20 according to the present embodiment.
  • FIG. 2 shows an example of the hardware configuration of the MM 20 according to the present embodiment.
  • the MM 20 may be physically configured as a computer device including a processor 1001, a memory 1002, a storage 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007 and the like.
  • the term "device” can be read as a circuit, a device, a unit, or the like.
  • the hardware configuration of the MM 20 may be configured to include one or more of the devices illustrated in the figure, or may be configured without some devices.
  • Each function in the MM 20 performs a calculation by causing the processor 1001 to read predetermined software (program) on hardware such as the processor 1001 and the memory 1002, and performs communication by the communication device 1004 and data in the memory 1002 and the storage 1003. This is realized by controlling the reading and / or writing of
  • the processor 1001 operates, for example, an operating system to control the entire computer.
  • the processor 1001 may be configured by a central processing unit (CPU: Central Processing Unit) including an interface with a peripheral device, a control device, an arithmetic device, a register, and the like.
  • CPU Central Processing Unit
  • the mobility management function unit 21, the request reception unit 22, the congestion state identification unit 23, the request reply unit 25, and the like may be realized by the processor 1001.
  • the processor 1001 reads a program (program code), a software module or data from the storage 1003 and / or the communication device 1004 to the memory 1002, and executes various processing according to these.
  • a program a program that causes a computer to execute at least a part of the operations described in the above embodiments is used.
  • the mobility management function unit 21 may be realized by a control program stored in the memory 1002 and operated by the processor 1001, or may be realized similarly for other functional blocks.
  • the various processes described above have been described to be executed by one processor 1001, but may be executed simultaneously or sequentially by two or more processors 1001.
  • the processor 1001 may be implemented by one or more chips.
  • the program may be transmitted from the network via a telecommunication line.
  • the memory 1002 is a computer readable recording medium, and includes, for example, at least one of a ROM (Read Only Memory), an EPROM (Erasable Programmable ROM), an EEPROM (Electrically Erasable Programmable ROM), and a RAM (Random Access Memory). It may be done.
  • the memory 1002 may be called a register, a cache, a main memory (main storage device) or the like.
  • the memory 1002 can store a program (program code), a software module, and the like that can be executed to execute various types of mobile communication processing according to an embodiment of the present invention.
  • the storage 1003 is a computer readable recording medium, and for example, an optical disc such as a CD-ROM (Compact Disc ROM), a hard disc drive, a flexible disc, a magneto-optical disc (eg, a compact disc, a digital versatile disc, a Blu-ray A (registered trademark) disk, a smart card, a flash memory (for example, a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like may be used.
  • the storage 1003 may be called an auxiliary storage device.
  • the above-mentioned storage medium may be, for example, a database including the memory 1002 and / or the storage 1003, a server or any other suitable medium.
  • the information holding unit 24 may be realized by the storage 1003.
  • the communication device 1004 is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also called, for example, a network device, a network controller, a network card, a communication module, or the like.
  • the request receiving unit 22 and the request replying unit 25 may be realized by the communication device 1004.
  • the input device 1005 is an input device that receives an input from the outside
  • the output device 1006 is an output device that implements output to the outside.
  • the input device 1005 and the output device 1006 may be realized by a touch panel display in which both are integrated.
  • bus 1007 for communicating information.
  • the bus 1007 may be configured by a single bus or may be configured by different buses among the devices.
  • the MM 20 is configured to include hardware such as a microprocessor, a digital signal processor (DSP), an application specific integrated circuit (ASIC), a programmable logic device (PLD), and a field programmable gate array (FPGA). Some or all of the functional blocks may be realized by the hardware. For example, processor 1001 may be implemented in at least one of these hardware.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • the mobility management function unit 21 is a part that performs position management of the UE 10 located in the mobile communication system 1, authentication control, and setting processing of communication data of control data or user data between the UP 40 and the UE 10.
  • the request reception unit 22 receives, from the UE 10, an attach request (Attach Request) for requesting establishment of connection of a communication path of control data.
  • the request receiving unit 22 includes, in the attach request, service type information (slice specifying information) or slice type information (slice specifying information) for identifying a slice, and DNN indicating an address of a connection destination node.
  • the mobility management function unit 21 performs a process of setting a session of control data between the UE 10 and the MM 20.
  • the request reception unit 22 receives, from the UE 10, a session request (PDU Session Request) for requesting establishment of connection of a communication path of user data following the attach request.
  • the request receiving unit 22 includes, in the session request, service type information (slice specifying information) or slice type information (slice specifying information) for identifying a slice, and DNN indicating an address of a connection destination node.
  • service type information aslice specifying information
  • slice type information slice type information
  • the congestion state identification unit 23 identifies a slice corresponding to service type information or slice type information included in the attach request, and congestion of a network to which the slice is connected. Identify the condition.
  • the congestion state specifying unit 23 specifies the network to which the slice is connected by referring to the network management information held in the information holding unit 24 and specifies the congestion state of the specified network.
  • parts (a) and (b) respectively show an example of the data configuration of the network management information held in the information holding unit 24.
  • slice type information for specifying a slice connected to the network for each of DNNs “DNN1” and “DNN2” for specifying a network of a connection destination.
  • “Slice # 1” and “Slice # 2” are associated with each other, and in the example of network management information shown in part (b) of FIG. 4, DNN “DNN2” and “DNN2” for identifying the connection destination network.
  • the slice type information “Slice # 1” and “Slice # 2” for identifying the slice connected to the network are associated with the above.
  • the congestion state identification unit 23 refers to the network management information shown in part (a) of FIG. 4 and transmits the slice “Slice # 1”.
  • the connection destination DNN “DNN1” is identified, and the congestion state of the DNN “DNN1” is identified.
  • the congestion state identification unit 23 may determine the congestion state by measuring the communication delay time between the MM 20 and the DNN, or the congestion state may be notified from the DNN, SM 30, or UP 40, etc. It is also good. In addition, the congestion state identification unit 23 may identify the congestion state each time an attach request is received, or may be performed in advance (at an arbitrary timing such as periodical). Further, the congestion state specifying unit 23 may specify the DNN of the connection destination of the slice based on the DNN included in the attach request, and may specify the congestion state of the specified DNN.
  • the congestion state identification unit 23 identifies a slice corresponding to service type information or slice type information included in the session request, and determines the congestion state of the slice. Identify. At this time, the congestion state specifying unit 23 specifies a slice by referring to the slice management information held in the information holding unit 24 and specifies the congestion state of the specified slice.
  • FIG. 5 shows an example of the data configuration of slice management information held in the information holding unit 24.
  • Identification information and UP identification information "SM1, UP1" and "SM2, UP2" are associated with each other.
  • a slice is assigned to each of the plurality of combinations of SMs 30 and UPs 40.
  • the congestion state identifying unit 23 refers to the slice management information shown in FIG. 5, and the SM 30 ′ assigned to the slice “Slice # 1”.
  • the SM 1 ′ ′ and the UP 40 “UP 1” are identified, and the congestion state of their SM 30 “SM 1” and UP 40 “UP 1” is identified.
  • the congestion state identification unit 23 may determine the congestion state by measuring the communication delay time between the MM 20 and the SM 30 or UP 40, or may be notified of the congestion state from the SM 30 or UP 40 or the like. Good. In addition, the congestion state identification unit 23 may identify the congestion state each time the session request is received, or may be performed in advance (at an arbitrary timing such as a regular interval).
  • the request reply unit 25 sends a response to the UE 10 in response to an attach request or a session request from the UE 10. That is, in response to the attach request, the request reply unit 25 sends back Attach Reject including a back-off timer when the congestion state of the network to which the slice is connected is identified as “congested”.
  • the attach rejection is a signal for requesting retransmission of the attach request
  • the backoff timer included in the attach rejection is a timer for indicating the timing of retransmission of the attach request.
  • the request reply unit 25 sends back a session rejection (PDU Session Reject) including a backoff timer when the slice congestion state is identified as “congested”.
  • the session rejection is a signal for requesting retransmission of the session request
  • the backoff timer included in the session rejection is a timer for indicating the timing of retransmission of the session request.
  • a session completion notification is returned after setting of the communication path of user data by the mobility management function unit 21.
  • FIG. 6 is a sequence diagram showing a procedure of setting processing of a communication route of control data by mobile communication system 1
  • FIG. 7 is a sequence showing a procedure of setting communication route of user data by mobile communication system 1.
  • step S101 the congestion state of DNN “DNN1" connected to slice “Slice # 1" is detected as “congested” by the congestion state specifying unit 23 of the MM 20 in advance.
  • step S102 when an attach request including slice type information "Slice # 1" and DNN "DNN1" is received from the UE 10 by the request reception unit 22 of the MM 20 (step S102), the congestion state identification unit 23 of the MM 20
  • the congestion state of DNN “DNN1” of the connection destination of slice “Slice # 1” is specified (step S103).
  • the attach rejection including the back-off timer from the request reply unit 25 of the MM 20 to the UE 10 Is returned (step S104).
  • the congestion state of the MM 20 itself may be detected in step S101, the congestion state of the MM 20 itself may be identified in step S103, and the attach rejection may be returned based on the congestion state of the MM 20 itself in step S104.
  • the SM 30 "SM1" assigned to the slice “Slice # 1" notifies that it is in the congestion state (step S201), and based on this notification, the congestion state identification unit 23 of the MM 20 makes the slice “Slice” in advance. It is assumed that the congestion state of # 1 ′ ′ is detected as “with congestion” (step S202).
  • the request receiving unit 22 of the MM 20 receives a session request including slice type information “Slice # 2” and DNN “DNN3” from the UE 10 (step S206)
  • the congestion state specifying unit 23 of the MM 20 slices After the congestion state of “Slice # 2” is identified as “no congestion” and the PDU-ID is allocated by the mobility management function unit 21 of the MM 20, the PDU-ID and slice type information “Slice # 2” and DNN “DNN3 A session request including “.” Is transmitted to the SM 30 “SM 2” assigned to the corresponding slice “Slice # 2” (step S 207).
  • a session completion notification is sent back from the SM 30 "SM 2" to the UE 10 via the MM 20 (steps S208 and S209).
  • management information for specifying a slice connected to the DNN is held for each DNN of the connection destination, the DNN of the connection destination of the slice is specified based on the management information, and the congestion state of the DNN Is identified. By doing this, the congestion state of the network to which the slice is connected can be properly identified. As a result, congestion control on a slice basis is appropriately realized.
  • management information for specifying slices assigned to a plurality of SMs and a plurality of UPs is held, and SMs or UPs assigned to a slice are specified based on the management information.
  • Congestion state is identified as a slice congestion state. By doing this, the congestion state of the slice is properly identified. As a result, congestion control on a slice basis is appropriately realized.
  • the SM or UP may be configured to identify a congestion state and control a reply to the UE 10 in response to a session request based on the congestion state.
  • the following describes the configuration in the case where the SM has a function of identifying a congestion state and a function of controlling a response to a session request.
  • FIG. 8 is a block diagram showing a hardware configuration of the SM 30A according to a modification of the SM 30 of the embodiment described above
  • FIG. 9 is a block diagram showing a functional configuration of the SM 30A.
  • the SM 30A includes, as functional components, a session management function unit 31, a request reception unit 32, a congestion state identification unit 33, an information storage unit (network information storage unit) 34, and a request reply unit A retransmission request transmission unit 35 is included.
  • each functional block may be realized by one physically and / or logically coupled device, or directly and / or indirectly two or more physically and / or logically separated devices. It may be connected by (for example, wired and / or wireless) and realized by the plurality of devices.
  • the SM 30A in the present modification may function as a computer that performs the processing of the SM 30A in the present modification.
  • FIG. 8 shows an example of the hardware configuration of the SM 30A according to the present modification.
  • the hardware configuration is the same as the configuration of FIG. 2 and thus detailed description will be omitted.
  • the session management function unit 31, the request reception unit 32, the congestion state identification unit 33, the request reply unit 35, and the like illustrated in FIG. 9 may be realized by the processor 1001.
  • the session management function unit 31 may be realized by a control program stored in the memory 1002 and operated by the processor 1001, or may be realized similarly for other functional blocks.
  • the information holding unit 34 and the like may be realized by the storage 1003.
  • the request receiving unit 32, the request replying unit 35, and the like may be realized by the communication device 1004.
  • the session management function unit 31 is a function unit that manages a session of a communication path (bearer) between the UE 10 located in the mobile communication system 1 and the UP 40. Specifically, bearer setting processing is executed in response to a session request from the MM 20.
  • the request reception unit 32 receives, from the UE 10 via the MM 20, a session request (PDU Session Request) for requesting establishment of connection of a communication path of user data. At this time, the request reception unit 32 transmits, to the session request, session identification information (PDU-ID) allocated by the MM 20, service type information (slice specification information) for identifying a slice, or slice type information (slice specification information And DNN indicating the address of the connection destination node.
  • the session management function unit 31 performs a process of setting a session for user data between the UE 10 and the UP 40 via the corresponding slice.
  • the congestion state identification unit 33 identifies a slice corresponding to service type information or slice type information included in the session request, and congestion of a network to which the slice is connected. Identify the condition.
  • the congestion state specifying unit 33 specifies the network to which the slice is connected by referring to the network management information held in the information holding unit 34, and specifies the congestion state of the specified network.
  • (a) part and (b) part respectively show an example of the data configuration of the network management information held in the information holding unit.
  • slice type information for specifying a slice connected to the network for each of the DNNs "DNN1" and "DNN2" for specifying a network of a connection destination.
  • “Slice # 1” and “Slice # 2” are associated with session identification information (PDU-ID) “PDU session # 1” and “PDU session # 2” for identifying a session set through a slice.
  • PDU-ID session identification information
  • Type information “Slice # 1”, “Slice # 2”, and session identification information (PDU-ID) “PDU session # 1” for identifying a session set through a slice, “PDU session "# 2" is associated.
  • multiple slices can be connected to the same DNN.
  • multiple sessions corresponding to slices may be set for the same DNN.
  • the congestion state identification unit 33 refers to network management information shown in part (a) of FIG. 10, and transmits the slice “Slice # 1”.
  • the connection destination DNN “DNN1” is identified, and the congestion state of the DNN “DNN1” is identified.
  • the congestion state identifying unit 33 may determine the congestion state by measuring the communication delay time between the SM 30A and the DNN, or may be notified of the congestion state from the DNN or UP 40 or the like. In addition, the congestion state identification unit 33 may identify the congestion state each time the session request is received, or may be performed in advance (at an arbitrary timing such as a regular interval). Further, the congestion state identification unit 33 may identify the DNN of the connection destination of the slice based on the DNN included in the session request, and may specify the congestion state of the identified DNN.
  • the congestion state identification unit 33 identifies a slice corresponding to service type information or slice type information included in the session request, and the congestion state of the slice itself Also identify. At this time, the congestion state identification unit 33 identifies the congestion state of its own SM 30A or UP 40 assigned to the identified slice.
  • the congestion state specifying unit 33 may determine the congestion state based on the congestion state of its own SM 30A, or may be notified of the congestion state such as UP 40 from UP 40 or the like assigned to the slice to be judged. For example, the determination of the congestion state is performed by determining whether or not the communication bandwidth allocated to the slice is congested. In addition, the congestion state identification unit 33 may identify the congestion state each time the session request is received, or may be performed in advance (at an arbitrary timing such as a regular interval).
  • the request reply unit 35 sends a response to the UE 10 via the MM 20 in response to the session request from the MM 20. That is, the request reply unit 35 rejects the session including the back-off timer when the congestion state of the network to which the slice is connected or the congestion state of the slice itself is identified as “congested” in response to the session request Returns PDU session Reject).
  • the session rejection is a signal for requesting retransmission of the session request
  • the backoff timer included in the session rejection is a timer for indicating the timing of retransmission of the session request.
  • FIGS. 11 and 12 are sequence diagrams showing a procedure of setting processing of a communication path of user data by the mobile communication system 1 according to the present modification.
  • a session request including slice type information "Slice # 1" and DNN "DNN1" is transmitted from the UE 10 to the MM 20 (step S301). Then, the MM 20 determines the SM 30 A allocated to the slice identified by the slice type information included in the session request, and the PDU-ID is allocated to the session between the UE 10 and the UP 40 (step S 302) .
  • the SM 30A specifies the congestion state of DNN “DNN1” that is the connection destination of slice “Slice # 1” (step S304).
  • session rejection including a back-off timer from the request reply unit 35 of the SM 30A to the MM 20 Is returned (step S305).
  • MM 20 the setting is changed so that all session requests for DNN “DNN1” from UE 10 return session rejection, and the PDU-ID allocated in step S 302 is deleted (see FIG. Step S306). Then, a session rejection including the newly set back-off timer is returned from the MM 20 to the UE 10 (step S307).
  • UE10 to MM20 including slice type information “Slice # 1” and DNN “DNN1”, and slice type information “Slice # 2” and DNN “DNN2” simultaneously request setting of two sessions It is assumed that a session request has been sent (step S308).
  • the MM 20 determines two SMs 30A “SM 1” and “SM 2” allocated to two slices specified by the slice type information included in the session request, and sets up between the UE 10 and the UP 40 A PDU-ID is assigned to each of the two sessions.
  • a session request including the PDU-ID, slice type information “Slice # 1”, and DNN “DNN1” is received from the MM 20 by the request receiving unit 32 of the one SM 30A that has been determined (step S309 ).
  • a session request including the PDU-ID, slice type information “Slice # 2”, and DNN “DNN2” is received from the MM 20 by the request reception unit 32 of the other SM 30A that has been determined (step S310).
  • congestion states of DNN "DNN1" and DNN “DNN2” are detected in advance in each of the two SMs 30A (steps S311 and S312).
  • the congestion state specifying unit 33 of one SM 30A specifies the congestion state of DNN "DNN1" connected to the slice "Slice # 1" (step S313).
  • the request reply unit 35 of one SM 30A directs the backoff timer (SM1 back-off timer) to the MM 20.
  • a session rejection including is returned (step S314).
  • the congestion state specifying unit 33 of the other SM 30A specifies the congestion state of DNN “DNN2” that is the connection destination of slice “Slice # 2” (step S315).
  • the request reply unit 35 of the other SM 30A directs the MM 20 to the backoff timer (SM2 back-off timer).
  • a session rejection including is returned (step S316).
  • the setting is changed to return session rejection for all the session requests for DNN "DNN1" and DNN “DNN2" from UE 10, and two PDU-IDs already allocated Is deleted (step S317). Then, a session rejection including two newly set back-off timers (SM1 back-off timer, SM2 back-off timer) is returned from the MM 20 to the UE 10 (step S318).
  • SM1 back-off timer SM2 back-off timer
  • a session request including slice type information "Slice # 1" and DNN “DNN1” is transmitted from the UE 10 to the MM 20 (step S402).
  • the MM 20 determines the SM 30 A allocated to the slice identified by the slice type information included in the session request, and the PDU-ID is allocated to the session between the UE 10 and the UP 40 (step S 403).
  • the SM 30A specifies the congestion state of the slice "Slice # 1" (step S405).
  • session rejection including a back-off timer from the request response unit 35 of the SM 30A to the MM 20 is performed.
  • a reply is sent (step S406).
  • Step S407 the setting is changed so that all session requests for slice "Slice # 1" from UE 10 will be returned, and the PDU-ID allocated in step S403 is deleted.
  • Step S408 a session rejection including a newly set back-off timer is returned from the MM 20 to the UE 10 (step S408).
  • a session request including slice type information “Slice # 2” and DNN “DNN3” is transmitted from the UE 10 to the MM 20 (step S409).
  • the MM 20 determines the SM 30 A allocated to the slice specified by the slice type information included in the session request, and the PDU-ID is allocated to the session between the UE 10 and the UP 40 (step S 410). .
  • step S 411 when a session request including PDU-ID, slice type information “Slice # 2” and DNN “DNN3” is received from the MM 20 by the request receiving unit 32 of the SM 30 A (step S 411), the SM 30 A
  • the congestion state specifying unit 33 specifies the congestion state of the slice "Slice # 2" (step S412).
  • a session completion notification is sent back from the request response unit 35 of the SM 30A to the MM 20 (step S413).
  • a session completion notification is transferred from the MM 20 to the UE 10 (step S 414).
  • notification of information is not limited to the aspects / embodiments described herein, and may be performed in other manners.
  • notification of information may be physical layer signaling (for example, Downlink Control Information (DCI), Uplink Control Information (UCI)), upper layer signaling (for example, Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof.
  • RRC signaling may be referred to as an RRC message, and may be, for example, an RRC connection setup (RRC Connection Setup) message, an RRC connection reconfiguration (RRC Connection Reconfiguration) message, or the like.
  • Each aspect / embodiment described in the present specification is LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G, 5G, FRA (Future Radio Access), W-CDMA (Registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi), IEEE 802.16 (WiMAX), IEEE 802.20, UWB (Ultra-Wide Band),
  • the present invention may be applied to a system utilizing Bluetooth (registered trademark), other appropriate systems, and / or an advanced next-generation system based on these.
  • Information and the like may be output from the upper layer (or lower layer) to the lower layer (or upper layer). Input and output may be performed via a plurality of network nodes.
  • the input / output information or the like may be stored in a specific place (for example, a memory) or may be managed by a management table. Information to be input or output may be overwritten, updated or added. The output information etc. may be deleted. The input information or the like may be transmitted to another device.
  • the determination may be performed by a value (0 or 1) represented by one bit, may be performed by a boolean value (Boolean: true or false), or may be compared with a numerical value (for example, a predetermined value). Comparison with the value).
  • notification of predetermined information is not limited to what is explicitly performed, but is performed by implicit (for example, not notifying of the predetermined information) It is also good.
  • Software may be called software, firmware, middleware, microcode, hardware description language, or any other name, and may be instructions, instruction sets, codes, code segments, program codes, programs, subprograms, software modules. Should be interpreted broadly to mean applications, software applications, software packages, routines, subroutines, objects, executables, threads of execution, procedures, functions, etc.
  • software, instructions, etc. may be sent and received via a transmission medium.
  • software may use a wireline technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or a website, server or other using wireless technology such as infrared, radio and microwave When transmitted from a remote source, these wired and / or wireless technologies are included within the definition of transmission medium.
  • wireline technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or a website, server or other using wireless technology such as infrared, radio and microwave
  • data, instructions, commands, information, signals, bits, symbols, chips etc may be voltage, current, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any of these May be represented by a combination of
  • radio resources may be indexed.
  • determining may encompass a wide variety of operations.
  • “Decision”, “decision” are, for example, calculating, computing, processing, deriving, investigating, looking up (eg, table, database or another) Search in data structures), ascertaining may be considered as “judgement” or “decision”.
  • “determination” and “determination” are receiving (e.g. receiving information), transmitting (e.g. transmitting information), input (input), output (output), access (accessing) (for example, accessing data in a memory) may be regarded as “judged” or “decided”.
  • connection means any direct or indirect connection or coupling between two or more elements, It can include the presence of one or more intermediate elements between two elements that are “connected” or “coupled”.
  • the coupling or connection between elements may be physical, logical or a combination thereof.
  • the two elements are by using one or more wires, cables and / or printed electrical connections, and radio frequency as some non-limiting and non-exclusive examples. It can be considered “connected” or “coupled” to one another by using electromagnetic energy such as electromagnetic energy having wavelengths in the region, microwave region and light (both visible and invisible) regions.
  • the phrase “based on” does not mean “based only on,” unless expressly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”
  • the present invention is applied to a mobile communication system and a congestion control method, and realizes congestion control on a slice basis to enable efficient communication.
  • SYMBOLS 1 mobile communication system 10 UE (mobile communication terminal) 20 MM (mobility management function unit) 30a 30b 30 SM (session management function unit 40a 40b 40 UP (user) Data transmission function unit) 21 mobility management function unit 22 request reception unit 23 congestion state identification unit 24 information holding unit (network information holding unit, slice allocation information holding unit) 25 request replying unit Retransmission request transmission unit) 31 Session management function unit 32 Request reception unit 33 Congestion state identification unit 34 Information storage unit (network information storage unit) 35 Request reply unit (retransmission request transmission unit) SLa, SLb ... slice.

Landscapes

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

Abstract

L'invention concerne un système de communication mobile (1) qui comporte un réseau central comprenant : un MM qui gère la mobilité d'un UE; une pluralité de SM qui gèrent une session de l'UE; et une pluralité d'UP qui transmettent/reçoivent des données d'utilisateur, une pluralité de tranches étant attribuées à la pluralité de SM et à la pluralité d'UP. Le système de communication mobile comprend une unité de réponse aux requêtes (25) qui transmet à l'UE une requête de retransmission consistant à demander la retransmission d'une requête d'établissement de connexion, lors de la réception, en provenance de l'UE, de la demande d'établissement de connexion qui comprend des informations de type tranche pour spécifier une tranche, et lorsque l'encombrement d'une tranche ou l'encombrement d'un réseau d'une cible de connexion de la tranche est spécifiée sur la base d'informations de type de tranche.
PCT/JP2017/045776 2017-01-10 2017-12-20 Système de communication mobile et procédé de contrôle d'encombrement WO2018131413A1 (fr)

Priority Applications (1)

Application Number Priority Date Filing Date Title
JP2018561892A JP7064448B2 (ja) 2017-01-10 2017-12-20 移動体通信システム及び輻輳制御方法

Applications Claiming Priority (2)

Application Number Priority Date Filing Date Title
JP2017001638 2017-01-10
JP2017-001638 2017-01-10

Publications (1)

Publication Number Publication Date
WO2018131413A1 true WO2018131413A1 (fr) 2018-07-19

Family

ID=62840156

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2017/045776 WO2018131413A1 (fr) 2017-01-10 2017-12-20 Système de communication mobile et procédé de contrôle d'encombrement

Country Status (2)

Country Link
JP (1) JP7064448B2 (fr)
WO (1) WO2018131413A1 (fr)

Cited By (6)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019098392A1 (fr) * 2017-11-20 2019-05-23 シャープ株式会社 Équipement utilisateur et procédé de contrôle de communication d'équipement utilisateur
JP2019097140A (ja) * 2017-11-20 2019-06-20 シャープ株式会社 端末装置、コアネットワーク内の装置、ｓｍｆ、及び通信制御方法
WO2020217532A1 (fr) * 2019-04-26 2020-10-29 株式会社Ｎｔｔドコモ Dispositif de gestion de session, dispositif de plan utilisateur, et procédé de communication
CN112690039A (zh) * 2018-09-21 2021-04-20 株式会社Ntt都科摩 网络节点
CN112822719A (zh) * 2021-01-12 2021-05-18 中国联合网络通信集团有限公司 网络切片调度方法及拥塞调度系统
JP2022539833A (ja) * 2019-07-09 2022-09-13 日本電気株式会社 ネットワークノード、ネットワークノードのための方法、ユーザ装置、及びネットワークスライス使用の制御のためのユーザ装置のための方法

Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015505660A (ja) * 2012-02-06 2015-02-23 インテル・コーポレーション 混雑している無線通信ネットワークにおける待ち時間の処理

Patent Citations (1)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
JP2015505660A (ja) * 2012-02-06 2015-02-23 インテル・コーポレーション 混雑している無線通信ネットワークにおける待ち時間の処理

Non-Patent Citations (3)

* Cited by examiner, † Cited by third party
Title
HUAWEI ET AL.: "Comparison of the options for session ID allocation and routing of subsequent SM signalling", 3GPP TSG-SA WG2 #118, S2-167000, 18 November 2016 (2016-11-18), pages 2 - 167000, XP051185441 *
HUAWEI ET AL.: "UE Slice Association/Overload control Procedure", 3GPP TSG-SA WG2#115, S2-162981, 27 May 2016 (2016-05-27), pages 2 - 162981, XP051116573 *
NEC ET AL.: "Updated interim agreements on session management", 3GPP TSG-SA WG2#117, S2-166281, 11 October 2016 (2016-10-11), pages 2 - 166281, XP051155802 *

Cited By (10)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
WO2019098392A1 (fr) * 2017-11-20 2019-05-23 シャープ株式会社 Équipement utilisateur et procédé de contrôle de communication d'équipement utilisateur
JP2019097140A (ja) * 2017-11-20 2019-06-20 シャープ株式会社 端末装置、コアネットワーク内の装置、ｓｍｆ、及び通信制御方法
US11343711B2 (en) 2017-11-20 2022-05-24 Sharp Kabushiki Kaisha UE and communication control method for UE
CN112690039A (zh) * 2018-09-21 2021-04-20 株式会社Ntt都科摩 网络节点
CN112690039B (zh) * 2018-09-21 2023-11-03 株式会社Ntt都科摩 网络节点
WO2020217532A1 (fr) * 2019-04-26 2020-10-29 株式会社Ｎｔｔドコモ Dispositif de gestion de session, dispositif de plan utilisateur, et procédé de communication
JP2022539833A (ja) * 2019-07-09 2022-09-13 日本電気株式会社 ネットワークノード、ネットワークノードのための方法、ユーザ装置、及びネットワークスライス使用の制御のためのユーザ装置のための方法
JP7311017B2 (ja) 2019-07-09 2023-07-19 日本電気株式会社 ネットワークノード、ネットワークノードのための方法、ユーザ装置、及びネットワークスライス使用の制御のためのユーザ装置のための方法
CN112822719A (zh) * 2021-01-12 2021-05-18 中国联合网络通信集团有限公司 网络切片调度方法及拥塞调度系统
CN112822719B (zh) * 2021-01-12 2023-02-24 中国联合网络通信集团有限公司 网络切片调度方法及拥塞调度系统

Also Published As

Publication number Publication date
JP7064448B2 (ja) 2022-05-10
JPWO2018131413A1 (ja) 2019-11-07

Similar Documents

Publication Publication Date Title
WO2018131413A1 (fr) Système de communication mobile et procédé de contrôle d'encombrement
CN110352611B (zh) 信息通知方法及移动通信系统
CN113287333B (zh) 网络节点和通知方法
JP6777451B2 (ja) 基地局
EP3687259B1 (fr) Procédé et dispositif de communication
US20190182733A1 (en) Communication control device and communication control method
CN112055380B (zh) 用于预测话务量的方法和装置
RU2771169C1 (ru) Пользовательское оборудование
CN111052822A (zh) 节点设备及其控制方法、程序
JPWO2018030545A1 (ja) コアネットワーク及び基地局
EP3522674B1 (fr) Procédés de commande de communication et systèmes de communication
JPWO2018061921A1 (ja) ゲートウェイ選択方法および通信システム
CN107710843A (zh) 用户装置、基站以及通信方法
CN112204895B (zh) 基站
CN110971431B (zh) 获取网络设备的配置信息的方法和相关装置
JP6954385B2 (ja) 無線装置、基地局、端末装置、無線通信システムおよび通信方法
US10674564B2 (en) Base station, management apparatus and connection method
US20210153191A1 (en) Network device, user device, and radio communication method
US20120102222A1 (en) System and Method for Local Operations in a Communications System
CN119895796A (zh) 用于在网络功能间通信的系统和方法
CN114375587B (zh) 终端
JP2018191148A (ja) 制御方法
JP2018170713A (ja) 通信端末
JP7077238B2 (ja) ゲートウェイ選択方法および通信システム
WO2019035404A1 (fr) Groupe de nœuds et procédé de migration

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

Country of ref document: EP

Kind code of ref document: A1

ENP Entry into the national phase

Ref document number: 2018561892

Country of ref document: JP

Kind code of ref document: A

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17891467

Country of ref document: EP

Kind code of ref document: A1