WO2018061924A1 - Procédé de commande de communication et système de communication - Google Patents

Procédé de commande de communication et système de communication Download PDF

Info

Publication number
WO2018061924A1
WO2018061924A1 PCT/JP2017/033880 JP2017033880W WO2018061924A1 WO 2018061924 A1 WO2018061924 A1 WO 2018061924A1 JP 2017033880 W JP2017033880 W JP 2017033880W WO 2018061924 A1 WO2018061924 A1 WO 2018061924A1
Authority
WO
WIPO (PCT)
Prior art keywords
pdu session
idle
bearer
terminal
base station
Prior art date
Application number
PCT/JP2017/033880
Other languages
English (en)
Japanese (ja)
Inventor
拓也 下城
雅純 清水
淳 巳之口
滋 岩科
スリサクル タコルスリ
マラ レディ サマ
Original Assignee
株式会社Ｎｔｔドコモ
Priority date (The priority date is an assumption and is not a legal conclusion. Google has not performed a legal analysis and makes no representation as to the accuracy of the date listed.)
Filing date
Publication date
Application filed by 株式会社Ｎｔｔドコモ filed Critical 株式会社Ｎｔｔドコモ
Publication of WO2018061924A1 publication Critical patent/WO2018061924A1/fr

Links

Images

Classifications

    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W72/00—Local resource management
    • H04W72/04—Wireless resource allocation
    • H—ELECTRICITY
    • H04—ELECTRIC COMMUNICATION TECHNIQUE
    • H04W—WIRELESS COMMUNICATION NETWORKS
    • H04W92/00—Interfaces specially adapted for wireless communication networks
    • H04W92/04—Interfaces between hierarchically different network devices
    • H04W92/12—Interfaces between hierarchically different network devices between access points and access point controllers

Definitions

  • 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.
  • a terminal 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).
  • PDN Packet Data Network
  • 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.
  • 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 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.
  • 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.
  • 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.
  • a communication control method 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.
  • 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.
  • a communication control method 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 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.
  • a communication control method 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
  • the processing server includes a step of releasing the one PDU session, and has the same effect as described above.
  • 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.
  • FIG. 1 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
  • (b) and (c) are figures showing an example of a correspondence table concerning an idle timer held by eNB. is there.
  • It is a sequence diagram which shows the releasing process of S1 bearer in 1st 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.
  • 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.
  • 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.
  • 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).
  • NTN 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.
  • the communication system 1 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.
  • 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.
  • PDN Packet data network
  • SGWs here, SGW1, SGW2
  • PGWs here, PGW1, PGW2
  • 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.
  • 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.
  • E-RAN Enterprise Radio Access Network
  • EPS Enhanced Packet System
  • DCN Data Center Network
  • 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.
  • 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
  • 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.
  • 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.
  • 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.
  • CPU central processing unit
  • the measurement unit 21, the determination unit 22, the request unit 23, and the like described above may be realized by the processor 20A.
  • 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.
  • a program program that causes a computer to execute at least a part of the operations described in the above embodiments is used.
  • 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.
  • 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).
  • 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.
  • DSP digital signal processor
  • ASIC application specific integrated circuit
  • PLD programmable logic device
  • FPGA field programmable gate array
  • the attach process in the first embodiment will be described with reference to FIG.
  • the Attach Request is transmitted from the eNB to the MME (Step 1 in FIG. 4).
  • 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).
  • UE authentication processing is also executed as in the conventional case.
  • 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.
  • IDLE timer1 idle timer information
  • 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.
  • the Bearer Request is transmitted from the eNB to the MME (step 5 in FIG. 4).
  • 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).
  • 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).
  • IDLE timer 2 the idle timer information
  • Step 7 in FIG. 4 an RRC connection is established between the UE and eNB (FIG. 4).
  • Step 8) 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.
  • bearers 1 and 2 are established by repeating almost the same bearer establishment procedure twice.
  • the EPS ID may be included in the Initial Context Request instead of the E-RAN ID for transmission.
  • 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.
  • “S1” in the S1 bearer is an interface name between the eNB-MME and the eNB-SGW.
  • 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.
  • 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.
  • E-RAB E-UTRAN Access Bearer
  • Step 8) of FIG. 5 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.
  • the bearer 1 remains without being released.
  • the bearer 1 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.
  • 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.
  • 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).
  • the MME sends a Delete Bearer Command to the SGW 2 corresponding to the bearer 2 (step 5 in FIG. 6).
  • 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).
  • 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).
  • 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).
  • the bearer 2 is released between the UE and the PGW 2 as shown in FIG.
  • the bearer 1 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.
  • 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.
  • 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).
  • IDLE timer 1 when the UE uses the service related to the bearer 1
  • IDLE timer 2 when the UE uses the service related to the bearer 2 as its own (MME).
  • 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.
  • 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.
  • bearers 1 and 2 are established by executing the bearer establishment procedure once.
  • a bearer release process shown in FIG. 9 is executed as a process of releasing one bearer.
  • 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.
  • 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).
  • the MME sends a Delete Bearer Command to the SGW (Step 5 in FIG. 9).
  • 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).
  • 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.
  • the bearer 1 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.
  • 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).
  • eNB base station
  • the communication system 2 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.
  • 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.
  • 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.
  • 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.
  • V2X Vehicle to Everything
  • MBB Mobile broadband
  • 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) 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.
  • 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.
  • 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).
  • C-CP Common CP
  • Step 1 in FIG. 11 a V2X slice is selected for the V2X service, and an MBB slice is selected for the video distribution service.
  • the PDU Session Request is transmitted from the eNB to the Common CP (Step 2 in FIG. 11).
  • 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).
  • 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).
  • UP-1 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.
  • 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).
  • 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.
  • 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).
  • MBB PDU session 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.
  • 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.
  • 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).
  • 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.
  • an MBB PDU session is established between the UE and eNB and between the eNB and UP-2 (step 14 in FIG. 11).
  • V2X PDU session and an MBB PDU session are established by repeating almost the same PDU session establishment procedure twice.
  • the process shown in FIG. 12 is executed as a process of releasing one PDU session.
  • 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.
  • 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.
  • 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).
  • 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.
  • 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).
  • 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).
  • MBB NAS Network Attached Storage
  • the MBB PDU session is released (Step 11b in FIG. 12).
  • the MBB PDU session is released between the UE and UP-2.
  • 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.
  • the MME in the EPC network is AMF (Access and Mobility Management Function)
  • 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.
  • the functions of SGW and PGW in the EPC network are integrated into UP, thereby omitting message exchange between SGW and PGW.
  • a radio access network 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.
  • PDU1 the PDU session
  • PDU2 the new PDU session
  • UP # 2 the UE and the second UP
  • UP # 2 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.
  • PDU2 PDU session
  • FIG. 14 shows a PDU session release process in the fourth embodiment.
  • a process of releasing one PDU session (PDU2) in a situation where a plurality of PDU sessions (PDU1, PDU2) are set is shown.
  • 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.
  • 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.
  • PDU1 PDU1
  • PDU1 PDU1
  • 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.
  • the AMF is the “processing server” described in the claims
  • the SMF is the “control plane”
  • the UP is the “user plane”.
  • RAN corresponds to a “base station”, respectively.
  • 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.
  • 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.
  • 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.
  • 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.
  • 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.
  • PDU1 the PDU session
  • PDU2 the new PDU session
  • UP # 2 the UE and the second UP
  • UP # 2 Service Request (UP # 2)
  • UP # 2 Service Request (UP # 2)
  • UP # 2 Service Request
  • the AMF is requested.
  • PDU2 idle timer threshold for a new PDU session
  • 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).
  • the UE acquires information on the idle timer threshold for PDU2 thereby.
  • 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).
  • 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).
  • PDU2 a new PDU session
  • FIG. 17 shows a PDU session release process in the fifth embodiment.
  • a process of releasing one PDU session (PDU2) in a situation where a plurality of PDU sessions (PDU1, PDU2) are set is shown.
  • 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.
  • 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.
  • PDU1 PDU1
  • PDU1 PDU1
  • 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.
  • 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.
  • the new PDU session (PDU2) becomes the UE and the second UP (UP # 2). Processes set between and are shown.
  • 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.
  • an idle timer threshold value for a new PDU session (PDU2) is calculated (step 2 in FIG. 19).
  • 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).
  • 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).
  • FIG. 20 shows a PDU session release process in the sixth embodiment.
  • a process of releasing one PDU session (PDU2) in a situation where a plurality of PDU sessions (PDU1, PDU2) are set is shown.
  • 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.
  • 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).
  • 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).
  • PDU2 is released between the UE and the RAN and between the RAN and the UP # 2.
  • PDU1 PDU1
  • PDU1 PDU1
  • 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.
  • an SMF calculates an idle timer threshold for a new PDU session, instead of AMF, for a so-called next-generation network.
  • 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.
  • PDU1 a PDU session
  • PDU2 a new PDU session
  • 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).
  • 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).
  • 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).
  • 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.
  • 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).
  • 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).
  • a new PDU session (PDU2) is established between the UE and the RAN and between the RAN and the UP # 2.
  • 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.
  • a device here, RAN
  • notification of information is not limited to the aspect / embodiment described in this specification, and may be performed by other methods.
  • 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.
  • 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.
  • LTE Long Term Evolution
  • LTE-A Long Term Evolution-Advanced
  • SUPER 3G IMT-Advanced
  • 4G 5G
  • FRA Full Radio Access
  • W-CDMA Wideband
  • GSM registered trademark
  • CDMA2000 Code Division Multiple Access 2000
  • UMB User 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.
  • 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).
  • notification of predetermined information is not limited to explicitly performed, but is performed implicitly (for example, notification of the predetermined information is not performed). Also good.
  • software, instructions, etc. may be transmitted / received via a transmission medium.
  • 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.
  • 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.
  • DSL digital subscriber line
  • wireless technology such as infrared, wireless and microwave.
  • system and “network” used in this specification are used interchangeably.
  • 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.
  • the radio resource may be indicated by an index.
  • 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 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.
  • 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.
  • 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”.
  • 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”.
  • 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.”
  • 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.

Abstract

Dans le système de communication de l'invention où une pluralité de porteuses est établie entre un UE et une ou plusieurs SGW par l'intermédiaire d'un eNB, l'eNB mesure un temps mort pour chacune des porteuses, et détermine, pour chacune des porteuses, si le temps mort mesuré a atteint ou non un seuil de temporisateur de temps mort défini à l'avance pour chaque porteuse de la pluralité de porteuses (étape 1). Lors de la détermination, pour l'une des porteuses, que le temporisateur de temps mort a atteint le seuil de temporisateur de temps mort (étape 2), l'eNB demande à une MME de libérer ladite porteuse (étape 4), et la MME exécute un processus de libération de ladite porteuse conformément à la demande provenant de l'eNB (étape 5, etc.).
PCT/JP2017/033880 2016-09-30 2017-09-20 Procédé de commande de communication et système de communication WO2018061924A1 (fr)

Applications Claiming Priority (6)

Application Number Priority Date Filing Date Title
JP2016-193505 2016-09-30
JP2016193505 2016-09-30
JP2017019782 2017-02-06
JP2017-019782 2017-02-06
JP2017-046273 2017-03-10
JP2017046273 2017-03-10

Publications (1)

Publication Number Publication Date
WO2018061924A1 true WO2018061924A1 (fr) 2018-04-05

Family

ID=61759742

Family Applications (1)

Application Number Title Priority Date Filing Date
PCT/JP2017/033880 WO2018061924A1 (fr) 2016-09-30 2017-09-20 Procédé de commande de communication et système de communication

Country Status (1)

Country Link
WO (1) WO2018061924A1 (fr)

Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110176407A1 (en) * 2008-06-09 2011-07-21 Telefonaktiebolaget Lm Ericsson (Publ) System and method of releasing resources in a telecommunication network
JP2012175575A (ja) * 2011-02-23 2012-09-10 Ntt Docomo Inc 通信サービス提供システム、通信サービス制御ノード、移動通信端末装置、通信サービス提供方法

Patent Citations (2)

* Cited by examiner, † Cited by third party
Publication number Priority date Publication date Assignee Title
US20110176407A1 (en) * 2008-06-09 2011-07-21 Telefonaktiebolaget Lm Ericsson (Publ) System and method of releasing resources in a telecommunication network
JP2012175575A (ja) * 2011-02-23 2012-09-10 Ntt Docomo Inc 通信サービス提供システム、通信サービス制御ノード、移動通信端末装置、通信サービス提供方法

Similar Documents

Publication Publication Date Title
WO2018232570A1 (fr) Procédés d'enregistrement et d'établissement de session, terminal, et entité amf
JP2013529039A (ja) ハンドオーバ方法、通信デバイス及び通信システム
TW202040978A (zh) 處理流關聯丟失錯誤的方法及裝置
CN110603828B (zh) 网络装置和无线通信方法
JPWO2019077801A1 (ja) 通信システム、通信制御装置、および通信方法
WO2019192445A1 (fr) Procédé et dispositif de création et de jonction d'un groupe de multidiffusion
WO2019223702A1 (fr) Procédé, appareil, et système de gestion de session pdu
JP2018056857A (ja) ユーザ装置、基地局及びコアネットワーク
WO2018030545A1 (fr) Réseau central et station de base
JP6898937B2 (ja) 通信制御方法および通信システム
JP7018884B2 (ja) 通信方法
WO2021022919A1 (fr) Procédé pour effectuer une commande d'accès sur un équipement d'utilisateur, système de réseau et dispositif associé
JP2021077995A (ja) 通信制御装置
WO2019159372A1 (fr) Procédé de transfert d'information et groupe de nœuds
WO2018061924A1 (fr) Procédé de commande de communication et système de communication
JP2018191148A (ja) 制御方法
JP2018170713A (ja) 通信端末
JP6967018B2 (ja) Ｒａｎ接続制御方法および基地局
WO2019193764A1 (fr) Dispositif de station de base et système de communication
JP7345565B2 (ja) 通信装置及び通信方法
JP2020194990A (ja) ノード群及びマイグレーション方法
JP2018191147A (ja) 制御方法
US20230164649A1 (en) Method and apparatus for providing access policy in wireless communication system
WO2018034078A1 (fr) Système de communication, serveur de traitement et procédé de commande d'établissement de support
JPWO2018003480A1 (ja) 通信制御装置、ユーザ装置及び通信制御方法

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

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: DE

122 Ep: pct application non-entry in european phase

Ref document number: 17855879

Country of ref document: EP

Kind code of ref document: A1

NENP Non-entry into the national phase

Ref country code: JP