WO2018061924A1

WO2018061924A1 - Communication control method and communication system

Info

Publication number: WO2018061924A1
Application number: PCT/JP2017/033880
Authority: WO
Inventors: 拓也下城; 雅純清水; 淳巳之口; 滋岩科; スリサクルタコルスリ; マラレディサマ
Original assignee: 株式会社Ｎｔｔドコモ
Priority date: 2016-09-30
Filing date: 2017-09-20
Publication date: 2018-04-05

Abstract

In this communication system where a plurality of bearers are set between a UE and one or more SGWs via an eNB, the eNB measures an idle time for each of the bearers, and determines, for each of the bearers, whether or not the measured idle time has reached an idle timer threshold set in advance for each of the plurality of bearers (step 1). When determining, for one of the bearers, that the idle timer has reached the idle timer threshold (step 2), the eNB requests an MME to release the one bearer (step 4), and the MME executes a process of releasing the one bearer in accordance with the request from the eNB (step 5, etc.).

Description

Communication control method and communication system

The present invention relates to a communication control method executed in a communication system in which a terminal can simultaneously access a plurality of user data packet paths, and the communication system.

In a mobile network, a terminal (UE: User Equipment) uses a user data packet path (bearer (PDN connection), PDU) with a PDN (Packet Data Network) corresponding to the service in order to use a target service. (Referred to as Protocol Data Unit session)) (see Patent Document 1).

However, it is not necessary to establish a user data packet route when the terminal is not using the service. Therefore, in the existing technology, the base station that manages the terminal determines whether the user data packet path is in operation by monitoring the presence / absence of packets transmitted / received through the user data packet path. The user data packet path has been released and is in an idle state.

JP 2012-175575 A

In recent years, since it is assumed that a terminal uses a plurality of services at the same time, a technique in which a terminal accesses a plurality of user data packet paths at the same time is being proposed.

However, in the existing technology related to the operation status confirmation by the base station described above, a case where a terminal accesses a plurality of user data packet paths at the same time is not assumed. Therefore, if any one of the plurality of user data packet paths is operating, that is, if there is a packet transmitted / received on any one of the plurality of user data packet paths, the plurality of user data packet paths It is inconvenient that it is determined that all of these are operating (that is, not in an idle state).

The present invention has been made to solve the above-described problem. Even when a terminal accesses a plurality of user data packet paths at the same time, it appropriately determines the operating status of each path and performs control related to release of the path. One of the purposes is to appropriately perform the above.

A communication control method according to an aspect of the present invention includes a terminal, a base station, a processing server that executes processing related to the terminal, and one or a plurality of serving gateways, and a plurality of bearers pass through the base station. A communication control method executed in a communication system set up between the terminal and the one or more serving gateways, wherein the base station sets an idle time that is a duration of an idle state of a bearer Measuring each time, and the base station is an idle timer threshold value for determining that a bearer is in an idle state, and is measured to the idle timer threshold value determined in advance for each of the plurality of bearers Determining whether or not an idle time has been reached for each bearer; and for one bearer, the idle time for the idle timer threshold The base station requests the processing server to release the one bearer, and the processing server responds to the request from the base station in response to a request from the base station. Performing a release process.

In the communication control method described above, in a communication system in which a plurality of bearers are set between a terminal and one or a plurality of serving gateways via a base station, the base station measures the idle time for each bearer and is measured. It is determined for each bearer whether or not the idle time has reached a predetermined idle timer threshold for each of the plurality of bearers. When it is determined that the idle time has reached the idle timer threshold for one bearer, the base station requests the processing server to release the one bearer, and the processing server responds to the request from the base station. Release one bearer. Accordingly, even when the terminal accesses a plurality of bearers (user data packet paths) at the same time, it is possible to appropriately determine the operating status of each path and appropriately perform control related to the release of the path.

The present invention can also be applied to a so-called next generation network (NGN), and can be described as follows, for example. A communication control method according to an aspect of the present invention includes a terminal, a base station, a processing server that executes processing related to the terminal, a plurality of control planes that transmit control signals for communication services used by the terminal, A plurality of user planes that transmit user signals for the communication service, and a communication system in which a PDU session is set between the terminal and each of the plurality of user planes via the base station, The base station measures the idle time, which is the duration of the idle state of the PDU session, for each PDU session; and the base station determines that the PDU session is in the idle state. An idle timer threshold for determining that there is a predetermined idle for each of the plurality of PDU sessions. Determining, for each PDU session, whether or not the measured idle time has reached a timer threshold, and if it is determined that the idle time has reached the idle timer threshold for one PDU session; The base station requesting the processing server to release the one PDU session; and the processing server performing the one PDU session release process in response to a request from the base station. Prepare.

In the communication control method described above, in a communication system in which a PDU session is set between a terminal and each of a plurality of user planes via a base station, the base station measures the idle time for each PDU session and is measured. It is determined for each PDU session whether or not the idle time has reached a predetermined idle timer threshold for each of a plurality of PDU sessions. When it is determined that the idle time has reached the idle timer threshold for one PDU session, the base station requests the processing server to release the one PDU session, and the processing server responds to the request from the base station. In response, one PDU session is released. Accordingly, even when the terminal accesses a plurality of PDU sessions (user data packet paths) at the same time, it is possible to appropriately determine the operating status of each path and appropriately perform control related to the release of the path.

In addition, a communication control method according to another aspect of the present invention includes a terminal, a base station, a processing server that executes processing related to the terminal, and a plurality of control signals for transmitting a communication service used by the terminal. A control plane and a plurality of user planes transmitting user signals for the communication service, and a PDU session is set between the terminal and each of the plurality of user planes via the base station A communication control method executed in a communication system, wherein the terminal measures an idle time, which is a duration of an idle state of a PDU session, for each PDU session, and the terminal is in an idle state of a PDU session. This is an idle timer threshold value for judging that the ID is determined in advance for each of a plurality of PDU sessions. Determining whether or not the measured idle time has reached a timer limit for each PDU session, and if it is determined that the idle time has reached the idle timer threshold for one PDU session, The terminal requesting the processing server to release the one PDU session, and the processing server performing the one PDU session release process in response to a request from the terminal; The same effect as described above is achieved.

A communication control method according to still another aspect of the present invention includes a terminal, a base station, a processing server that executes processing related to the terminal, and a plurality of control signals for transmitting a communication service used by the terminal. And a plurality of user planes for transmitting user signals for the communication service, and a PDU session is set between the terminal and each of the plurality of user planes via the base station. A communication control method executed in a communication system, wherein the processing server measures an idle time, which is a duration of an idle state of a PDU session, for each PDU session; Is an idle timer threshold for determining that is in an idle state, and in advance for each of a plurality of PDU sessions Determining, for each PDU session, whether or not the measured idle time has reached the determined idle timer threshold, and determining that the idle time has reached the idle timer threshold for one PDU session In this case, the processing server includes a step of releasing the one PDU session, and has the same effect as described above.

According to the present invention, even when a terminal accesses a plurality of user data packet paths at the same time, it is possible to appropriately determine the operating status of each path and appropriately perform control related to the release of the path.

It is a figure which shows the structural example of the communication system which concerns on 1st Embodiment. (A) is a figure showing an example of a correspondence table concerning an idle timer held by MME, and (b) and (c) are figures showing an example of a correspondence table concerning an idle timer held by eNB. is there. It is a figure which shows the hardware structural example of each apparatus. It is a sequence diagram which shows the attach process in 1st Embodiment. It is a sequence diagram which shows the releasing process of S1 bearer in 1st Embodiment. It is a sequence diagram which shows the bearer release process in 1st Embodiment. It is a figure which shows the structural example of the communication system which concerns on 2nd Embodiment. It is a sequence diagram which shows the attach process in 2nd Embodiment. It is a sequence diagram which shows the bearer release process in 2nd Embodiment. It is a figure which shows the structural example of the communication system which concerns on 3rd Embodiment. It is a sequence diagram which shows the PDU session establishment process in 3rd Embodiment. It is a sequence diagram which shows the MBB slice release process in 3rd Embodiment. It is a sequence diagram which shows the PDU session establishment process in 4th Embodiment. It is a sequence diagram which shows the PDU session release process in 4th Embodiment. It is a figure which shows the structural example of the communication system which concerns on 5th Embodiment. It is a sequence diagram which shows the PDU session establishment process in 5th Embodiment. It is a sequence diagram which shows the PDU session release process in 5th Embodiment. It is a figure which shows the structural example of the communication system which concerns on 6th Embodiment. It is a sequence diagram which shows the PDU session establishment process in 6th Embodiment. It is a sequence diagram which shows the PDU session release process in 6th Embodiment. It is a sequence diagram which shows the PDU session establishment process in 7th Embodiment.

Hereinafter, first to seventh embodiments of the present invention will be described with reference to the drawings. In the first embodiment, multiple bearers are set between a plurality of SGWs (Serving gateways) different from a terminal (User Equipment (hereinafter referred to as “UE” in the embodiment of the invention)) in an EPC (Evolved Packet Core) network. In this embodiment, the eNodeB corresponding to the base station (hereinafter referred to as “eNB” in the embodiment of the present invention) takes the lead in controlling to release one of the plurality of bearers. In this embodiment, control is performed to release one bearer among a plurality of bearers under the circumstances where a plurality of bearers are set between a UE and a single SGW. In the third embodiment, a PDU session is set between a UE and each of a plurality of user planes in a so-called next generation network (NGN: Next Generation Network). The fourth embodiment is an embodiment that is different from the third embodiment regarding a so-called next-generation network. The fifth to seventh embodiments are various modifications relating to the next generation network. In the description of the drawings, the same elements are denoted by the same reference numerals, and redundant description is omitted.

[First Embodiment]
As described above, in the first embodiment, in a situation in which a plurality of bearers are set between a plurality of SGWs different from the UE in the EPC network, an embodiment for performing control to release one bearer among the plurality of bearers led by the base station. Will be explained.

(System configuration of the first embodiment)
As shown in FIG. 1, the communication system 1 according to the first embodiment includes a terminal (UE) 10, an eNB 20, and an MME (Processing for location management, authentication control, communication path setting, etc. of the UE 10 located in the network. Mobility Management Entity) 30, HSS (Home Subscriber Server) 60 that manages user information (subscriber information) of the terminal user, SGW 40 described later, and PGW (Packet data network gateway) described later located upstream of the SGW 40. 50. Here, the “processing server” according to the present invention corresponds to the MME 30.

The SGW 40 is a gateway device that functions as a serving packet switch that accommodates LTE, and one or a plurality of SGWs 40 are provided corresponding to the requirements of the communication service used by the UE 10.

The PGW 50 is a junction point with a PDN (Packet data network), and is a gateway device that performs IP address assignment, packet transfer to the SGW, and the like.

In this embodiment, as an example, an example will be described in which SGWs (here, SGW1, SGW2) and PGWs (here, PGW1, PGW2) are provided corresponding to requirements of a plurality of communication services used by the UE 10.

As a functional block related to the present invention, the eNB 20 measures the idle time, which is the duration of the idle state of the bearer, for each bearer, and sets the idle time measured by the measurement unit 21 to an idle timer threshold described later. A determination unit 22 that determines whether or not the bearer has been reached, and requests the MME 30 to release the one bearer when the determination unit 22 determines that the idle time has reached the idle timer threshold for one bearer. And a request unit 23. Further, the MME 30 includes a release processing unit 31 that performs a release process of one bearer in response to a request from the request unit 23.

The idle timer threshold value (hereinafter also referred to as “Idle timer” in the embodiment of the present invention) is an idle time reference value for determining that one bearer is in an idle state. It is determined in advance by the MME 30 (or SMF (Slice Management Function) (not shown)) based on the type, the usage type of the UE, the subscriber type of the terminal user, and the like. The MME 30 holds a correspondence table storing an E-RAN (Enterprise Radio Access Network) ID, EPS (Enhanced Packet System) ID, DCN (Data Center Network) ID, etc. and an idle timer threshold value in association with each other. The timer threshold value is notified to the eNB 20. As an example, a correspondence table storing the E-RAN ID and the idle timer threshold value shown in FIG. As shown in FIG. 2B, the Idle timer is stored in a table format, for example, in association with each bearer by the determination unit 22 of the eNB 20. The determination unit 22 determines for each bearer whether or not the idle time measured by the measurement unit 21 has reached the idle timer threshold, using the stored Idle timer information.

Here, an example of a hardware configuration of the eNB 20 corresponding to the “base station” of the present invention will be described with reference to FIG. The functional block (configuration unit) of the eNB 20 is realized by any combination of hardware and / or software. Further, the means for realizing each functional block is not particularly limited. In other words, each functional block may be realized by one device physically and / or logically coupled, or two physically and / or logically separated two wired and / or wirelessly linked to each other. You may implement | achieve with the above apparatus. Note that the hardware configuration example described below is not limited to the eNB 20 and may be employed in the HSS 60, the PGW 50, the SGW 40, the MME 30, and the UE 10 illustrated in FIG.

For example, the eNB 20 in an embodiment of the present invention may function as a computer that performs bearer (PDU session) release control according to the present invention. FIG. 3 is a diagram illustrating an example of a hardware configuration of the eNB 20 according to the embodiment of the present invention. The eNB 20 described above may be physically configured as a computer device including a processor 20A, a memory 20B, a storage 20C, a communication module 20D, an input device 20E, an output device 20F, a bus 20G, and the like.

In the following description, the term “apparatus” can be read as a circuit, a device, a unit, or the like. The hardware configuration of the eNB 20 may be configured to include one or a plurality of devices illustrated in the figure, or may be configured not to include some devices.

Each function in the eNB 20 reads predetermined software (program) on hardware such as the processor 20A and the memory 20B, so that the processor 20A performs calculation, performs communication by the communication module 20D, and stores data in the memory 20B and the storage 20C. This is realized by controlling reading and / or writing.

The processor 20A controls the entire computer by operating an operating system, for example. The processor 20A may be configured by a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like. For example, the measurement unit 21, the determination unit 22, the request unit 23, and the like described above may be realized by the processor 20A.

Further, the processor 20A reads a program (program code), a software module, and data from the storage 20C and / or the communication module 20D to the memory 20B, and executes various processes according to these. As the program, a program that causes a computer to execute at least a part of the operations described in the above embodiments is used. For example, the measurement unit 21, the determination unit 22, the request unit 23, and the like may be realized by a control program stored in the memory 20B and operated by the processor 20A, and may be similarly realized for other functional blocks. Although the above-described various processes have been described as being executed by one processor 20A, they may be executed simultaneously or sequentially by two or more processors 20A. The processor 20A may be implemented by one or more chips. Note that the program may be transmitted from a network via a telecommunication line.

The memory 20B is a computer-readable recording medium, and includes, for example, at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), and the like. May be. The memory 20B may be called a register, a cache, a main memory (main storage device), or the like. The memory 20B can store a program (program code), a software module, and the like that can be executed to implement the wireless communication method according to the embodiment of the present invention.

The storage 20C is a computer-readable recording medium, such as an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, a Blu-ray). (Registered trademark) disk, smart card, flash memory (for example, card, stick, key drive), floppy (registered trademark) disk, magnetic strip, and the like. The storage 20C may be called an auxiliary storage device. The above-described storage medium may be, for example, a database, a server, or other suitable medium including the memory 20B and / or the storage 20C.

The communication module 20D is hardware (transmission / reception device) for performing communication between computers via a wired and / or wireless network, and is also referred to as a network device, a network controller, a network card, or the like.

The input device 20E is an input device that accepts external input. The output device 20F is an output device (for example, a display, a speaker, an LED lamp, etc.) that performs output to the outside. Note that the input device 20E and the output device 20F may have an integrated configuration (for example, a touch panel).

Further, each device such as the processor 20A and the memory 20B is connected by a bus 20G for communicating information. The bus 20G may be configured with a single bus or may be configured with different buses between devices.

The eNB 20 includes 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). Alternatively, some or all of the functional blocks may be realized by the hardware. For example, the processor 20A may be implemented by at least one of these hardware.

(Processing content of the first embodiment)
Hereinafter, the processing content of the first embodiment will be described with reference to FIGS.

First, the attach process in the first embodiment will be described with reference to FIG. When the UE transmits an Attach Request for requesting an attach process to the eNB, the Attach Request is transmitted from the eNB to the MME (Step 1 in FIG. 4). Then, the MME selects “SGW1” as the SGW and “PGW1” as the PGW according to the service type used by the UE, and establishes a default bearer (step 2 in FIG. 4). At that time, although omitted in FIG. 4, UE authentication processing is also executed as in the conventional case. Further, the MME receives the idle timer information (IDLE timer1) when the UE uses the service related to the bearer 1 from the table of FIG. 2 (a) stored in the own device (MME) or from the SMF (not shown). When an Initial Context Request with E-RAN ID-1 and acquired IDLE timer1 added is sent to the eNB (step 3 in FIG. 4), an RRC connection is established between the UE and the eNB (FIG. 4). Step 4), thereby, bearer 1 is established between UE and eNB, between eNB and SGW1, and between SGW1 and PGW1. The eNB acquires the idle timer information (IDLE timer 1) related to the bearer 1 in step 3 described above.

In the same manner for the bearer 2, when the UE transmits a Bearer Request for the bearer 2 to the eNB, the Bearer Request is transmitted from the eNB to the MME (step 5 in FIG. 4). Then, the MME selects “SGW2” as the SGW and “PGW2” as the PGW according to the service type used by the UE, and establishes a default bearer (step 6 in FIG. 4). Further, the MME receives the idle timer information (IDLE timer 2) when the UE uses the service related to the bearer 2 from the table of FIG. 2 (a) stored in its own device (MME) or from the SMF (not shown). When an Initial Context Request with E-RAN ID-2 and acquired IDLE timer2 added is sent to the eNB (Step 7 in FIG. 4), an RRC connection is established between the UE and eNB (FIG. 4). Step 8) Thereby, bearer 2 is established between UE and eNB, between eNB and SGW2, and between SGW2 and PGW2. The eNB acquires idle timer information (IDLE timer 2) related to the bearer 2 in step 7 described above.

As described above,

bearers

1 and 2 are established by repeating almost the same bearer establishment procedure twice. In

steps

3 and 7, the EPS ID may be included in the Initial Context Request instead of the E-RAN ID for transmission.

In the first embodiment, the S1 bearer release process shown in FIG. 5 and the bearer release process shown in FIG. 6 can be executed as the process of releasing one bearer. Hereinafter, it demonstrates in order. Note that “S1” in the S1 bearer is an interface name between the eNB-MME and the eNB-SGW.

In the S1 bearer release process shown in FIG. 5, the idle timers of the

bearers

1 and 2 are operating in the eNB with the

bearers

1 and 2 already established (step 1 in FIG. 5). That is, the idle time is measured for each bearer by the measurement unit 21 in FIG. Then, when the idle timer of the bearer 2 reaches a threshold value (step 2 in FIG. 5) while there is no uplink / downlink traffic of one bearer (here, for example, bearer 2), the determination unit 22 in FIG. It is determined that the time has reached IDLE timer2, and the request unit 23 in FIG. 1 requests the bearer 2 to be released, and the bearer 2 release process is executed as follows.

Here, Radio Bearer Release is executed between eNB and UE for bearer 2 (step 3 in FIG. 5), and eNB sends S1 UE context Release Request including E-RAB (E-UTRAN Access Bearer) / EPS ID. It transmits to MME (step 4 of FIG. 5), and MME transmits Release Access Bearer Request to SGW2 corresponding to bearer 2 (step 5 of FIG. 5). Thereby, SGW2 releases S1 bearer between eNB and SGW2, and transmits Release Access Bearer Response to MME (step 6 of Drawing 5). After that, the MME sends an S1 UE context Release Command including the E-RAB / EPS ID to the eNB (Step 7 in FIG. 5), and RRC Connection Release is executed for the bearer 2 between the eNB and the UE that receives this ( Step 8) of FIG. 5, thereby releasing a specific S1 bearer (between eNB and SGW2) and a bearer between UE and eNB in bearer 2, and releasing a bearer between SGW2 and PGW2, as shown in FIG. It remains without being. On the other hand, the bearer 1 remains without being released.

At this time, since the bearer 1 remains without being released, the UE state remains Connected. Thereby, even when a terminal accesses a plurality of bearers at the same time, it is possible to appropriately determine the operating status of each bearer and appropriately perform control related to bearer release.

Next, the bearer release process shown in FIG. 6 will be described. In the bearer release process shown in FIG. 6, the idle timers of the

bearers

1 and 2 are operating in the eNB with the

bearers

1 and 2 already established (step 1 in FIG. 6). That is, the idle time is measured for each bearer by the measurement unit 21 in FIG. Then, when the idle timer of the bearer 2 reaches a threshold value (step 2 in FIG. 6) while there is no up / down traffic of one bearer (for example, bearer 2 in this case), the determination unit 22 in FIG. It is determined that the time has reached IDLE timer2, and the request unit 23 in FIG. 1 requests the bearer 2 to be released, and the bearer 2 release process is executed as follows.

Here, Radio Bearer Release is executed between eNB and UE for bearer 2 (step 3 in FIG. 6), and eNB transmits Indication of Bearer Release including E-RAB / EPS ID to MME (FIG. 6). Step 4) The MME sends a Delete Bearer Command to the SGW 2 corresponding to the bearer 2 (step 5 in FIG. 6). Upon receiving this, SGW2 sends a Delete Bearer Command to PGW2 (step 6 in FIG. 6), PGW2 sends a Delete Bearer Request to SGW2 (step 7 in FIG. 6), and SGW2 deletes Delete Bearer Request. Is transmitted to the MME (step 8 in FIG. 6). Further, the MME sends a Deactivate Bearer Request including the E-RAB / EPS ID to the eNB (step 9 in FIG. 6), and the RRC Connection Release is executed for the bearer 2 between the eNB and the UE that receives the request (see FIG. 6). 6 step 10). After that, the eNB sends a Deactivate Bearer Response including the E-RAB / EPS ID to the MME (Step 11 in FIG. 6), and the MME sends a Delete Bearer Response to the SGW 2 (Step 12 in FIG. 6). The SGW 2 transmits a Delete Bearer Response to the PGW 2 (Step 13 in FIG. 6). As a result, the bearer 2 is released between the UE and the PGW 2 as shown in FIG.

[Second Embodiment]
As described above, in the second embodiment, in a situation where multiple bearers are set between a UE and a single SGW in an EPC network, control for releasing one bearer among the multiple bearers led by a base station (eNB) is performed. An embodiment to be performed will be described.

(System configuration of the second embodiment)
As shown in FIG. 7, the communication system 1S according to the second embodiment has substantially the same configuration as the communication system 1 (FIG. 1) of the first embodiment described above, but a plurality of bearers are between the UE 10 and a single SGW 40. Is different from the communication system 1 (FIG. 1) of the first embodiment in that it reaches a single PGW 50.

Functional blocks (release processing unit 31, measurement unit 21, etc.) related to the present invention included in eNB 20 and MME 30, the idle timer correspondence table shown in FIGS. 2 (a) and 2 (b), and hardware of each device in FIG. Since the hardware configuration example is the same as that of the first embodiment, a duplicate description is omitted here.

(Processing contents of the second embodiment)
Hereinafter, the processing content of the second embodiment will be described with reference to FIGS. 8 and 9. In the attach process in the second embodiment illustrated in FIG. 8, when the UE transmits an Attach Request requesting an attach process related to a plurality of bearers (here, bearers 1 and 2) to the eNB, the Attach Request is transmitted from the eNB to the MME. (Step 1 in FIG. 8). And MME selects a single SGW and a single PGW according to the service type etc. which UE uses, and establishes two default bearers (step 2 of FIG. 8). At that time, although omitted in FIG. 8, UE authentication processing is also executed as in the conventional case.

Then, the MME uses the idle timer information (IDLE timer 1) when the UE uses the service related to the bearer 1 and the idle timer information (IDLE timer 2) when the UE uses the service related to the bearer 2 as its own (MME). ) Is saved from the table in Fig. 2 (a) or SMF (not shown), and the Initial Context Request including the combination of E-RAN ID1 and IDLE timer1 and the combination of E-RAN ID2 and IDLE timer2 is sent to the eNB. After transmission (step 3 in FIG. 8), an RRC connection is then established between the UE and the eNB (step 4 in FIG. 8), which allows the UE and eNB, the eNB and the single SGW, and the single Bearer 1 and Bearer 2 are established between the SGW and the single PGW.

As described above,

bearers

1 and 2 are established by executing the bearer establishment procedure once.

In the second embodiment, a bearer release process shown in FIG. 9 is executed as a process of releasing one bearer. In the bearer release process shown in FIG. 9, with the

bearers

1 and 2 already established, the idle timer of the bearer 1 and the idle timer of the bearer 2 are operating in the eNB (step 1 in FIG. 9). That is, the idle time is measured for each bearer by the measurement unit 21 in FIG. Then, when the idle timer of the bearer 2 reaches a threshold value (step 2 in FIG. 9) without the uplink / downlink traffic of one bearer (here, for example, bearer 2), the determination unit 22 in FIG. It is determined that the time has reached IDLE timer2, and the request unit 23 in FIG. 1 requests the bearer 2 to be released, and the bearer 2 release process is executed as follows.

Here, Radio Bearer Release is executed between eNB and UE for bearer 2 (step 3 in FIG. 9), and eNB transmits Indication of Bearer Release including E-RAB / EPS ID to MME (FIG. 9). Step 4) The MME sends a Delete Bearer Command to the SGW (Step 5 in FIG. 9). Upon receiving this, the SGW sends a Delete Bearer Command to the PGW (step 6 in FIG. 9), the PGW sends a Delete Bearer Request to the SGW (step 7 in FIG. 9), and the SGW then deletes the Delete Bearer Request. Is transmitted to the MME (step 8 in FIG. 9). Further, the MME sends a Deactivate Bearer Request including the E-RAB / EPS ID to the eNB (step 9 in FIG. 9), and RRC Connection Release is executed for the bearer 2 between the eNB and the UE that receives the request (see FIG. 9). 9 step 10). Thereafter, the eNB transmits a Deactivate Bearer Response including the E-RAB / EPS ID to the MME (Step 11 in FIG. 9), and the MME transmits a Delete Bearer Response to the SGW (Step 12 in FIG. 9). The SGW transmits a Delete Bearer Response to the PGW (step 13 in FIG. 9). As described above, as shown in FIG. 9, the bearer 2 is released between the UE and the PGW.

[Third Embodiment]
As described above, in the third embodiment, in a so-called next generation network, a PDU session is set between the UE and each of a plurality of user planes, and one of the PDU sessions is led by a base station (eNB). An embodiment for performing control to release a PDU session will be described.

(System configuration of the third embodiment)
As shown in FIG. 10, the communication system 2 according to the third embodiment includes a terminal (UE) 10, an eNB 20 corresponding to a base station, and a common control plane (hereinafter referred to as an embodiment of the invention) in a next-generation network. (Hereinafter referred to as “Common CP”)) 35, SDM (Subscription Data Management) 65 for managing user information (subscriber information) of the terminal user, CP-SM (Control Plane-Session Management) 70 to be described later, And a user plane (hereinafter referred to as “UP” in the embodiment of the present invention) 80. Here, the “processing server” according to the present invention corresponds to Common CP35.

The CP-SM 70 corresponds to a session management function unit in a gateway that transmits a control signal for a communication service used by the UE 10, and one or more CP-SMs 70 are provided corresponding to the requirements of the communication service. Here, CP-SM1 and CP-SM2 are set as an example.

UP 80 corresponds to a gateway that transmits a user signal for a communication service used by UE 10, and UP 80 is set corresponding to each CP-SM 70. That is, UP-1 is set corresponding to CP-SM1, and UP-2 is set corresponding to CP-SM2.

In this embodiment, as shown in FIG. 10, as a communication service used by the UE 10, for example, a V2X (Vehicle to Everything) service and a video distribution service are assumed, and the processing of FIG. Therefore, a V2X session is set between the UE 10 and the UP-1, and an MBB (Mobile broadband) session is set between the UE 10 and the UP-2 for the moving image distribution service.

Common CP 35 and eNB 20 related functional blocks (release processing unit 36, measurement unit 21 and the like) related to the present invention, Idle timer correspondence table shown in FIGS. 2 (a) and 2 (c), and each of FIG. Since the hardware configuration example of the apparatus is the same as that of the first embodiment, a duplicate description is omitted here. The correspondence table of Idle timer shown in FIG. 2A is held by the Common CP 35 corresponding to the MME 30 in FIG. As shown in FIG. 2C, the idle timer is stored in a table format, for example, in association with each PDU session by the determination unit 22 of the eNB 20. The determination unit 22 determines, for each PDU session, whether or not the idle time measured by the measurement unit 21 has reached the idle timer threshold using the stored Idle timer information.

(Processing content of the third embodiment)
Hereinafter, the processing content of the third embodiment will be described with reference to FIGS. 11 and 12. In the attach process in the third embodiment shown in FIG. 11, first, UE authentication and slice selection are executed by a conventional method among UE, eNB and Common CP (abbreviated as “C-CP” in FIGS. 11 and 12). (Step 1 in FIG. 11). Here, a V2X slice is selected for the V2X service, and an MBB slice is selected for the video distribution service.

Next, when the UE transmits a PDU Session Request for the V2X slice to the eNB, the PDU Session Request is transmitted from the eNB to the Common CP (Step 2 in FIG. 11). Then, the Common CP obtains the user information (subscriber information) of the UE such as the UE ID from the SDM (Step 3 in FIG. 11), and transmits the PDU Session Request to the CP-SM1 (Step 4 in FIG. 11). . Furthermore, CP-SM1 selects UP-1 as the UP for the V2X slice (step 5 in FIG. 11), and transmits a PDU Session Request to UP-1 (step 6 in FIG. 11). Upon receiving the PDU Session Request, UP-1 sends a PDU Session Response to CP-SM1 as an affirmative response (Step 7 in FIG. 11), and CP-SM1 sends a PDU Session Response to the Common CP (FIG. 11). Step 8). Further, the Common CP obtains the idle timer information when the UE uses the V2X service from the table of FIG. 2 (a) stored in its own device (Common CP) or from the SMF (not shown), and the Session ID. Then, the PDU Session Response to which the UE ID, UP ID and the acquired idle timer information are added is transmitted to the eNB, and the eNB transmits the PDU Session Response to the UE (Step 9 in FIG. 11). In step 9, the eNB receives the PDU Session Response to which the idle timer information for the V2X slice is added, and acquires the idle timer information for the V2X slice. Then, a PDU session for the V2X slice (hereinafter referred to as “V2X PDU session”) is established between the UE and the eNB and between the eNB and the UP-1 (step 10 in FIG. 11).

For the PDU session for the MBB slice (hereinafter referred to as “MBB PDU session”), when the UE sends a PDU Session Request for the MBB slice to the eNB, the PDU Session Request is sent from the eNB to the Common CP. (Step 11 in FIG. 11). Thereafter, for the MBB slice, processing similar to Steps 3 to 8 is executed between Common CP, CP-SM2 and UP-2 (Step 12 in FIG. 11). Further, the Common CP acquires idle timer information when the UE uses the MBB service from the table of FIG. 2A stored in the own device (Common CP) or from the SMF (not shown), and the Session ID. Then, the PDU Session Response to which the UE ID, UP ID and the acquired idle timer information are added is transmitted to the eNB, and the eNB transmits the PDU Session Response to the UE (Step 13 in FIG. 11). In step 13, the eNB receives the PDU Session Response to which the idle timer information for the MBB slice is added, and acquires the idle timer information for the MBB slice. Then, an MBB PDU session is established between the UE and eNB and between the eNB and UP-2 (step 14 in FIG. 11).

As described above, a V2X PDU session and an MBB PDU session are established by repeating almost the same PDU session establishment procedure twice.

In the third embodiment, the process shown in FIG. 12 is executed as a process of releasing one PDU session. In the process shown in FIG. 12, the V2X PDU session and the MBB PDU session are already established, and the V2X PDU session idle timer and the MBB PDU session idle timer are operating in the eNB (step 1 in FIG. 12). . That is, the idle time is measured for each PDU session by the measurement unit 21 in FIG. When the idle timer of the PDU session reaches a threshold (IDLE timer 2) without any upstream / downstream traffic of one PDU session (for example, MBB PDU session in this case) (step 2 in FIG. 12), the judging unit 22 It is determined that the idle time of the MBB PDU session has reached IDLE timer2, and the request unit 23 requests the release of the MBB PDU session, and the MBB PDU session release process is executed as follows.

Here, the RRC Connection Release is executed between the eNB and the UE for the MBB PDU session (Step 3 in FIG. 12), and the eNB transmits a PDU Session Release Request including the UE ID and Session ID to the Common CP (FIG. 12). Step 4). Then, the Common CP identifies CP-SM2 from the Session ID included in the PDU Session Release Request (Step 5 in FIG. 12), and transmits the PDU Session Release Request including the UE ID and Session ID to CP-SM2. (Step 6 in FIG. 12). CP-SM2 sends a Release Session Request including the UE ID and Session ID to UP-2 (Step 7 in FIG. 12), and UP-2 corresponds to the UE ID included in the received Release Session Request. Release the UE context for the UE (step 8 in FIG. 12).

Then, UP-2 sends a Release Session Response including the UE ID and Session ID to CP-SM2 as an affirmative response (Step 9 in FIG. 12), and CP-SM2 includes the UE ID and Session ID. PDU Session Release Response is sent to Common CP (Step 10 in FIG. 12). Further, the MBB NAS (Network Attached Storage) is released between the Common CP and the UE (Step 11a in FIG. 12), and the MBB PDU session is released (Step 11b in FIG. 12). Thus, as shown in FIG. 12, the MBB PDU session is released between the UE and UP-2.

At this time, since the V2X PDU session remains without being released, the UE state remains Connected. Accordingly, even when the terminal accesses a plurality of PDU sessions at the same time, it is possible to appropriately determine the operating status of each PDU session and appropriately perform control related to PDU session release.

[Fourth Embodiment]
In the following fourth embodiment, an embodiment different from the third embodiment will be described with respect to a so-called next-generation network. In the fourth embodiment and the fifth to seventh embodiments described later, the MME in the EPC network is AMF (Access and Mobility Management Function), and the SGW is SMF (Session Management Function) and UP (U-Plane node), respectively. The node name is changed, and the message exchange between the MME-SGW in the EPC network is replaced with the message exchange between the AMF-SMF or the AMF-UP via the SMF. Further, the functions of SGW and PGW in the EPC network are integrated into UP, thereby omitting message exchange between SGW and PGW. Also in the fourth to seventh embodiments, a radio access network (RAN) includes a device corresponding to the base station (eNB) 20 described in the first to third embodiments. It is referred to as “RAN”.

FIG. 13 shows PDU session establishment processing in the fourth embodiment. Here, in a situation where the PDU session (PDU1) has already been set up between the UE and the first UP (UP # 1), the new PDU session (PDU2) becomes the UE and the second UP (UP # 2). Processes set between and are shown.

Specifically, when a request for a service provided by UP # 2 (Service Request (UP # 2)) is sent from the UE to the AMF via the RAN (step 1 in FIG. 13), the AMF is requested. Based on the service characteristics and the like, an idle timer threshold value for a new PDU session (PDU2) is calculated (step 2 in FIG. 13). Then, when the AMF transmits an Initial Context Setup Request to which the calculated PDU2 idle timer threshold information is added to the RAN (step 3 in FIG. 13), a radio bearer is set up between the UE and the RAN (FIG. 13). Step 4) After that, Initial Context Setup Complete is transmitted from the RAN to the AMF (Step 5 in FIG. 13). When the AMF sends a Modify Session Request to UP # 2 via the second SMF (SMF # 2) (Step 6 in FIG. 13), UP # 2 that has received the Modify Session Request receives Modify as an affirmative response. Session Response is transmitted to AMF via SMF # 2 (Step 7 in FIG. 13). Thereby, a new PDU session (PDU2) is established between the UE and the RAN and between the RAN and the UP # 2.

FIG. 14 shows a PDU session release process in the fourth embodiment. Here, a process of releasing one PDU session (PDU2) in a situation where a plurality of PDU sessions (PDU1, PDU2) are set is shown.

Specifically, in a situation where a plurality of PDU sessions (PDU1, PDU2) are set, an idle timer for each PDU is operating in the RAN. That is, the idle time is measured for each PDU session by the measurement unit 21 (FIG. 1) in the RAN (step 1 in FIG. 14). Then, when the idle timer of the PDU2 expires without the upstream / downstream traffic of one PDU session (here, PDU2) (step 2 in FIG. 14), the determination unit 22 (FIG. 1) expires the idle timer of the PDU2. PDU2 is requested to be released by the request unit 23 (FIG. 1), and the following PDU2 release process is executed.

Here, RRC Connection Release is executed between RAN and UE for PDU2 (step 3 in FIG. 14), and RAN sends UE Context Release Request for the service provided by UP # 2 to AMF (step in FIG. 14). 4). Then, when AMF sends a Release Access Session Request to UP # 2 via SMF # 2 (Step 5 in FIG. 14), UP # 2 that has received the Release Access Session Request receives Release Access Session Response as an affirmative response. It transmits to AMF via SMF # 2 (step 6 in FIG. 14). Further, the AMF sends a UE Context Release Command to the RAN as a response to the UE Context Release Request (step 7 in FIG. 14), while the RAN sends a UE Context Release Complete to the AMF (FIG. 14). Step 8). Accordingly, as shown in FIG. 14, PDU2 is released between the UE and the RAN and between the RAN and the UP # 2.

At this time, since another PDU session (PDU1) remains without being released, the UE state remains Connected. Accordingly, even when the UE accesses a plurality of PDU sessions at the same time, it is possible to appropriately determine the operating status of each PDU session and appropriately perform control related to PDU session release.

In the fourth embodiment and the fifth to seventh embodiments described later, the AMF is the “processing server” described in the claims, the SMF is the “control plane”, and the UP is the “user plane”. RAN corresponds to a “base station”, respectively.

According to the first to fourth embodiments described above, even when a terminal accesses a plurality of bearers or PDU sessions at the same time, the operation status of each bearer or each PDU session is appropriately determined to release the bearer or PDU session. Such control can be performed appropriately.

In addition, in the idle time monitoring for determining the operating status of each bearer or each PDU session, an idle timer threshold for determining that it is in an idle state is used. This idle timer threshold is determined by the base station (eNB). It is stored in association with each bearer or each PDU session as shown in FIG. 2 (b) and FIG. 2 (c). In this way, by managing the idle timer threshold by the base station (eNB), it is possible to appropriately monitor the idle time when a new bearer or PDU session is established, and to determine the operating status of each bearer or each PDU session. Can be done appropriately.

It should be noted that the HSS 60 in FIG. 1 and FIG. 7 and the SDM 65 in FIG. 10 are not essential components for the control related to the release of the bearer or PDU session of the present invention, and the appropriate idle timer threshold for each bearer or PDU session is As long as the configuration is notified, the HSS 60 and the SDM 65 may be omitted.

[Fifth Embodiment]
In the following fifth embodiment, regarding a so-called next generation network, instead of the RAN in the fourth embodiment, when the UE measures the idle time for each PDU session and the idle timer related to one PDU session expires. An embodiment for requesting release of the PDU session will be described.

As shown in FIG. 15, in the communication system according to the fifth embodiment, the UE 10 includes a measurement unit 21, a determination unit 22, and a request unit 23 according to the first to fourth embodiments instead of the radio access network (RAN) 25. In addition, as described above, the node name is changed to AMF37 for the MME in the EPC network and SMF75 and UP80 for the SGW, respectively. The RAN 25 includes a device corresponding to the base station (eNB) 20 described in the first to third embodiments, and is referred to as “RAN” below.

FIG. 16 shows a PDU session establishment process in the fifth embodiment. Here, in a situation where the PDU session (PDU1) has already been set up between the UE and the first UP (UP # 1), the new PDU session (PDU2) becomes the UE and the second UP (UP # 2). Processes set between and are shown.

Specifically, when a request for a service provided by UP # 2 (Service Request (UP # 2)) is sent from the UE to the AMF via the RAN (step 1 in FIG. 16), the AMF is requested. Based on the service characteristics and the like, an idle timer threshold for a new PDU session (PDU2) is calculated (step 2 in FIG. 16). Then, when the AMF transmits an Initial Context Setup Request to which the calculated PDU2 idle timer threshold information is added to the RAN (step 3 in FIG. 16), the Initial Context Setup Request is forwarded to the UE (in FIG. 16). In step 4), the UE acquires information on the idle timer threshold for PDU2 thereby. Thereafter, a radio bearer is set up between the UE and the RAN (step 5 in FIG. 16), and Initial Context Setup Complete is transmitted from the RAN to the AMF (step 6 in FIG. 16). Then, when the AMF sends a Modify Session Request to UP # 2 via the second SMF (SMF # 2) (Step 7 in FIG. 16), UP # 2 that has received the Modify Session Request receives Modify as a positive response. Session Response is transmitted to AMF via SMF # 2 (Step 8 in FIG. 16). Thereby, a new PDU session (PDU2) is established between the UE and the RAN and between the RAN and the UP # 2.

FIG. 17 shows a PDU session release process in the fifth embodiment. Here, a process of releasing one PDU session (PDU2) in a situation where a plurality of PDU sessions (PDU1, PDU2) are set is shown.

Specifically, in a situation where a plurality of PDU sessions (PDU1, PDU2) are set, an idle timer for each PDU is operating in the UE. That is, the idle time is measured for each PDU session by the measurement unit 21 in the UE 10 in FIG. 15 (step 1 in FIG. 17). Then, when the idle timer of the PDU2 expires without the uplink / downlink traffic of one PDU session (here, PDU2) (step 2 in FIG. 17), the determination unit 22 determines that the idle timer of the PDU2 has expired, The request unit 23 requests the release of PDU2, and the following PDU2 release process is executed.

Here, RRC Connection Release is executed between RAN and UE for PDU2 (Step 3 in FIG. 17), and RAN sends UE Context Release Request for the service provided by UP # 2 to AMF (Step in FIG. 17). 4). Then, when AMF sends a Release Access Session Request to UP # 2 via SMF # 2 (Step 5 in FIG. 17), UP # 2 that has received the Release Access Session Request receives Release Access Session Response as an affirmative response. It transmits to AMF via SMF # 2 (step 6 in FIG. 17). Further, the AMF transmits a UE Context Release Command to the RAN as a response to the UE Context Release Request (Step 7 in FIG. 17), while the RAN transmits a UE Context Release Complete to the AMF (FIG. 17). Step 8). Thus, as shown in FIG. 17, PDU2 is released between the UE and the RAN and between the RAN and the UP # 2.

[Sixth Embodiment]
In the following sixth embodiment, regarding a so-called next-generation network, when the AMF measures the idle time for each PDU session instead of the RAN in the fourth embodiment and the idle timer related to one PDU session expires. An embodiment for performing the PDU session release process will be described.

As shown in FIG. 18, in the communication system according to the sixth embodiment, the AMF 37 includes the measurement unit 21 and the determination unit 22 in the first to fourth embodiments in addition to the release processing unit 36.

FIG. 19 shows PDU session establishment processing in the sixth embodiment. Here, in a situation where the PDU session (PDU1) has already been set up between the UE and the first UP (UP # 1), the new PDU session (PDU2) becomes the UE and the second UP (UP # 2). Processes set between and are shown.

Specifically, when a service request (Service Request (UP # 2)) provided by UP # 2 is sent from the UE to the AMF via the RAN (step 1 in FIG. 19), the AMF is requested. Based on the service characteristics and the like, an idle timer threshold value for a new PDU session (PDU2) is calculated (step 2 in FIG. 19). When the AMF transmits an Initial Context Setup Request to the RAN (Step 3 in FIG. 19), the Initial Context Setup Request is transferred to the UE (Step 4 in FIG. 19). Thereafter, a radio bearer is set up between the UE and the RAN (step 5 in FIG. 19), and Initial Context Setup Complete is transmitted from the RAN to the AMF (step 6 in FIG. 19). Then, when the AMF sends a Modify Session Request to UP # 2 via the second SMF (SMF # 2) (Step 7 in FIG. 19), UP # 2 that received the Modify Session Request receives Modify as a positive response. Session Response is transmitted to AMF via SMF # 2 (Step 8 in FIG. 19). Thereby, a new PDU session (PDU2) is established between the UE and the RAN and between the RAN and the UP # 2.

FIG. 20 shows a PDU session release process in the sixth embodiment. Here, a process of releasing one PDU session (PDU2) in a situation where a plurality of PDU sessions (PDU1, PDU2) are set is shown.

Specifically, in a situation where a plurality of PDU sessions (PDU1, PDU2) are set, an idle timer for each PDU is operating in the AMF. That is, the idle time is measured for each PDU session by the measurement unit 21 in the AMF 37 in FIG. 18 (step 1 in FIG. 20). Then, when the idle timer of the PDU2 expires without the uplink / downlink traffic of one PDU session (here, PDU2), the determination unit 22 determines that the idle timer of the PDU2 has expired (step 2 in FIG. 20). The release processing unit 36 executes the following PDU2 release processing.

Here, RRC Connection Release between RAN and UE is executed for PDU2 (

Steps

3 and 4 in FIG. 20), and RAN sends UE Context Release Request for the service provided by UP # 2 to AMF (FIG. 20). Step 5). When the AMF sends a Release Access Session Request to UP # 2 via SMF # 2 (Step 6 in FIG. 20), UP # 2 that has received the Release Access Session Request receives Release Access Session Response as an affirmative response. It transmits to AMF via SMF # 2 (step 7 in FIG. 20). Furthermore, the AMF sends a UE Context Release Command to the RAN as a response to the UE Context Release Request (step 8 in FIG. 20), while the RAN sends a UE Context Release Complete to the AMF (FIG. 20). Step 9). Thus, as shown in FIG. 20, PDU2 is released between the UE and the RAN and between the RAN and the UP # 2.

[Seventh Embodiment]
In the following seventh embodiment, an embodiment will be described in which an SMF calculates an idle timer threshold for a new PDU session, instead of AMF, for a so-called next-generation network. In the following, an example is shown in which the RAN holds information on the calculated idle timer threshold and measures the idle time for each PDU session, but instead of the RAN as in the fifth and sixth embodiments, The idle timer threshold information calculated by the UE or AMF may be held, and the idle time may be measured for each PDU session.

FIG. 21 shows a PDU session establishment process in the seventh embodiment, which includes an idle timer threshold value calculation process by the SMF. In this case, in a situation where a PDU session (PDU1) has already been set up between the UE and the first UP (UP # 1), a new PDU session (PDU2) is transferred between the UE and the second UP (UP # 1). The process set between 2) is shown.

Specifically, when a service request (Service Request (UP # 2)) provided by UP # 2 is sent from the UE to the AMF via the RAN (step 1 in FIG. 21), the AMF PDU Session Request (UP # 2) is transmitted to the second SMF (SMF # 2) (step 2 in FIG. 21). Then, the SMF # 2 calculates an idle timer threshold for a new PDU session (PDU2) based on the requested service characteristics and the like (step 3 in FIG. 21). Thereafter, when the SMF # 2 transmits a PDU Session Response to which the calculated PDU2 idle timer threshold information is added to the AMF (step 4 in FIG. 21), the AMF receives the PDU2 idle timer threshold information. The added Initial Context Setup Request is transmitted to the RAN (Step 5 in FIG. 21). As a result, the RAN obtains information on the idle timer threshold for PDU2, and thereafter, it is possible to measure the idle time of PDU2 using the information on the threshold. Thereafter, a radio bearer is set up between the UE and the RAN (step 6 in FIG. 21), and Initial Context Setup Complete is transmitted from the RAN to the AMF (step 7 in FIG. 21). Further, when the AMF sends a Modify Session Request to UP # 2 via SMF # 2 (Step 8 in FIG. 21), UP # 2 that receives the Modify Session Request sends Modify Session Response as an affirmative response to SMF # 2. The data is transmitted to the AMF via (step 9 in FIG. 21). Thereby, a new PDU session (PDU2) is established between the UE and the RAN and between the RAN and the UP # 2.

As in the seventh embodiment, instead of the AMF, the SMF may calculate the idle timer threshold, and the information on the calculated idle timer threshold is appropriately transmitted to a device (here, RAN) that performs the idle time measurement. And retained.

As mentioned above, although this embodiment was described in detail, it is clear for those skilled in the art that this embodiment is not limited to embodiment described in this specification. The present embodiment can be implemented as a modification and change without departing from the spirit and scope of the present invention defined by the description of the scope of claims. Therefore, the description of the present specification is for illustrative purposes and does not have any limiting meaning to the present embodiment.

The notification of information is not limited to the aspect / embodiment described in this specification, and may be performed by other methods. For example, notification of information includes physical layer signaling (for example, DCI (Downlink Control Information), UCI (Uplink Control Information)), upper layer signaling (for example, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling), It may be implemented by broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof. Further, the RRC signaling may be called an RRC message, and may be, for example, an RRC connection setup message, an RRC connection reconfiguration message, or the like.

Each aspect / embodiment described in this specification includes 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-WideBand), The present invention may be applied to a Bluetooth (registered trademark), a system using another appropriate system, and / or a next generation system extended based on the system.

The processing procedures, sequences, flowcharts and the like of each aspect / embodiment described in this specification may be switched in order as long as there is no contradiction. For example, the methods described herein present the elements of the various steps in an exemplary order and are not limited to the specific order presented.

Information etc. can be output from the upper layer (or lower layer) to the lower layer (or upper layer). Input / output may be performed via a plurality of network nodes.

The input / output information or the like may be stored in a specific location (for example, a memory) or may be managed by a management table. Input / output information and the like can be overwritten, updated, or additionally written. The output information or the like may be deleted. The input information or the like may be transmitted to another device.

The determination may be performed by a value represented by 1 bit (0 or 1), may be performed by a true / false value (Boolean: true or false), or may be performed by comparing numerical values (for example, a predetermined value) Comparison with the value).

Each aspect / embodiment described in this specification may be used alone, in combination, or may be switched according to execution. In addition, notification of predetermined information (for example, notification of being “X”) is not limited to explicitly performed, but is performed implicitly (for example, notification of the predetermined information is not performed). Also good.

Software, whether it is called software, firmware, middleware, microcode, hardware description language, or other names, instructions, instruction sets, codes, code segments, program codes, programs, subprograms, software modules , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. should be interpreted broadly.

Further, software, instructions, etc. may be transmitted / received via a transmission medium. For example, software may use websites, servers, or other devices using wired technology such as coaxial cable, fiber optic cable, twisted pair and digital subscriber line (DSL) and / or wireless technology such as infrared, wireless and microwave. When transmitted from a remote source, these wired and / or wireless technologies are included within the definition of transmission media.

The information, signals, etc. described herein may be represented using any of a variety of different technologies. For example, data, commands, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description are voltages, currents, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these May be represented by a combination of

Note that the terms described in this specification and / or terms necessary for understanding this specification may be replaced with terms having the same or similar meaning.

The terms “system” and “network” used in this specification are used interchangeably.

In addition, information, parameters, and the like described in this specification may be represented by absolute values, may be represented by relative values from a predetermined value, or may be represented by other corresponding information. . For example, the radio resource may be indicated by an index.

The names used for the above parameters are not limited in any way. Further, mathematical formulas and the like that use these parameters may differ from those explicitly disclosed herein. Since various channels (eg, PUCCH, PDCCH, etc.) and information elements (eg, TPC, etc.) can be identified by any suitable name, the various names assigned to these various channels and information elements are However, it is not limited.

The base station (eNB) of this embodiment can accommodate one or a plurality of cells (also called sectors). When the base station accommodates a plurality of cells, the entire coverage area of the base station can be divided into a plurality of smaller areas, and each smaller area can be divided into a base station subsystem (for example, an indoor small base station RRH: Remote). A communication service can also be provided by Radio Head). The term “cell” or “sector” refers to part or all of the coverage area of a base station and / or base station subsystem that provides communication services in this coverage. Further, the terms “base station”, “eNB”, “cell”, and “sector” may be used interchangeably herein. A base station may also be referred to in terms such as a fixed station, NodeB, access point, femto cell, small cell, and the like.

A terminal (UE) is defined by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal , Wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate terminology.

As used herein, the terms “determining” and “determining” may encompass a wide variety of actions. “Judgment” and “decision” are, for example, judgment, calculation, calculation, processing, derivation, investigating, looking up (eg, table) , Searching in a database or another data structure), considering ascertaining as “determining”, “deciding”, and the like. In addition, “determination” and “determination” include receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access. (accessing) (e.g., accessing data in a memory) may be considered as "determined" or "determined". In addition, “determination” and “decision” means that “resolving”, “selecting”, “choosing”, “establishing”, and “comparing” are regarded as “determining” and “deciding”. May be included. In other words, “determination” and “determination” may include considering some operation as “determination” and “determination”.

As used herein, the phrase “based on” does not mean “based only on”, unless expressly specified otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”

In the present specification, when a designation such as “first” or “second” is used, any reference to the element does not generally limit the quantity or order of the elements. These designations can be used herein as a convenient way to distinguish between two or more elements. Thus, a reference to the first and second elements does not mean that only two elements can be employed there, or that in some way the first element must precede the second element.

As long as “include”, “comprising”, and variations thereof, are used in the specification or claims, these terms are similar to the term “comprising”. It is intended to be comprehensive. Furthermore, the term “or” as used herein or in the claims is not intended to be an exclusive OR.

In this specification, unless there is only one device that is clearly present in context or technically, a plurality of devices are also included.

DESCRIPTION OF

SYMBOLS

1, 1S, 2 ... Communication system, 10 ... UE (terminal), 20 ... eNB (base station), 20A ... Processor, 20B ... Memory, 20C ... Storage, 20D ... Communication module, 20E ... Input device, 20F ... Output device , 20G ... bus, 21 ... measurement unit, 22 ... determination unit, 23 ... request unit, 25 ... RAN (base station), 30 ... MME (processing server), 31 ... release processing unit, 35 ... Common CP (processing server) 36 ... Release processing unit, 37 ... AMF (processing server), 40 ... SGW, 50 ... PGW, 60 ... HSS, 65 ... SDM, 70 ... CP-SM (control plane), 80 ... UP (user plane).

Claims

A terminal, a base station, a processing server that executes processing related to the terminal, and one or more serving gateways, and a plurality of bearers pass through the base station and the terminal and the one or more serving gateways A communication control method executed in a communication system set in between,
The base station measuring for each bearer idle time, which is the duration of the idle state of the bearer;
Whether the measured idle time has reached the idle timer threshold for the base station to determine that the bearer is in an idle state and is predetermined for each of the plurality of bearers The step of judging for each bearer,
When it is determined that the idle time has reached the idle timer threshold for one bearer, the base station requests the processing server to release the one bearer;
The processing server performing a release process of the one bearer in response to a request from the base station;
A communication control method comprising:
In the step of requesting release of the one bearer, the processing server requests release of an S1 bearer corresponding to the one bearer.
The communication control method according to claim 1.
The communication system further includes one or more packet data network gateways located upstream of the serving gateway;
In the step of requesting the release of the one bearer, the processing server releases the S1 bearer corresponding to the one bearer and the bearer between the serving gateway corresponding to the one bearer and the packet data network gateway. Request,
The communication control method according to claim 1.
The idle timer threshold is stored in association with each bearer by the base station,
The communication control method according to any one of claims 1 to 3.
A terminal, a base station, a processing server for executing processing related to the terminal, a plurality of control planes for transmitting a control signal for a communication service used by the terminal, and a user signal for the communication service A communication control method executed in a communication system including a plurality of user planes, wherein a PDU session is set between the terminal and each of the plurality of user planes via the base station,
The base station measuring, for each PDU session, an idle time that is a duration of an idle state of the PDU session;
Whether the measured idle time has reached the idle timer threshold for the base station to determine that the PDU session is idle and predetermined for each of a plurality of PDU sessions. Determining whether or not for each PDU session;
When the base station determines that the idle time has reached the idle timer threshold for one PDU session, the base station requests the processing server to release the one PDU session;
The processing server performing a release process of the one PDU session in response to a request from the base station;
A communication control method comprising:
The idle timer threshold is stored in association with each PDU session by the base station,
The communication control method according to claim 5.
A terminal, a base station, a processing server that executes processing related to the terminal, and one or more serving gateways, and a plurality of bearers pass through the base station and the terminal and the one or more serving gateways A communication system set in between,
The base station
A measurement unit that measures the idle time, which is the duration of the idle state of the bearer, for each bearer;
Whether or not the idle time measured by the measuring unit has reached an idle timer threshold for determining that the bearer is in an idle state, the idle timer threshold being predetermined for each of the plurality of bearers And a determination unit that determines for each bearer,
A request unit that requests the processing server to release the one bearer when the determination unit determines that the idle time has reached the idle timer threshold for the one bearer;
With
The processing server
A release processing unit that performs a release process of the one bearer in response to a request from the base station;
Comprising
Communications system.
A terminal, a base station, a processing server for executing processing related to the terminal, a plurality of control planes for transmitting a control signal for a communication service used by the terminal, and a user signal for the communication service A communication system in which a PDU session is set between the terminal and each of the plurality of user planes via the base station,
The base station
A measurement unit that measures, for each PDU session, an idle time that is a duration of an idle state of the PDU session;
Whether or not the idle time measured by the measurement unit has reached an idle timer threshold for determining that the PDU session is in an idle state, which is predetermined for each of a plurality of PDU sessions. A determination unit that determines for each PDU session;
A request unit that requests the processing server to release the one PDU session when the determination unit determines that the idle time has reached the idle timer threshold for one PDU session;
With
The processing server
A release processing unit that performs a release process of the one PDU session in response to a request from the base station;
Comprising
Communications system.
A terminal, a base station, a processing server for executing processing related to the terminal, a plurality of control planes for transmitting a control signal for a communication service used by the terminal, and a user signal for the communication service A communication control method executed in a communication system including a plurality of user planes, wherein a PDU session is set between the terminal and each of the plurality of user planes via the base station,
The terminal measures, for each PDU session, an idle time that is a duration of an idle state of the PDU session;
Whether or not the measured idle time has reached the idle timer threshold for determining that the PDU session is in an idle state, which is predetermined for each of a plurality of PDU sessions. Determining for each PDU session;
The terminal requesting the processing server to release the one PDU session when it is determined that the idle time has reached the idle timer threshold for one PDU session;
The processing server performing a release process of the one PDU session in response to a request from the terminal;
A communication control method comprising:
A terminal, a base station, a processing server for executing processing related to the terminal, a plurality of control planes for transmitting a control signal for a communication service used by the terminal, and a user signal for the communication service A communication control method executed in a communication system including a plurality of user planes, wherein a PDU session is set between the terminal and each of the plurality of user planes via the base station,
The processing server measuring, for each PDU session, an idle time that is a duration of an idle state of the PDU session;
Whether the measured idle time has reached the idle timer threshold for the processing server to determine that the PDU session is idle and is predetermined for each of a plurality of PDU sessions. Determining whether or not for each PDU session;
When it is determined that the idle time has reached the idle timer threshold for one PDU session, the processing server performs a release process of the one PDU session;
A communication control method comprising:
A terminal, a base station, a processing server for executing processing related to the terminal, a plurality of control planes for transmitting a control signal for a communication service used by the terminal, and a user signal for the communication service A communication system in which a PDU session is set between the terminal and each of the plurality of user planes via the base station,
The terminal
A measurement unit that measures, for each PDU session, an idle time that is a duration of an idle state of the PDU session;
Whether or not the idle time measured by the measurement unit has reached an idle timer threshold for determining that the PDU session is in an idle state, which is predetermined for each of a plurality of PDU sessions. A determination unit that determines for each PDU session;
A request unit that requests the processing server to release the one PDU session when the determination unit determines that the idle time has reached the idle timer threshold for one PDU session;
With
The processing server
A release processing unit that performs a release process of the one PDU session in response to a request from the terminal;
Comprising
Communications system.
A terminal, a base station, a processing server for executing processing related to the terminal, a plurality of control planes for transmitting a control signal for a communication service used by the terminal, and a user signal for the communication service A communication system in which a PDU session is set between the terminal and each of the plurality of user planes via the base station,
The processing server
A measurement unit that measures, for each PDU session, an idle time that is a duration of an idle state of the PDU session;
Whether or not the idle time measured by the measurement unit has reached an idle timer threshold for determining that the PDU session is in an idle state, which is predetermined for each of a plurality of PDU sessions. A determination unit that determines for each PDU session;
A release processing unit that performs release processing of the one PDU session when the determination unit determines that the idle time has reached the idle timer threshold for one PDU session;
Comprising
Communications system.