WO2020217532A1 - Session management device, user plane device, and communication method - Google Patents

Abstract

A session management device is provided with: a reception unit that receives network slice related information that is transmitted from a user device; and a transmission unit that transmits the network slice related information to a user plane device that performs transmission and reception of user data.

Description

Session management device, user plane device, and communication method

The present invention relates to resource control in a communication system.

In 3GPP (3rd Generation Partnership Project), in order to realize further increase in system capacity, further increase in data transmission speed, further reduction in delay in wireless sections, etc., 5G or NR (New Radio) is used. Studies on a wireless communication system called (hereinafter, the wireless communication system is referred to as "5G" or "NR") are in progress. In 5G, various wireless technologies are being studied in order to satisfy the requirement that the delay of the wireless section be 1 ms or less while achieving a throughput of 10 Gbps or more.

In NR, 5GC (5GCoreNetwork) corresponding to EPC (EvolvedPacketCore), which is the core network in the LTE (LongTermEvolution) network architecture, and E-UTRAN, which is the RAN (RadioAccessNetwork) in the LTE network architecture. A network architecture including NG-RAN (Next Generation-Radio Access Network) corresponding to (Evolved Universal Terrestrial Radio Access Network) is being studied (for example, Non-Patent Document 1).

In 5GC, by using parameters such as S-NSSAI (Single-Network Slice Selection Assistance Information), it is possible to select a network slice suitable for the application used by the UE on the network side.

However, with the existing 5GC, it is not possible to control each network slice with respect to the UPF (user plane device), which is a network node responsible for the U plane function.

The present invention has been made in view of the above points, and an object of the present invention is to provide a technique capable of controlling each network slice of a user plane device.

According to the disclosed technology, a receiver that receives network slice-related information transmitted from the user device,
A session management device including a transmission unit that transmits the network slice-related information to a user plane device that transmits / receives user data is provided.

According to the disclosed technology, a technology that enables control for each network slice related to the user plane device is provided.

It is a figure for demonstrating the communication system in embodiment of this invention. It is a figure for demonstrating the sequence example between UPF50 and SMF40. It is a figure for demonstrating the sequence example between UPF50 and SMF40. It is a figure for demonstrating the sequence example between UPF50 and SMF40. It is a figure for demonstrating the sequence example between UPF50 and SMF40. It is a figure for demonstrating an example of a load status / congestion status notification. It is a figure which shows the procedure of establishing a PDU session. It is a figure which shows an example of the functional structure of SMF40 in embodiment of this invention. It is a figure which shows an example of the functional structure of UPF50 in embodiment of this invention. It is a figure which shows an example of the hardware composition of SMF40 or UPF50 in embodiment of this invention.

Hereinafter, embodiments of the present invention will be described with reference to the drawings. The embodiments described below are examples, and the embodiments to which the present invention is applied are not limited to the following embodiments.

In operating the wireless communication system according to the embodiment of the present invention, existing technology may be used as appropriate. However, the existing technology is, for example, existing LTE or existing 5G, but is not limited to existing LTE or existing 5G.

Further, in the following description, the node names, signal names, etc. described in the 5G standard (or LTE standard) are currently used, but the node names and signals having the same functions as these are used. The name etc. may be called by a name different from these.

(System configuration example)
FIG. 1 is a diagram for explaining a communication system according to an embodiment of the present invention. As shown in FIG. 1, a communication system is composed of a UE (which may be referred to as a user device 10) and a plurality of network nodes. Hereinafter, one network node corresponds to each function, but one network node may realize a plurality of functions, or a plurality of network nodes may realize one function. Further, the "connection" described below may be a logical connection or a physical connection. Further, in FIG. 1, reference numerals are attached to the network nodes appearing in the operation examples described later.

The NG-RAN (Next Generation-Radio Access Network) 30 is a network node having a wireless access function, and is connected to a UE 10, an AMF (Access and Mobility Management Function) 20, and an UPF (User plane function) 50. The AMF 20 is a network node having functions such as RAN interface termination, NAS (Non-Access Stratum) termination, registration management, connection management, reachability management, and mobility management.

The UPF50 is a network node having functions such as a PDU (Protocol Data Unit) session point to the outside that interconnects with a DN (Data Network), packet routing and forwarding, and QoS (Quality of Service) handling of a user plane, and is a user. Send and receive data. UPF50 and DN constitute a network slice. In the wireless communication network according to the embodiment of the present invention, a plurality of network slices are constructed.

In the example of FIG. 1, one UPF50 corresponds to one network slice as an example, but in the present embodiment, one UPF50 can operate a plurality of network slices.

The UPF50 may be called a user plane device. Further, the plurality of network slices operated by UPF50 are, for example, slices involved in communication between NG-RAN30 and UPF50 (for example, PSA (PDU Session Anchor) UPF).

Further, the UPF50 is physically, for example, one or a plurality of computers (servers, etc.), and the hardware resources (CPU, memory, hard disk, network interface, etc.) of the computers can be logically integrated / divided. Multiple resources can be regarded as a resource pool, and each resource can be used as a network slice in the resource pool. The operation of the network slice by the UPF50 means, for example, management of the association between the network slice and the resource, start / stop of the resource, monitoring of the operation status of the resource, and the like.

AMF20 includes UE10, NG-RAN30, SMF (Session Management function) 40, NSSF (Network Slice Selection Function), NEF (Network Exposure Function), NRF (Network Repository Function), AUSF (Authentication Server Function), PCF (Policy Control). It is connected to Function) and AF (Application Function). AMF, SMF, NSSF, NEF, NRF, AUSF, PCF, AF are network nodes that are interconnected via their respective service-based interfaces, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nausf, Npcf, Naf. is there.

The SMF40 is a network node having functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, and roaming function. The SMF 40 may be referred to as a session management device.

NEF is a network node that has the function of notifying other NFs (Network Functions) of capabilities and events. The NSSF is a network node having functions such as selecting a network slice to be connected by a UE, determining an allowed NSSAI (Network Slice Selection Assistance Information), determining an NSSAI to be set, and determining an AMF set to be connected by the UE. .. The PCF is a network node having a function of controlling the policy of the network. AF is a network node that has a function of controlling an application server.

(About issues)
As described above, the UPF 50 in this embodiment can operate a plurality of network slices. However, in the prior art, the SMF 40 cannot dynamically grasp the network slice operated by the UPF 50. Therefore, for example, even if a certain network slice operated by UPF50 temporarily fails, SMF40 cannot grasp it. Further, the SMF 40 cannot grasp the load status or the congestion status for each network slice in the UPF 50. As a result, it becomes difficult to control each network slice regarding UPF.

Further, in the prior art, in the procedure for establishing a PDU session executed to start transmission / reception of user data (PDU) between the UE 10 and the DN, the S-NSSAI (example of the slice identifier) notified from the UE 10 is used. Since the UPF50 is not notified, the UPF50 cannot control each network slice.

Hereinafter, techniques for solving the above problems will be described using Examples 1 to 3.

(Example 1)
For example, when the power of the UPF50 is turned on and the UPF50 is started up, the UPF50 executes a setup procedure for connecting to the SMF40 (to start up a link). Also, if necessary, the UPF50 and SMF40 perform an update (update) procedure for updating the link.

FIG. 2 is a diagram showing an example of the setup procedure. In S101, UPF50 transmits a PFCPAssociationSetupRequest to SMF40. The prior art PFCP Association Setup Request is described in Non-Patent Document 2. As a configuration not found in the prior art, the PFCPAssociationSetupRequest of the first embodiment includes information (referred to as network slice-related information) for identifying each of one or a plurality of network slices supported by the UPF50. The network slice-related information may be S-NSSAI (s), NSI-ID (s) (Network Slice Instance Identifier (s)), or S-NSSAI (s) and NSI-. It may be ID (s) or information other than these.

PFCP means Packet Forwarding Control Protocol. In addition, the PFCP Association Setup procedure is a procedure performed to establish a PFCP association between the SMF 40 and the UPF 50 so that the SMF 40 can use the resources of the UPF 50 (to establish the PFCP Sessions). ..

The PFCPAssociationSetupRequest sent in S101 may include information on the node ID of UPF50, information on functions supported by UPF50, information on available user planes, and the like, in addition to network slice-related information.

The SMF40 that received the PFCPAssociationSetupRequest in S101 stores information such as network slice-related information in a storage device such as a memory. In S102, the SMF 40 transmits a PFCP Association Setup Response to the UPF 50.

Although the example of FIG. 2 shows an example of transmitting a PFCP Association Setup Request from the UPF 50, a PFCP Association Setup Request may be transmitted from the SMF 40. In this case, the PFCPAssociationSetupResponse transmitted from the UPF50 includes network slice-related information that identifies one or more network slices supported by the UPF50.

The above-mentioned example is an example in which the PFCPAssociationSetupRequest or PFCPAssociationSetupResponse that is transmitted from the UPF50 to the SMF40 includes network slice-related information that identifies one or more network slices supported by the UPF50. Instead of such a method, the UPF50 sends the network slice-related information that identifies one or more network slices supported by the UPF50 to the SMF40 by including it in a message other than PFCPAssociationSetupRequest or PFCPAssociationSetupResponse. You may. In addition, the UPF 50 may send network slice-related information that identifies one or more network slices supported by the UPF 50 to the SMF 40 as a new message.

FIG. 3 is another example of the first embodiment and is a diagram showing an example of an update procedure. In S111, the UPF 50 transmits a PFCP Association Update Request to the SMF 40. The prior art PFCP Association Update Request is described in Non-Patent Document 2. As a configuration not found in the prior art, the PFCPAssociationUpdateRequest of the first embodiment includes network slice-related information that identifies each of the one or more network slices supported by the UPF50. The network slice-related information may be S-NSSAI (s), NSI-ID (s) (Network Slice Instance Identifier (s)), or S-NSSAI (s) and NSI-. It may be ID (s) or information other than these.

The PFCP Association Update procedure is a procedure performed to modify the PFCP association between the SMF 40 and the UPF 50. For example, this procedure may be performed if changes occur in the network slices supported by the UPF50.

The SMF40 that received the PFCPAssociationUpdateRequest in S111 stores information such as network slice-related information in a storage device such as a memory. In S112, the SMF 40 transmits a PFCP Association Update Response to the UPF 50.

Note that. The example of FIG. 3 shows an example of transmitting a PFCP Association Update Request from UPF 50, but a PFCP Association Update Request may be transmitted from SMF 40. In this case, the PFCPAssociationUpdateResponse transmitted from the UPF50 includes network slice-related information that identifies one or more network slices supported by the UPF50.

Since the SMF 40 can grasp the network slice operated by the UPF 50 by the technique of the first embodiment, for example, in the UPF selection at the time of establishing the PDU session, the UPF can be selected according to the network slice operated by each UPF. That is, it becomes possible to control each network slice with respect to UPF.

(Example 2)
Next, Example 2 will be described. It is assumed that the second embodiment is executed after the processing in the first embodiment is executed. However, Example 2 may be carried out independently of Example 1.

The UPF50 can notify the SMF40 of the load status of the resources of the UPF50 (which may be referred to as an operating status) by the Load Control Information described in Non-Patent Document 2. As a result, the SMF 40 can grasp the load status of each UPF, so that an appropriate UPF can be selected from among a plurality of UPFs. However, in the prior art, since the load status can be notified only for each node, the SMF 40 cannot grasp the load status for each network slice in the UPF 50.

Therefore, in the second embodiment, as shown in FIG. 4, in S201, the UPF50 transmits the Load Control Information of each of the one or a plurality of network slices supported by the UPF50 to the SMF40. Note that the Load Control Information here may be referred to as load information or load control information. The SMF 40 that has received the Load Control Information of each network slice stores the Load Control Information in a storage device such as a memory. Note that LoadControlInformation may be included in PFCPSessionEstablishmentResponse.

For example, the UPF50 may include the Load Control Information of each of the one or more network slices supported by the UPF50 in one message and transmit the load to the SMF40, and the UPF50 may include one or a plurality of network slices supported by the UPF50. Each Load Control Information may be sent as one message for each network slice.

Further, the LoadControlInformation (or the message carrying the LoadControlInformation) may include an identifier indicating which network slice it corresponds to. Further, the LoadControlInformation (or a message carrying the LoadControlInformation) may include a node ID indicating which UPF it corresponds to. However, the node ID may not be explicitly included, and the UPF may be identified by an IP address or the like.

The UPF50 may periodically transmit LoadControlInformation to the SMF40 for each network slice, or at a predetermined trigger (for example, when the load changes by a predetermined value or more from the load at the time of the previous transmission). You may send it.

FIG. 5 shows another example of Example 2. As shown in FIG. 5, in S211 the UPF50 transmits Overload Control Information for each of the one or more network slices supported by the UPF50 to the SMF40. Note that the Overload Control Information here may be referred to as congestion information, congestion control information, overload information, overload control information, and the like. Upon receiving the Overload Control Information for each network slice, the SMF 40 stores the Overload Control Information in a storage device such as a memory. Note that OverloadControlInformation may be included in PFCPSessionEstablishmentResponse.

Overload Control Information for a network slice is, for example, that the amount of traffic input to the network slice exceeds the amount of traffic that the network slice can handle appropriately, or the amount of traffic input to the network slice. However, it may be information indicating that the network slice is expected to exceed the amount of traffic that can be appropriately processed.

For example, the UPF50 may include the Overload Control Information of each of the one or more network slices supported by the UPF50 in one message and transmit it to the SMF40, and the UPF50 may include one or a plurality of network slices supported by the UPF50. Each Overload Control Information may be sent as one message for each network slice.

Further, the OverloadControlInformation (or a message carrying OverloadControlInformation) may include an identifier indicating which network slice it corresponds to. Further, the OverloadControlInformation (or a message carrying OverloadControlInformation) may include a node ID indicating which UPF it corresponds to. However, the node ID may not be explicitly included, and the UFP may be identified by an IP address or the like.

Note that the UPF 50 may periodically transmit Overload Control Information to the SMF 40 for each network slice, or may transmit it at a predetermined trigger (for example, when an overload state occurs).

FIG. 6 is a diagram showing a specific example of the second embodiment. In the example of FIG. 6, there are two UPFs, UPF50A and UPF50B, and each UPF operates a network slice 1, a network slice 2, and a network slice 3.

In this case, the UPF50A transmits the load information about the network slice 1, the load information about the network slice 2, and the load information about the network slice 3 in the UPF50A to the SMF40. The UPF50B transmits the load information about the network slice 1, the load information about the network slice 2, and the load information about the network slice 3 in the UPF50B to the SMF40.

Further, for example, when the UPF50A detects that the network slice 1 in the UPF50A has been congested, it transmits congestion information indicating that the network slice 1 has been congested to the SMF40.

According to the technique of the second embodiment, the SMF 40 can grasp the load status and the congestion status of each network slice operated by the UPF 50. Therefore, for example, in the UPF selection at the time of establishing the PDU session, the load status of each network slice operated by each UPF. And UPF selection can be performed according to the congestion situation. That is, it becomes possible to control each network slice with respect to UPF.

(Example 3)
Next, Example 3 will be described. Example 3 is an example of a PDU session establishment procedure. Example 3 is premised on the implementation of Example 1 and Example 2. However, this premise is an example, and Example 3 may be implemented regardless of either Example 1 or Example 2. Further, it may be assumed that the third embodiment is carried out only by the first embodiment.

FIG. 7 shows the procedure for establishing a PDU session in Example 3. FIG. 7 shows a part of the PDU session establishment procedure, and particularly shows a part focusing on transmission / reception of S-NSSAI.

In S301, the UE 10 transmits a 5 GMM (5GS Mobility Management) signal and a 5 GSM (5GS session management) signal, and the AMF 20 receives these signals. A ULNAS TRANSPORT message terminating at AMF20 is transmitted as a 5GMM signal, and the ULNAS TRANSPORT message includes S-NSSAI, DNN (Data Network Name), and the like. As a 5GSM signal, a PDU session establishment request terminated with SMF40 is transmitted.

In S302, AMF20 sends Nsmf_PDUSession_CreateSMContextRequest to SMF40. The Nsmf_PDUSession_CreateSMContextRequest includes n1SmMsg (= PDU session establishment request) transparently transferred from the UE 10 and S-NSSAI, DNN, etc. sent from the AMF 20.

In S303, when the SMF40 confirms that it supports the S-NSSAI transmitted from the UE 10, it selects a specific network slice to be used in the PDU session of the UE 10 based on the S-NSSAI, and the SMF40 selects the specific network slice to be used in the PDU session of the UE 10. Select an UPF with a network slice.

As an example, the configuration of FIG. 6 will be described as an example. For example, suppose the SMF 40 selects network slice 2 for the UE 10 based on the S-NSSAI transmitted from the UE 10.

According to Examples 1 and 2, the SMF 40 grasps each network slice of each UPF (UPF50A and UPF50B in the case of FIG. 6), and the load status and congestion status of each network slice.

Here, for example, assuming that the SMF40 finds that the load of the network slice 2 of the UPF50A is higher than the load of the network slice 2 of the UPF50B, the SMF40 sends and receives user data of the UE 10 (for traffic leveling). UPF50B is selected as the UPF for (using network slice 2).

Return to Fig. 7 and continue the explanation. In FIG. 7, it is assumed that the UPF 50 is the UPF selected by the SMF 40. In S304, the SMF 40 transmits a PFCP Session Establishment Request including network slice related information (here, S-NSSAI transmitted by the UE 50 as an example), a DNN, and the like to the UPF 50.

Note that the conventional PFCP Session Establishment Request described in Non-Patent Document 3 and the like does not include S-NSSAI, DNN, etc., but these are included in this embodiment. As a result, the UPF 50 can perform control after identifying the network slice desired by the UE 10.

Note that S-NSSAI is an example of network slice-related information included in the PFCP Session Establishment Request. The network slice-related information included in the PFCP Session Establishment Request may be NSI-ID. Further, the network slice-related information included in the PFCP Session Establishment Request may be an identifier different from both S-NSSAI and NSI-ID.

Further, instead of including the network slice-related information in the PFCPSessionEstablishmentRequest, the network slice-related information is included in an information element or message different from the PFCPSessionEstablishmentRequest, and the information element or message is changed from SMF40 to UPF50. It may be transmitted.

In S305, UPF50 sends PFCP Session Establishment Response to SMF40.

In S306, SMF40 transmits a Namf_Communication_N1N2MessageTransfer message to AMF20. Namf_Communication_N1N2MessageTransfer includes n1MessageContainer (= PDU session establishment accept, which includes S-NSSAI, DNN, etc.) that is transparently transferred to UE10, and n2InfoContainer (=) that is transparently transferred to NG-RAN30. PDU session resource setup request. This includes S-NSSAI but not DNN).

In S307, the AMF 20 transmits a PDU session establishment accept to the UE 10. This includes S-NSSAI, DNN and the like. In S308, the AMF 20 transmits a PDU session resource setup request to the NG-RAN 30. There is S-NSSAI in this, but there is no DNN.

After receiving the network slice related information (for example, S-NSSAI-A), the UPF50 transmits / receives user data of the UE 10 after establishing the PDU session, for example, using the network slice resource corresponding to the S-NSSAI-A. Do.

In the above example, in the UPF50, the network slice is controlled for each network slice-related information, but it may be controlled for each "network slice-related information + DNN". Further, for example, control for each "S-NSSAI + DNN" or control for each "NSI-ID + DNN" may be performed.

According to the technique of Example 3, the SMF40 and UPF50 can be controlled for each network slice.

(Device configuration)
Next, a functional configuration example of the session management device 40 corresponding to the SMF 40 and the user plane device 50 corresponding to the UPF 50 that executes the processes and operations described so far will be described. The session management device 40 and the user plane device 50 include a function of carrying out the above-described first to third embodiments. However, the session management device 40 and the user plane device 50 may each have only a part of the functions of options 1 to 3.

<Session management device 40>
FIG. 8 is a diagram showing an example of the functional configuration of the session management device 40. As shown in FIG. 8, the session management device 40 includes a transmission unit 410, a reception unit 420, a setting unit 430, and a control unit 440. The functional configuration shown in FIG. 8 is only an example. Any function classification and name of the functional unit may be used as long as the operation according to the embodiment of the present invention can be executed.

The transmission unit 410 includes a function of generating a signal to be transmitted and transmitting the signal to the network. The receiving unit 420 includes a function of receiving various signals and acquiring information of, for example, a higher layer from the received signals. The transmitter 410 and the receiver 420 may be referred to as a transmitter and a receiver, respectively.

The setting unit 430 stores the setting information in the storage device (storage unit) and reads it out from the storage device as needed. The content of the setting information is, for example, information on S-NSSAI that it supports.

The control unit 440 controls the session management device 40. The function unit related to signal transmission in the control unit 440 may be included in the transmission unit 410, and the function unit related to signal reception in the control unit 440 may be included in the reception unit 420.

<User plane device 50>
FIG. 9 is a diagram showing an example of the functional configuration of the user plane device 50. As shown in FIG. 9, the user plane device 50 includes a transmission unit 510, a reception unit 520, a setting unit 530, and a control unit 540. The functional configuration shown in FIG. 9 is only an example. Any function classification and name of the functional unit may be used as long as the operation according to the embodiment of the present invention can be executed.

The transmission unit 510 includes a function of generating a signal to be transmitted and transmitting the signal to the network. The receiving unit 520 includes a function of receiving various signals and acquiring information of, for example, a higher layer from the received signals. The transmitter 510 and the receiver 520 may be referred to as a transmitter and a receiver, respectively.

The setting unit 530 stores the setting information in the storage device (storage unit) and reads it out from the storage device as needed. The contents of the setting information are, for example, information for identifying the network slice operated by the user, information on resources corresponding to the network slice, and the like.

The control unit 540 executes, for example, the operation of the network slice. The function unit related to signal transmission in the control unit 540 may be included in the transmission unit 510, and the function unit related to signal reception in the control unit 540 may be included in the reception unit 520.

(Hardware configuration)
The block diagrams (FIGS. 8 and 9) used in the description of the above-described embodiment show blocks of functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Further, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized by using one device that is physically or logically connected, or directly or indirectly (for example, by two or more devices that are physically or logically separated). , Wired, wireless, etc.) and may be realized using these plurality of devices. The functional block may be realized by combining the software with the one device or the plurality of devices.

Functions include judgment, decision, judgment, calculation, calculation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, solution, selection, selection, establishment, comparison, assumption, expectation, and assumption. There are broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, assigning, etc., but only these. I can't. For example, a functional block (constituent unit) that functions transmission is called a transmitting unit or a transmitter. As described above, the method of realizing each of them is not particularly limited.

For example, the session management device 40, the user plane device 50, and the like in one embodiment of the present disclosure may function as a computer that performs the processing of the present disclosure. FIG. 10 is a diagram showing an example of the hardware configuration of the session management device 40 and the user plane device 50 according to the embodiment of the present disclosure. The above-mentioned session management device 40 and user plane device 50 are physically as computer devices including a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, a bus 1007, and the like. It may be configured. The session management device 40 and the user plane device 50 may be virtual machines, respectively. Further, the resource of the network slice operated by the user plane device 50 may be a virtual machine.

In the following explanation, the word "device" can be read as a circuit, device, unit, etc. The hardware configuration of the session management device 40 and the user plane device 50 may be configured to include one or more of the devices shown in the figure, or may be configured not to include some of the devices.

Each function of the session management device 40 and the user plane device 50 is performed by the processor 1001 performing calculations by loading predetermined software (programs) on hardware such as the processor 1001 and the storage device 1002, and communication by the communication device 1004. It is realized by controlling at least one of reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

The processor 1001 operates, for example, an operating system to control the entire computer. The processor 1001 may be composed of a central processing unit (CPU: Central Processing Unit) including an interface with a peripheral device, a control device, an arithmetic unit, a register, and the like. For example, the above-mentioned control unit 440, control unit 540, and the like may be realized by the processor 1001.

Further, the processor 1001 reads a program (program code), a software module, data, or the like from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, 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-described embodiment is used. For example, the control unit 440 of the session management device 40 shown in FIG. 8 may be realized by a control program stored in the storage device 1002 and operated by the processor 1001. Further, for example, the control unit 540 of the user plane device 50 shown in FIG. 9 may be realized by a control program stored in the storage device 1002 and operated by the processor 1001. Although it has been described that the various processes described above are executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. Processor 1001 may be implemented by one or more chips. The program may be transmitted from the network via a telecommunication line.

The storage device 1002 is a computer-readable recording medium, for example, by at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EPROM (Electrically Erasable Programmable ROM), RAM (Random Access Memory), and the like. It may be configured. The storage device 1002 may be referred to as a register, a cache, a main memory (main storage device), or the like. The storage device 1002 can store a program (program code), a software module, or the like that can be executed to implement the communication method according to the embodiment of the present disclosure.

The auxiliary storage device 1003 is a computer-readable recording medium, and is, for example, 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, Blu). -It may be composed of at least one of a ray (registered trademark) disk), a smart card, a flash memory (for example, a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, and the like. The storage medium described above may be, for example, a database, server or other suitable medium containing at least one of the storage device 1002 and the auxiliary storage device 1003.

The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, or the like. The communication device 1004 includes, for example, a high frequency switch, a duplexer, a filter, a frequency synthesizer, and the like in order to realize at least one of frequency division duplex (FDD: Frequency Division Duplex) and time division duplex (TDD: Time Division Duplex). It may be composed of. For example, the transmission / reception antenna, the amplifier unit, the transmission / reception unit, the transmission line interface, and the like may be realized by the communication device 1004. The transmission / reception unit may be physically or logically separated from each other in the transmission unit and the reception unit.

The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives an input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, etc.) that outputs to the outside. The input device 1005 and the output device 1006 may have an integrated configuration (for example, a touch panel).

Further, each device such as the processor 1001 and the storage device 1002 is connected by a bus 1007 for communicating information. The bus 1007 may be configured by using a single bus, or may be configured by using a different bus for each device.

The session management device 40 and the user plane device 50 include a microprocessor, a digital signal processor (DSP: Digital Signal Processor), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), and the like. It may be configured to include the hardware of, and a part or all of each functional block may be realized by the hardware. For example, processor 1001 may be implemented using at least one of these hardware.

(Summary of embodiments)
The present embodiment provides at least the session management device, the user plane device, and the communication method shown in the following items 1 to 6.
(Section 1)
A receiver that receives network slice-related information transmitted from the user device,
A session management device including a transmission unit that transmits the network slice-related information to a user plane device that transmits / receives user data.
(Section 2)
The session management device according to item 1, wherein the network slice-related information is S-NSSAI or NSI-ID.
(Section 3)
The session management device according to item 1 or 2, wherein the transmission unit transmits a session establishment request including the network slice related information to the user plane device.
(Section 4)
A control unit that operates one or more network slices,
A user plane device including a transmission unit that transmits network slice-related information for each of the one or more network slices to a session management device.
(Section 5)
A control unit that operates one or more network slices,
A user plane device including a transmitter that transmits load information or congestion information for each of the one or more network slices to a session management device.
(Section 6)
Steps to receive network slice related information sent from the user device,
A communication method executed by a session management device, comprising a step of transmitting the network slice-related information to a user plane device that transmits / receives user data.

A technique that enables control of each network slice of a user plane device by any of the configurations described in the first, second, third, fourth, fifth, and sixth paragraphs. Is provided.

(Supplement to the embodiment)
Although the embodiments of the present invention have been described above, the disclosed inventions are not limited to such embodiments, and those skilled in the art can understand various modifications, modifications, alternatives, substitutions, and the like. There will be. Although explanations have been given using specific numerical examples in order to promote understanding of the invention, these numerical values are merely examples and any appropriate value may be used unless otherwise specified. The classification of items in the above description is not essential to the present invention, and the items described in two or more items may be used in combination as necessary, and the items described in one item may be used in another item. It may be applied (as long as there is no contradiction) to the matters described in. The boundary of the functional unit or the processing unit in the functional block diagram does not always correspond to the boundary of the physical component. The operation of the plurality of functional units may be physically performed by one component, or the operation of one functional unit may be physically performed by a plurality of components. With respect to the processing procedure described in the embodiment, the order of processing may be changed as long as there is no contradiction. For convenience of processing description, the session management device 40 and the user plane device 50 have been described using functional block diagrams, but such devices may be implemented in hardware, software, or a combination thereof. The software operated by the processor of the session management device 40 according to the embodiment of the present invention and the software operated by the processor of the user plane device 50 according to the embodiment of the present invention are a random access memory (RAM), a flash memory, respectively. It may be stored in read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server or any other suitable storage medium.

Further, the notification of information is not limited to the mode / embodiment described in the present disclosure, and may be performed by using another method. For example, information notification includes physical layer signaling (for example, DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (for example, RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, etc. Broadcast information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination thereof may be used. RRC signaling may be referred to as an RRC message, for example, RRC. It may be a connection setup (RRCConnectionSetup) message, an RRC connection reconfiguration (RRCConnectionReconfiguration) message, or the like.

Each aspect / embodiment described in the present disclosure includes LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), and 5G (5th generation mobile communication). system), FRA (Future Radio Access), NR (new Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)) )), LTE 802.16 (WiMAX®), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth®, and other systems that utilize suitable systems and have been extended based on these. It may be applied to at least one of the next generation systems. Further, a plurality of systems may be applied in combination (for example, a combination of at least one of LTE and LTE-A and 5G).

The order of the processing procedures, sequences, flowcharts, etc. of each aspect / embodiment described in the present specification may be changed as long as there is no contradiction. For example, the methods described in the present disclosure present elements of various steps using exemplary order, and are not limited to the particular order presented.

In some cases, the specific operation performed by the session management device 40 or the user plane device 50 in the present specification may be performed by another node (upper node).

The information, signals, etc. described in the present disclosure 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 and the like may be saved in a specific location (for example, memory), or may be managed using a management table. Input / output information and the like can be overwritten, updated, or added. The output information and the like may be deleted. The input information or the like may be transmitted to another device.

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

Software is an instruction, instruction set, code, code segment, program code, program, subprogram, software module, whether called software, firmware, middleware, microcode, hardware description language, or another name. , Applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc. should be broadly interpreted to mean.

In addition, software, instructions, information, etc. may be transmitted and received via a transmission medium. For example, a website that uses at least one of wired technology (coaxial cable, fiber optic cable, twist pair, digital subscriber line (DSL: Digital Subscriber Line), etc.) and wireless technology (infrared, microwave, etc.) When transmitted from a server, or other remote source, at least one of these wired and wireless technologies is included within the definition of transmission medium.

The information, signals, etc. described in this disclosure may be represented using any of a variety of different techniques. For example, data, instructions, commands, information, signals, bits, symbols, chips, etc. that may be referred to throughout the above description may be voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any of these. It may be represented by a combination of.

Note that the terms explained in the present disclosure and the terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Also, the signal may be a message. Further, the component carrier (CC: Component Carrier) may be referred to as a carrier frequency, a cell, a frequency carrier, or the like.

The terms "system" and "network" used in this disclosure are used interchangeably.

In addition, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, relative values from predetermined values, or using other corresponding information. It may be represented. For example, the radio resource may be one indicated by an index.

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

In this disclosure, "base station (BS: Base Station)", "wireless base station", "base station device", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB" (GNB) ”,“ access point ”,“ transmission point (transmission point) ”,“ reception point ”,“ transmission / reception point (transmission / reception point) ”,“ cell ”,“ sector ”, Terms such as "cell group," "carrier," and "component carrier" can be used interchangeably. Base stations are sometimes referred to by terms such as macrocells, small cells, femtocells, and picocells.

The base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the entire coverage area of the base station can be divided into multiple smaller areas, each smaller area being a base station subsystem (eg, a small indoor base station (RRH:)). Communication services can also be provided by (Remote Radio Head). The term "cell" or "sector" is a part or all of the coverage area of at least one of the base station and the base station subsystem that provides the communication service in this coverage. Point to.

In the present disclosure, terms such as "mobile station (MS: Mobile Station)", "user terminal", "user device (UE: User Equipment)", and "terminal" may be used interchangeably. ..

Mobile stations can be subscriber stations, mobile units, subscriber units, wireless units, remote units, mobile devices, wireless devices, wireless communication devices, remote devices, mobile subscriber stations, access terminals, mobile terminals, wireless, depending on the trader. It may also be referred to as a terminal, remote terminal, handset, user agent, mobile client, client, or some other suitable term.

At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, or the like. At least one of the base station and the mobile station may be a device mounted on the mobile body, the mobile body itself, or the like. The moving body may be a vehicle (eg, car, airplane, etc.), an unmanned moving body (eg, drone, self-driving car, etc.), or a robot (manned or unmanned). ) May be. It should be noted that at least one of the base station and the mobile station includes a device that does not necessarily move during communication operation. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

The terms "determining" and "determining" used in this disclosure may include a wide variety of actions. "Judgment" and "decision" are, for example, judgment (judging), calculation (calculating), calculation (computing), processing (processing), derivation (deriving), investigation (investigating), search (looking up, search, inquiry). It may include (eg, searching in a table, database or another data structure), ascertaining as "judgment" or "decision". Also, "judgment" and "decision" are receiving (for example, receiving information), transmitting (for example, transmitting information), input (input), output (output), and access. (Accessing) (for example, accessing data in memory) may be regarded as "judgment" or "decision". In addition, "judgment" and "decision" mean that "resolving", "selecting", "choosing", "establishing", "comparing", etc. are regarded as "judgment" and "decision". Can include. That is, "judgment" and "decision" may include considering some action as "judgment" and "decision". Further, "judgment (decision)" may be read as "assuming", "expecting", "considering" and the like.

The terms "connected", "coupled", or any variation thereof, mean any direct or indirect connection or connection between two or more elements, and each other. It can include the presence of one or more intermediate elements between two "connected" or "combined" elements. The connection or connection between the elements may be physical, logical, or a combination thereof. For example, "connection" may be read as "access". As used in the present disclosure, the two elements use at least one of one or more wires, cables and printed electrical connections, and, as some non-limiting and non-comprehensive examples, the radio frequency domain. Can be considered to be "connected" or "coupled" to each other using electromagnetic energies having wavelengths in the microwave and light (both visible and invisible) regions.

The reference signal can also be abbreviated as RS (Reference Signal), and may be called a pilot (Pilot) depending on the applicable standard.

The phrase "based on" as used in this disclosure does not mean "based on" unless otherwise stated. In other words, the statement "based on" means both "based only" and "at least based on".

Any reference to elements using designations such as "first", "second", etc. as used in this disclosure does not generally limit the quantity or order of those elements. These designations can be used in the present disclosure as a convenient way to distinguish between two or more elements. Thus, references to the first and second elements do not mean that only two elements can be adopted, or that the first element must somehow precede the second element.

The "means" in the configuration of each of the above devices may be replaced with "part", "circuit", "device" and the like.

When "include", "including" and variations thereof are used in the present disclosure, these terms are as comprehensive as the term "comprising". Is intended. Furthermore, the term "or" used in the present disclosure is intended not to be an exclusive OR.

The wireless frame may be composed of one or more frames in the time domain. Each one or more frames in the time domain may be referred to as a subframe. Subframes may further consist of one or more slots in the time domain. The subframe may have a fixed time length (eg, 1 ms) that is independent of numerology.

The numerology may be a communication parameter that applies to at least one of the transmission and reception of a signal or channel. Numerology includes, for example, subcarrier spacing (SCS: SubCarrier Spacing), bandwidth, symbol length, cyclic prefix length, transmission time interval (TTI: Transmission Time Interval), number of symbols per TTI, wireless frame configuration, transmitter / receiver. At least one of a specific filtering process performed in the frequency domain, a specific windowing process performed by the transmitter / receiver in the time domain, and the like may be indicated.

The slot may be composed of one or more symbols in the time domain (OFDM (Orthogonal Frequency Division Multiplexing) symbol, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbol, etc.). Slots may be time units based on new melody.

The slot may include a plurality of mini slots. Each minislot may consist of one or more symbols in the time domain. Further, the mini slot may be called a sub slot. A minislot may consist of a smaller number of symbols than the slot. A PDSCH (or PUSCH) transmitted in time units larger than the minislot may be referred to as a PDSCH (or PUSCH) mapping type A. The PDSCH (or PUSCH) transmitted using the minislot may be referred to as PDSCH (or PUSCH) mapping type B.

The wireless frame, subframe, slot, minislot and symbol all represent the time unit when transmitting a signal. The radio frame, subframe, slot, minislot and symbol may have different names corresponding to each.

For example, one subframe may be called a transmission time interval (TTI), a plurality of consecutive subframes may be called TTI, and one slot or one minislot may be called TTI. You may. That is, at least one of the subframe and TTI may be a subframe (1 ms) in existing LTE, a period shorter than 1 ms (eg, 1-13 symbols), or a period longer than 1 ms. It may be. The unit representing TTI may be called a slot, a mini slot, or the like instead of a subframe.

Here, TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in the LTE system, the base station schedules each user plane device 50 to allocate radio resources (frequency bandwidth that can be used in each user plane device 50, transmission power, etc.) in TTI units. .. The definition of TTI is not limited to this.

The TTI may be a transmission time unit such as a channel-encoded data packet (transport block), a code block, or a code word, or may be a processing unit such as scheduling or link adaptation. When a TTI is given, the time interval (for example, the number of symbols) to which the transport block, code block, code word, etc. are actually mapped may be shorter than the TTI.

When one slot or one mini slot is called TTI, one or more TTIs (that is, one or more slots or one or more mini slots) may be the minimum time unit for scheduling. Further, the number of slots (number of mini-slots) constituting the minimum time unit of the scheduling may be controlled.

A TTI having a time length of 1 ms may be referred to as a normal TTI (TTI in LTE Rel. 8-12), a normal TTI, a long TTI, a normal subframe, a normal subframe, a long subframe, a slot, or the like. TTIs shorter than normal TTIs may be referred to as shortened TTIs, short TTIs, partial TTIs (partial or fractional TTIs), shortened subframes, short subframes, minislots, subslots, slots, and the like.

The long TTI (for example, normal TTI, subframe, etc.) may be read as a TTI having a time length of more than 1 ms, and the short TTI (for example, shortened TTI, etc.) is less than the TTI length of the long TTI and 1 ms. It may be read as a TTI having the above TTI length.

The resource block (RB) is a resource allocation unit in the time domain and the frequency domain, and may include one or a plurality of continuous subcarriers in the frequency domain. The number of subcarriers contained in the RB may be the same regardless of the numerology, and may be, for example, 12. The number of subcarriers contained in the RB may be determined based on numerology.

Further, the time domain of RB may include one or more symbols, and may have a length of 1 slot, 1 mini slot, 1 subframe, or 1 TTI. Each 1TTI, 1 subframe, etc. may be composed of one or a plurality of resource blocks.

In addition, one or more RBs include a physical resource block (PRB: Physical RB), a sub-carrier group (SCG: Sub-Carrier Group), a resource element group (REG: Resource Element Group), a PRB pair, an RB pair, and the like. May be called.

Further, the resource block may be composed of one or a plurality of resource elements (RE: Resource Element). For example, 1RE may be a radio resource area of 1 subcarrier and 1 symbol.

Bandwidth part (BWP: Bandwidth Part) (which may also be called partial bandwidth) may represent a subset of consecutive common resource blocks (RBs) for a certain neurology in a carrier. Here, the common RB may be specified by the index of the RB with respect to the common reference point of the carrier. PRBs may be defined in a BWP and numbered within that BWP.

The BWP may include a BWP for UL (UL BWP) and a BWP for DL (DL BWP). One or more BWPs may be set in one carrier for the UE.

At least one of the configured BWPs may be active, and the UE may not expect to send or receive a given signal / channel outside the active BWP. In addition, "cell", "carrier" and the like in this disclosure may be read as "BWP".

The above-mentioned structures such as wireless frames, subframes, slots, mini slots and symbols are merely examples. For example, the number of subframes contained in a wireless frame, the number of slots per subframe or wireless frame, the number of minislots contained within a slot, the number of symbols and RBs contained in a slot or minislot, included in the RB. The number of subcarriers, the number of symbols in the TTI, the symbol length, the cyclic prefix (CP: Cyclic Prefix) length, and other configurations can be changed in various ways.

In the present disclosure, if articles are added by translation, for example a, an and the in English, the disclosure may include that the nouns following these articles are in the plural.

In the present disclosure, the term "A and B are different" may mean "A and B are different from each other". The term may mean that "A and B are different from C". Terms such as "separate" and "combined" may be interpreted in the same way as "different".

Each aspect / embodiment described in the present disclosure may be used alone, in combination, or switched with execution. Further, the notification of predetermined information (for example, the notification of "being X") is not limited to the explicit one, but is performed implicitly (for example, the notification of the predetermined information is not performed). May be good.

Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure may be implemented as an amendment or modification without departing from the purpose and scope of the present disclosure, which is determined by the description of the scope of claims. Therefore, the description of this disclosure is for purposes of illustration only and does not have any restrictive meaning to this disclosure.

40 Session management device 410 Transmission unit 420 Reception unit 430 Setting unit 440 Control unit 50 User plane device 510 Transmission unit 520 Reception unit 530 Setting unit 540 Control unit 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device

Claims (6)

1. A receiver that receives network slice-related information transmitted from the user device,
   A session management device including a transmission unit that transmits the network slice-related information to a user plane device that transmits / receives user data.
2. The session management device according to claim 1, wherein the network slice-related information is S-NSSAI or NSI-ID.
3. The session management device according to claim 1 or 2, wherein the transmission unit transmits a session establishment request including the network slice-related information to the user plane device.
4. A control unit that operates one or more network slices,
   A user plane device including a transmission unit that transmits network slice-related information for each of the one or more network slices to a session management device.
5. A control unit that operates one or more network slices,
   A user plane device including a transmitter that transmits load information or congestion information for each of the one or more network slices to a session management device.
6. Steps to receive network slice related information sent from the user device,
   A communication method executed by a session management device, comprising a step of transmitting the network slice-related information to a user plane device that transmits / receives user data.
   

Images