阅读说明：本技术 网络节点 (Network node ) 是由 胜间田优树 巳之口淳 玛拉·瑞蒂·萨玛 R·圭尔佐尼 萨里库尔·塔克尔斯里 于 2018-09-21 设计创作，主要内容包括：网络节点具有：控制部,其决定UPF(User Plane Function)的重新配置的执行；以及发送部,其将包含PDU(Protocol Data Unit)会话ID以及与重新配置后的UPF有关的SMF(Session Management Function)的地址在内的重新配置的指示,经由所述SMF或者直接发送给AMF(Access and Mobility Management)。(The network node has: a control unit for determining execution of reconfiguration of UPF (user Plane function); and a transmission unit that transmits an instruction to reconfigure a session ID including a pdu (protocol Data unit) session ID and an address of an SMF (session Management function) associated with the reconfigured UPF, to the amf (access and Mobility Management) via the SMF or directly.)

1. A network node, wherein the network node has:

a control unit which determines execution of reconfiguration of a UPF which is a user plane function; and

and a transmitting unit which transmits a reconfiguration instruction including a PDU session ID which is a protocol data unit session ID and an address of an SMF which is a session management function related to the reconfigured UPF, to the AMF which is an access and mobility management function, via the SMF or directly.

2. The network node of claim 1,

in a case where the indication of reconfiguration is sent to the AMF via the SMF, an address of the SMF is assigned by the SMF.

3. The network node of claim 1,

when there is already a PDU session related to the reconfigured UPF, the process of establishing a PDU session related to the reconfigured UPF is not performed during the execution of the reconfiguration instruction.

4. The network node of claim 1,

the network node has a receiving part that receives an indication of a reconfiguration of a UPF from an application function or a maintenance function,

the network node performs reconfiguration of the UPF according to the received reconfiguration indication.

5. The network node of claim 4,

when an indication of a reconfiguration of a UPF is received from the maintenance function, the PDU session related to the UPF before reconfiguration is cut off before the reconfiguration is completed in case of SSC mode 2, session and service continuity mode 2, and the PDU session related to the UPF before reconfiguration is cut off after the reconfiguration is completed in case of SSC mode 3.

Technical Field

The present invention relates to a network node in a wireless communication system.

Background

In 3GPP (3rd Generation Partnership Project), in order to increase the system capacity, increase the data transmission rate, and reduce the delay in a Radio zone, a Radio communication method called 5G or NR (New Radio interface) (hereinafter, this Radio communication method is referred to as "5G" or "NR") has been studied. In 5G, various radio technologies have been studied in order to satisfy a requirement condition that a throughput (throughput) of 10Gbps or more is realized and a delay between radio zones is 1ms or less.

In NR, a Network architecture including a 5GC (5G Core Network: 5G Core Network) corresponding to an EPC (Evolved Packet Core) as a Core Network in an LTE (Long Term Evolution) Network architecture and a NG-RAN (Next Generation Radio Access Network: Next Generation Radio Access Network) corresponding to an E-UTRAN (Evolved Universal Terrestrial Radio Access Network) as a RAN (Radio Access Network) in an LTE Network architecture (for example, non-patent document 1) is studied.

Documents of the prior art

Non-patent document

Non-patent document 1: 3GPP TS 23.501 V15.2.0(2018-06)

Disclosure of Invention

Problems to be solved by the invention

When performing reconfiguration of a PDU (Protocol Data Unit) Session, the timing of reconfiguring SMF (Session Management Function) and UPF (User Plane Function) is ambiguous, assuming multiple network architectures and triggers for reconfiguration.

The present invention has been made in view of the above circumstances, and has as its object to appropriately perform reconfiguration of a PDU session according to a network architecture and a trigger.

Means for solving the problems

According to the disclosed technique, there is provided a network node having: a control unit for determining execution of reconfiguration of UPF (User Plane Function); and a transmission Unit that transmits an instruction to reconfigure a Session ID including a PDU (Protocol Data Unit) Session ID and an address of an SMF (Session Management Function) associated with the UPF after reconfiguration, to an AMF (Access and Mobility Management) via the SMF or directly.

Effects of the invention

According to the disclosed technology, reconfiguration of a PDU session can be performed appropriately according to network architecture and triggers.

Drawings

Fig. 1 is a diagram for explaining an outline of a network architecture.

Fig. 2 is a diagram showing a configuration example (1) of the network.

Fig. 3 is a sequence diagram for explaining an example of PDU session reconfiguration.

Fig. 4 is a diagram showing a configuration example (2) of the network.

Fig. 5 is a diagram illustrating an example of PDU session reconfiguration in an embodiment of the present invention.

Fig. 6 is a timing diagram for explaining the triggering of PDU session reconfiguration in the embodiment of the present invention.

Fig. 7 is a diagram showing a configuration example (1) of a network in the embodiment of the present invention.

Fig. 8 is a diagram showing a configuration example (2) of a network in the embodiment of the present invention.

Fig. 9 is a timing diagram for explaining an example (1) of PDU session reconfiguration based on PCF/AF triggering in an embodiment of the present invention.

Fig. 10 is a sequence diagram for explaining an example (2) of PDU session reconfiguration based on PCF/AF triggering in an embodiment of the present invention.

Fig. 11 is a timing diagram for explaining an example (1) of PDU session reconfiguration based on O & M trigger in an embodiment of the present invention.

Fig. 12 is a sequence diagram for explaining an example (2) of PDU session reconfiguration based on O & M trigger in an embodiment of the present invention.

Fig. 13 is a sequence diagram for explaining example (3) of PDU session reconfiguration based on O & M trigger in the embodiment of the present invention.

Fig. 14 is a sequence diagram for explaining an example (4) of PDU session reconfiguration based on O & M trigger in an embodiment of the present invention.

Fig. 15 is a sequence diagram for explaining example (3) of PDU session reconfiguration based on PCF/AF triggering in an embodiment of the present invention.

Fig. 16 is a sequence diagram for explaining an example (4) of PDU session reconfiguration based on PCF/AF triggering in an embodiment of the present invention.

Fig. 17 is a sequence diagram for explaining an example (5) of PDU session reconfiguration based on O & M trigger in an embodiment of the present invention.

Fig. 18 is a diagram showing an example of a functional configuration of the network node 10 according to the embodiment of the present invention.

Fig. 19 is a diagram showing an example of a functional configuration of the user apparatus 20 according to the embodiment of the present invention.

Fig. 20 is a diagram showing an example of a hardware configuration of the network node 10 or the user equipment 20 according to the embodiment of the present invention.

Detailed Description

Embodiments of the present invention will be described below 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 embodiments described below.

The conventional technique can be suitably used when the wireless communication system according to the embodiment of the present invention is operated. However, the existing technology is, for example, but not limited to, existing LTE. In addition, unless otherwise specified, the term "LTE" used in the present specification has a broad meaning including LTE-Advanced and modes after LTE-Advanced (e.g., NR) or wireless LAN (Local Area Network).

In the embodiment of the present invention, the "configuration" radio parameter or the like may be a predetermined value (Pre-configuration), or may be a radio parameter notified from the network node 10 or the user equipment 20.

Fig. 1 is a diagram for explaining an outline of a network architecture. The Network shown in fig. 1 includes a Packet Core (Packet Core: Packet Core), an UPF (User Plane Function), and a UE (User Equipment) of an EPC (Evolved Packet Core: Evolved Packet Core), a 5GC (5G Core Network: 5G Core Network), and the like. The UPF is a Network node 10 having functions for external PDU (Protocol Data Unit) session points interconnected with DNs (Data networks), routing and forwarding (forwarding) of packets, qos (quality of service) processing of a user plane, and the like. As shown in fig. 1, UEs are respectively assigned IP addresses and establish a connection with a Packet Core (Packet Core) via UPF.

Here, for example, when the UPF is changed for the same UE and the same AP (Access Point) for any reason, all PDU sessions are disconnected before a new PDU Session is established in SSC (Session and Service Continuity) mode 2. On the other hand, in SSC mode 3, after a new PDU session is established, an old PDU session is cut off.

Fig. 2 is a diagram showing a configuration example (1) of the network. As shown in fig. 2, the network includes a UE as a user equipment 20 and a plurality of network nodes 10. In the following, 1 network node 10 corresponds to each function, but a plurality of functions may be implemented by 1 network node 10, or 1 function may be implemented by a plurality of network nodes 10. The "connection" described below may be a logical connection or a physical connection.

Ran (radio Access network) is a network node 10 with radio Access Function, and is connected to UE, AMF (Access and Mobility Management Function) and UPF (User Plane Function). The AMF is a network node 10 having functions such as registration management, connection management, reachability management, and mobility management, such as a terminal of a RAN interface and a terminal of NAS (Non-Access Stratum). The AMF is connected to the RAN and an SMF (Session Management Function).

The UPF is a network node 10 having functions for external pdu (protocol Data unit) session points interconnected with dn (Data network), routing and forwarding of packets, qos (quality of service) processing of a user plane, and the like. In the example shown in FIG. 2, DN has DC (Data Center: Data Center) #1and DC # 2. In addition, DC #1 includes application servers V2X-App #1a, and DC #2 includes application servers V2X-App # 1b.

The SMF is a network node 10 having functions such as session management, ip (internet Protocol) Address allocation and management of the UE, a DHCP (Dynamic Host Configuration Protocol) function, an ARP (Address Resolution Protocol) proxy, and a roaming function. The SMF is connected with UPF and PCF (Policy Control Function)/NEF (Network Exposure Function).

The NEF is a Network node 10 having a Function of notifying other NFs (Network Function) of capabilities and events. The PCF is a network node 10 having a function of performing policy control of the network. The PCF/NEF is connected to the SMF and AF (Application Function). The AF is a network node 10 having a function of controlling an application server. The AF is connected to DC #1and DC # 2.

In the network shown in fig. 2, an example in which the reconfiguration of the UPF is triggered by the AF is explained. Assume that the UE has established a PDU session of SSC mode 3 with the application server V2X-App #1a contained in DC # 1. Here, the AF decides to move the application server to V2X-App #1b in response to an arbitrary trigger such as maintenance of the application server. The AF requests reconnection of the PDU session of SSC mode 3 with the application server V2X-App #1b contained in DC # 2. The SMF reconfigures the PDU session of UPF #1 to the PDU session of UPF # 2.

Fig. 3 is a sequence diagram for explaining an example of PDU session reconfiguration. Fig. 3 is an example of a timing sequence for performing reconfiguration of a PDU session of SSC pattern 3. SMF #1 manages UPF #1, and SMF #2 manages UPF # 2. When a PDU session is established between the UE and UPF #1, SMF #1 decides that a reconfiguration of UPF and SMF is required. Next, SMF #1 notifies the AMF and the UE of the PDU session change. Next, a PDU session setup procedure of UPF #2 started by the UE is performed. After the PDU session is established between the UE and the UPF #2, the PDU session of the UPF #1 is released.

Fig. 4 is a diagram showing a configuration example (2) of a network in the embodiment of the present invention. An example is illustrated in which reconfiguration of UPF is triggered by SMF in the network shown in fig. 4. The DNN (Data Network Name: Data Network Name) contains the application server. Assume that the UE has established a PDU session in SSC mode 3 with the application server V2X-App #1a contained in the DNN. Here, the SMF determines to move the connection of the UE to the UPF #2 based on an arbitrary trigger such as load dispersion. The SMF reconfigures the PDU session of UPF #1 to the PDU session of UPF # 2. In the above example, the application server V2X-App #1a contained in the DNN is not changed.

As mentioned above, the SMF decides that a reconfiguration of the UPF needs to be made, which decision constitutes a trigger for the reconfiguration process of the UPF.

Fig. 5 is a diagram illustrating an example of PDU session reconfiguration in an embodiment of the present invention.

Case #1(Case #1) shown in fig. 5 is a PDU session switching of SSC pattern 3 between UPFs controlled by different SMFs. Case #2(Case #2) shown in fig. 5 is a PDU session handover of SSC pattern 3 between UPFs controlled by the same SMF. The solid arrows represent old PDU sessions and the dashed arrows represent new PDU sessions.

As in Case #1(Case #1), when 2 UPFs are switched by 2 SMFs, the SMF change is performed within the lifetime (lifetime) of the PDU session. On the other hand, as in Case #2(Case #2), when 2 UPFs are switched by 1 SMF, the change of the SMF may not be performed during the lifetime of the PDU session. Here, it is not clear how the handover of the PDU session is performed. For example, details of determining the timing of notification of AF, AMF, or SMF are not specified.

Fig. 6 is a timing diagram for explaining the triggering of PDU session reconfiguration in the embodiment of the present invention. PDU session reconfiguration envisages for example the following 3 triggers.

1) PCF and AF triggering

The AF indicates the reconfiguration of the UPF to the SMF via the PCF due to an arbitrary event on the application side. For example, Npcf _ SMPolicyControl _ UpdateNotify shown in fig. 6 is a message constituting a trigger.

2) O & M (Operation & Maintenance: operation and maintenance) triggers

In case UPF #1 is not available for maintenance reasons etc., the O & M indicates a reconfiguration of the UPF to the SMF. A message based on the O & M trigger (e.g., maintence notification, etc.) is input to the SMF.

3) AMF triggering

In Handover, Registration procedure, Mobility event notification timing, the SMF decides the reconfiguration of the UPF in SSC-3 according to a trigger from the AMF. For example, Nsmf _ pdusesion _ UpdateSMControl shown in fig. 6 is a message constituting a trigger.

By the trigger, the SMF determines that the reconfiguration of the UPF is required, the reconfiguration process from the UPF1 to the UPF2 is performed, and the UL/DL data transmission and reception between the UE and the UPF1 is switched to the UL/DL data transmission and reception between the UE and the UPF 2.

Fig. 7 is a diagram showing a configuration example (1) of a network in the embodiment of the present invention. As shown in fig. 7, the network according to the embodiment of the present invention is a network including 2 SMFs, i.e., SMF #1and SMF # 2. As in Case #1(Case #1) of fig. 5, is one of the architectures where different UPFs are controlled by different SMFs. The connection structure of AMF and SMF is a structure in which AMF is connected to SMF #2and SMF #2 is connected to SMF # 1. That is, AMF is not directly connected to SMF # 1. Hereinafter, the network shown in fig. 7 is referred to as architecture # 1.

Fig. 8 is a diagram showing a configuration example (2) of a network in the embodiment of the present invention. As shown in fig. 8, the network in the embodiment of the present invention is a network including 2 SMFs, SMF #1and SMF # 2. As shown in Case #1(Case #1) of fig. 5, is one of the architectures where different UPFs are controlled by different SMFs. The connection structure of AMF and SMF is a structure in which AMF is connected to SMF #1and SMF #1 is connected to SMF # 2. That is, AMF is not directly connected to SMF # 2. Hereinafter, the network shown in fig. 8 is referred to as architecture # 2.

Fig. 9 is a timing diagram for explaining an example (1) of PDU session reconfiguration based on PCF/AF triggering in an embodiment of the present invention. Regarding the user plane data in the start state shown in fig. 9, the state where the UPF #1 is an Anchor (Anchor) but the UPF #2 is also forwarding traffic, and a PDU session between the UE and the UPF #2 already exists. Fig. 9 is a sequence executed in the architecture #1 shown in fig. 7, and shows the operation of the SSC pattern 3. In addition, fig. 9 is a sequence executed in an architecture in which different UPFs are controlled by different SMFs, as in Case #1(Case #1) of fig. 5.

The AF notifies SMF #1 of the reconfiguration of the DN via the PCF (AF Request for relocation,2.Npcf _ SMPolicyControl _ UpdateNotify). Then, SMF #1 decides to move the Session to SMF #2and UPF #2(3. terminal that Session is connected to move to SMF #2and UPF # 2: decides that the Session needs to be moved to SMF #2and UPF # 2). Then, SMF #1 forwards (forwards) an indication for AMF to SMF #2 (4.Nsmf _ ServiceRelocation). The Nsmf ServiceRelocation contains UE ID, PDU session ID, reconfiguration indication. Next, the SMF #2 notifies the AMF of the forwarded instruction and the address of the SMF #2 as the movement destination (5.Namf _ Communication _ N1N2 MessageTransfer). Then, AMF sends switching indication of PDU Session to UE, receives establishment request of new PDU Session from UE (6.PDU Session Modification Command: PDU Session Modification Command, 7.PDU Session Est Req). Then, AMF Selects SMF #2 according to the indication from SMF #1 (8.AMF Selects the SMF #2due to indication by SMF #1and forwards the old & New PDU Sessions ID: AMF Selects SMF #2 according to the indication of SMF #1and forwards both the old PDU session ID and the New PDU session ID). Next, the AMF includes the PDU Session establishment request and the PDU release request in the PDU Session IDs of the old and new parties, and notifies SMF #2(9.PDU Session Req). Then, SMF #2selects UPF #2 as the new anchor (10.SMF #2selects the UPF #2due the indication, which at ends the UE will connect UPF # 2: SMF #2selects UPF #2 according to the indication, which knows that the UE has connected UPF # 2). Since the PDU session of the UPF #2 with the UE already exists, the timing of the PDU session establishment is not performed but reconfigured. Further, after the PDU session of the UPF #2 with the UE is reconfigured, the old PDU session is released.

Fig. 10 is a sequence diagram for explaining an example (2) of PDU session reconfiguration based on PCF/AF triggering in an embodiment of the present invention. Fig. 10 is a timing sequence executed in the architecture #2 shown in fig. 7, showing the action of the SSC pattern 3. In addition, fig. 10 is a sequence executed in an architecture in which different UPFs are controlled by different SMFs, as in Case #1(Case #1) of fig. 5.

The timing after "Forward (Forward) the instruction (4.Nsmf _ ServiceRelocation) for the AMF to the SMF # 2" from which the timing in fig. 9 is deleted is the timing shown in fig. 10. In the architecture #2, SMF #1and AMF have direct paths, so SMF #1 directly notifies AMF of a reconfiguration indication (5.Namf _ Communication _ N1N2MessageTransfer) including an address of SMF #2 without notifying AMF via SMF # 2.

Fig. 11 is a timing diagram for explaining an example (1) of PDU session reconfiguration based on O & M trigger in an embodiment of the present invention. Fig. 11 is a sequence executed in the architecture #1 shown in fig. 7, showing the action of the SSC pattern 2. In addition, fig. 11 is a sequence executed in an architecture in which different UPFs are controlled by different SMFs, as in Case #1(Case #1) of fig. 5.

The O & M notifies SMF #1 of maintenance of UPF #1 (1b.O & M Trigger for UPF #1 maintence notification: O & M triggers maintenance notification for UPF # 1). Then, SMF #1 decides to move the Session to SMF #2and UPF #2(1b. terminal that Session is connected to move to SMF #2and UPF # 2: decides that the Session needs to be moved to SMF #2and UPF # 2). Then SMF #1 forwards (forwards) an indication for AMF to SMF #2 (4.Nsmf _ ServiceRelease). The Nsmf _ ServiceRelease contains the UE ID, PDU session ID, release indication to select SMF #2 but not SMF # 1. Then, SMF #2 informs the AMF of the forwarded (forwarded) indication and the indication that SMF #1 is not selected (5.Namf _ Communication _ N1N2 MessageTransfer). Then, the PDU Session is released through SMF #1and the UE (3.PDU Session Release: PDU Session Release). Next, a new PDU Session establishment request is received from the UE (4.PDU Session Est Req). Next, the AMF Selects SMF #2 according to the indication from SMF #1 (5.AMF Selects the SMF #2due to indication by SMF # 1: AMF Selects SMF #2 based on the indication of SMF # 1). Next, the AMF notifies SMF #2 of a PDU Session establishment request (6.PDU Session Req). Next, a PDU Session is established between the UE and UPF #2 (PDU Session initiated with UPF # 2: PDU Session established with UPF # 2).

Fig. 12 is a sequence diagram for explaining an example (2) of PDU session reconfiguration based on O & M trigger in an embodiment of the present invention. Fig. 11 is a timing sequence executed in the architecture #2 shown in fig. 7, showing the action of the SSC pattern 2. In addition, fig. 12 is a sequence executed in an architecture in which different UPFs are controlled by different SMFs, as in Case #1(Case #1) of fig. 5.

The timing after deleting the timing "Forward (Forward) instruction for AMF (4.Nsmf _ ServiceRelease)" to SMF #2 in fig. 11 is the timing shown in fig. 12. In the architecture #2, SMF #1and AMF have direct paths, so SMF #1 directly notifies AMF of a reconfiguration indication including an address of SMF #2 without notifying AMF via SMF #2 (2.Namf _ Communication _ N1N2 MessageTransfer).

Fig. 13 is a sequence diagram for explaining example (3) of PDU session reconfiguration based on O & M trigger in the embodiment of the present invention. Fig. 13 is a sequence executed in the architecture #1 shown in fig. 7, showing the action of the SSC pattern 3. In addition, as shown in Case #1(Case #1) of fig. 5, fig. 13 is a sequence executed in an architecture in which different UPFs are controlled by different SMFs. The sequence shown in fig. 13 is executed mainly for the purpose of load distribution.

The O & M notifies SMF #1 of maintenance of UPF #1 (1b.O & M Trigger for UPF #1 maintence notification: O & M triggers maintenance notification for UPF # 1). Then, SMF #1 decides to move the Session to SMF #2and UPF #2(1b. terminal that Session is connected to move to SMF #2and UPF # 2: decides that the Session needs to be moved to SMF #2and UPF # 2). Then, SMF #1 forwards (forwards) an indication for AMF to SMF #2 (4.Nsmf _ ServiceRelocation). The Nsmf ServiceRelocation contains UE ID, PDU session ID, reconfiguration indication. Thereafter, step #5(5.Namf _ Communication _ N1N2MessageTransfer) to step #9(9.PDU Session Req) of FIG. 9 are performed.

Fig. 14 is a sequence diagram for explaining an example (4) of PDU session reconfiguration based on O & M trigger in an embodiment of the present invention. Fig. 14 is a timing sequence executed in the architecture #2 shown in fig. 7, showing the action of the SSC pattern 3. In addition, fig. 14 is a sequence executed in an architecture in which different UPFs are controlled by different SMFs, as in Case #1(Case #1) of fig. 5. The timing shown in fig. 14 is mainly performed for the purpose of load distribution.

The O & M notifies SMF #1 of maintenance of UPF #1 (1b.O & M Trigger for UPF #1 maintence notification: O & M triggers maintenance notification for UPF # 1). Then, SMF #1 decides to move the Session to SMF #2and UPF #2(1b. terminal that Session is connected to move to SMF #2and UPF # 2: decides that the Session needs to be moved to SMF #2and UPF # 2). Then, the SMF #1 notifies the AMF of a reconfiguration instruction including the address of the SMF #2(5. Namf _ Communication _ N1N2 MessageTransfer). Thereafter, step #6(6.PDU Session Modification Command: PDU Session Modification Command) to step #9(9.PDU Session Req) of FIG. 10 are performed.

Fig. 15 is a sequence diagram for explaining example (3) of PDU session reconfiguration based on PCF/AF triggering in an embodiment of the present invention. Fig. 15 is a sequence performed in an architecture in which different UPFs are controlled by the same SMF, as in Case #2(Case #2) of fig. 5, and reconfiguration of the UPFs with respect to the UE group is performed.

The AF decides to change the PDU session to a new DC or DNAI (DN Access Identifier: DN Access Identifier) in SSC mode 3 (Creation of the AF request: Creation of AF request). Subsequently, the AF notifies the NEF of the SSC mode (2.Nnef _ trafficinfiluence _ Update (e.g. SSC modes)). The reconfiguration of the UPF is performed in the notified SSC mode. Next, NEF and udr (unified Data reporting) update the information of the UE group (3a. updating the information) and respond to AF (3b. nnef _ trafficlnfluency _ update response). The UDR then indicates to the PCF a handover of the PDU session (4.Nudr _ DM _ Notify). The PCF then indicates to the SMF a switch of PDU session (5.Npcf _ SMPolicyControl _ UpdateNotify). The SMF then performs a reconfiguration of the UPF according to the timing shown in fig. 3 or fig. 6(6. UPF location of SSC 3PDU session: UPF reconfiguration of the PDU session of SSC 3).

Fig. 16 is a sequence diagram for explaining an example (4) of PDU session reconfiguration based on PCF/AF triggering in an embodiment of the present invention. Fig. 16 is a timing sequence performed in an architecture in which different UPFs are controlled by the same SMF, as in Case #2(Case #2) of fig. 5, and reconfiguration of the UPFs with respect to a single UE is performed.

In the case of a single UE, unlike the PDU session reconfiguration shown in fig. 15, the timing is not via UDR, NEF indicates directly to PCF the indication received from AF (1.NEF receivers Nnef _ Traf ficilnfluence _ Create/Update/Delete Request from AF NEF receives from AF the nff _ Traf ficilnfluence _ Create/Update/Delete Request) (4.Npcf _ PolicyAuthorization _ Create/Update/Delete Request: Npcf _ PolicyAuthorization _ Create/Update/Delete Request). In addition, a BSF (Binding Support Function) is an NF service having a Function of registering or deregistering a consumer of the NF service with a PCF.

Fig. 17 is a sequence diagram for explaining an example (5) of PDU session reconfiguration based on O & M trigger in an embodiment of the present invention. As in Case #2(Case #2) of fig. 5, fig. 17 is a timing sequence performed by an architecture in which different UPFs are controlled by the same SMF, the O & M for load control triggering reconfiguration of the UPF.

The UPF periodically notifies the SMF or O & M of Load information (1a. Load information (Load info),1b. Load information (Load info)). Then, the O & M indicates to the SMF that deletion or movement of the PDU Session of UPF #1 is performed in SSC mode 3 (2a. reduce/move SSC 3PDU Session from UPF # 1: PDU reduced/moved SSC 3 from UPF # 1). Then, the SMF decides to move the PDU session to UPF #2 in SSC mode 3 (2b. SMF determination: SMF determination). Thereafter, the PDU session is reconfigured for the UPF #2 in accordance with the timing of fig. 3 or fig. 6.

In addition, SSC pattern 3 is "make before break: make-before-break concept (concept). That is, when the session moves between IP anchors, the session of the UE is not interrupted during the lifetime of the PDU session. That is, it is possible to cope with a change in the IP address of the session.

With the above-described embodiments, the network node is able to perform reconfiguration of a PDU session between the UE and the UPF by deciding on reconfiguration by the SMF and sending an indication of the reconfiguration to the AMF.

That is, the reconfiguration of the PDU session can be performed appropriately according to the network architecture and the trigger.

(device construction)

Next, a functional configuration example of the network node 10 and the user equipment 20 that execute the above-described processing and operation will be described. The network node 10 and the user device 20 comprise functionality to implement the embodiments described above. However, the network node 10 and the user device 20 may each have only a part of the functionality of the embodiments.

< network node 10 >

Fig. 18 is a diagram showing an example of the functional configuration of the network node 10. As shown in fig. 18, the network node 10 includes a transmission unit 110, a reception unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in fig. 18 is merely an example. The names of the function division and the function unit may be arbitrary as long as the operation according to the embodiment of the present invention can be performed. Further, the network node 10 having a plurality of different functions in the system architecture may be constituted by a plurality of network nodes 10 separated for each function.

The transmitter 110 includes a function of generating a signal to be transmitted to the user device 20 or another network node 10 and transmitting the signal wirelessly. The receiving unit 120 includes a function of receiving various signals transmitted from the user apparatus 20 and acquiring, for example, higher-layer information from the received signals. The transmitter 110 has a function of transmitting NR-PSS, NR-SSS, NR-PBCH, DL/UL control signal, DL reference signal, and the like to the user equipment 20.

The setting unit 130 stores preset setting information and various kinds of setting information transmitted to the user device 20 in the storage device, and reads the setting information from the storage device as necessary. The content of the setting information is, for example, information related to session management.

As described in the embodiment, the control unit 140 performs processing related to the PDU session establishment processing between the user equipment 20 and the user plane. Further, the control unit 140 performs processing related to reconfiguration of the PDU session between the user equipment 20 and the user plane. The transmitting unit 110 may include a functional unit related to signal transmission in the control unit 140, and the receiving unit 120 may include a functional unit related to signal reception in the control unit 140.

< user device 20 >

Fig. 19 is a diagram showing an example of the functional configuration of the user apparatus 20. As shown in fig. 19, the user device 20 includes a transmission unit 210, a reception unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in fig. 19 is merely an example. The names of the function division and the function unit may be arbitrary as long as the operation according to the embodiment of the present invention can be performed.

The transmission unit 210 generates a transmission signal from the transmission data and wirelessly transmits the transmission signal. The receiving unit 220 receives various signals wirelessly and acquires a higher layer signal from the received physical layer signal. The reception unit 220 has a function of receiving an NR-PSS, an NR-SSS, an NR-PBCH, a DL/UL/SL control signal, a reference signal, or the like transmitted from the network node 10. For example, as D2D communication, the transmitter 210 transmits PSCCH (Physical downlink Control Channel), PSCCH (Physical downlink Shared Channel), PSDCH (Physical downlink Discovery Channel), PSBCH (Physical downlink Broadcast Channel), etc. to other user equipments 20, and the receiver 120 receives PSCCH, PSDCH, PSBCH, etc. from other user equipments 20. The transmission unit 210 and the reception unit 220 have a transmission/reception function of a wireless LAN or a wired LAN.

The setting unit 230 stores various setting information received by the receiving unit 220 from the network node 10 or the user device 20 in the storage device, and reads the setting information from the storage device as necessary. The setting unit 230 also stores preset setting information. The content of the setting information is, for example, information related to session management.

As described in the embodiment, the control section 240 performs processing related to PDU session establishment with the user plane. Further, the control section 240 performs processing related to the reconfiguration of the PDU session. The function section related to signal transmission in the control section 240 may be included in the transmission section 210, and the function section related to signal reception in the control section 240 may be included in the reception section 220.

(hardware construction)

The block diagrams (fig. 18 and 19) used in the description of the above embodiment show blocks in units of functions. These functional blocks (components) are realized by any combination of at least one of hardware and software. Note that means for realizing each functional block is not particularly limited. That is, each functional block may be implemented by one apparatus which is physically and/or logically combined, or may be implemented by a plurality of apparatuses which are directly and/or indirectly (for example, by wired and/or wireless) connected with two or more apparatuses which are physically and/or logically separated. The functional blocks may also be implemented by a combination of software and one or more of the above-described apparatuses.

The functions include, but are not limited to, judgment, decision, determination, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, establishment, comparison, assumption, expectation, view, broadcast (broadcasting), notification (notification), communication (communication), forwarding (forwarding), configuration (configuration), reconfiguration (reconfiguration), allocation (allocation, mapping), assignment (allocation), and the like. For example, a function block (a configuration unit) that functions transmission is called a transmission unit (transmitting unit) or a transmitter (transmitter). As described above, the implementation method is not particularly limited.

For example, the network node 10, the user equipment 20, and the like in one embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 20 is a diagram showing an example of hardware configurations of the network node 10 and the user equipment 20 according to an embodiment of the present disclosure. The network node 10 and the user device 20 may be configured as a computer device physically 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.

In the following description, the term "device" may be replaced with "circuit", "device", "unit", and the like. The hardware configuration of the network node 10 and the user equipment 20 may include one or more of the illustrated devices, or may not include some of the devices.

The functions in the network node 10 and the user device 20 are implemented by: when predetermined software (program) is read into hardware such as the processor 1001 and the storage device 1002, the processor 1001 performs an operation to control communication of the communication device 1004 or 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 and controls the entire computer. The processor 1001 may be a Central Processing Unit (CPU) including an interface with a peripheral device, a control device, an arithmetic device, a register, and the like. For example, the controller 140, the controller 240, and the like can be implemented by the processor 1001.

Further, the processor 1001 reads out a program (program code), a software module, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 to the storage device 1002, and executes various processes according to the read program. As the program, a program that causes a computer to execute at least a part of the operations described in the above embodiments is used. For example, the control unit 140 of the network node 10 shown in fig. 18 may be realized by a control program stored in the storage device 1002 and operated by the processor 1001. The control unit 240 of the user device 20 shown in fig. 19 may be realized by a control program stored in the storage device 1002 and operated by the processor 1001, for example. Although the above-described various processes are executed by 1 processor 1001, the above-described various processes may be executed by 2 or more processors 1001 at the same time or sequentially. The processor 1001 may be mounted by 1 or more chips. In addition, the program may be transmitted from the network via a telecommunication line.

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

The auxiliary storage device 1003 is a computer-readable recording medium, and may be constituted by at least one of 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 Disc, a digital versatile Disc, a Blu-ray (registered trademark) Disc, a smart card, a flash memory (for example, a card, a stick, a Key drive), a Floppy (registered trademark) Disc, a magnetic stripe, and the like.

The communication device 1004 is hardware (a transmitting/receiving device) for performing communication between computers via at least one of a wired network and a wireless network, and may be referred to as a network device, a network controller, a network card, a communication module, or the like. Communication apparatus 1004 is configured to include a high-Frequency switch, a duplexer, a filter, a Frequency synthesizer, and the like, for example, in order to realize at least one of Frequency Division multiplexing (FDD) and Time Division multiplexing (TDD). For example, a transmitting/receiving antenna, an amplifier unit, a transmitting/receiving unit, a transmission line interface, and the like can be realized by the communication device 1004. The transmitter and receiver may be physically and/or logically separated from each other.

The input device 1005 is an input device (for example, a keyboard, a mouse, a microphone, a switch, a key, a sensor, and the like) that receives an input from the outside. The output device 1006 is an output device (for example, a display, a speaker, an LED lamp, or the like) that outputs to the outside. The input device 1005 and the output device 1006 may be integrally formed (for example, a touch panel).

Further, the processor 1001 and the storage device 1002 are connected to each other via a bus 1007 for communicating information. The bus 1007 may be constituted by a single bus or may be constituted by different buses between devices.

The network node 10 and the user Device 20 may be configured to include hardware such as a microprocessor, a Digital Signal Processor (DSP), an ASIC (Application Specific Integrated Circuit), a PLD (Programmable Logic Device), an FPGA (Field Programmable Gate Array), or the like, and a part or all of the functional blocks may be implemented by the hardware. For example, the processor 1001 may be installed through at least 1 of these hardware.

(summary of the embodiment)

As described above, according to an embodiment of the present invention, there is provided a network node including: a control unit for determining execution of reconfiguration of UPF (User Plane Function); and a transmission Unit that transmits an instruction to reconfigure a Session ID including a PDU (Protocol Data Unit) Session ID and an address of an SMF (Session Management Function) associated with the UPF after reconfiguration, to an AMF (Access and Mobility Management) via the SMF or directly.

According to the above described embodiments, the network node is able to perform a reconfiguration of a PDU session between the UE and the UPF by deciding on the reconfiguration by the SMF and sending an indication of the reconfiguration to the AMF. That is, the reconfiguration of the PDU session can be performed appropriately according to the network architecture and the trigger.

In a case where the indication of reconfiguration is sent to the AMF via the SMF, an address of the SMF is assigned by the SMF. With this structure, the SMF can notify the AMF of the address of the SMF to be reconfigured.

In the case where there is already a PDU session related to the reconfigured UPF, the process of establishing a PDU session related to the reconfigured UPF may not be performed during the execution of the reconfiguration instruction. With this structure, unnecessary network timings can be prevented from being performed.

The network node may have a receiving part that receives an indication of a reconfiguration of the UPF from an application function or a maintenance function, the network node performing the reconfiguration of the UPF according to the received indication of the reconfiguration. With this structure, reconfiguration of the UPF can be performed according to a trigger received from the AF or the O & M.

When an indication of reconfiguration of a UPF is received from the maintenance function, in case of SSC (Session and Service Continuity) mode 2, a PDU Session related to the UPF before reconfiguration is cut off before reconfiguration is completed, and in case of SSC mode 3, a PDU Session related to the UPF before reconfiguration is cut off after reconfiguration is completed. With this configuration, the disconnection timing of the PDU session before reconfiguration can be controlled according to the SSC mode.

(supplement to embodiment)

While the embodiments of the present invention have been described above, the disclosed invention is not limited to such embodiments, and various modifications, alternatives, and substitutions will be apparent to those skilled in the art. Although specific numerical examples are used to facilitate understanding of the present invention, these numerical values are merely examples and any appropriate values may be used unless otherwise specified. The distinction of items in the above description is not essential to the present invention, and items described in two or more items may be used in combination as necessary, or items described in one item may be applied to items described in other items (as long as there is no contradiction). Boundaries of the functional units or the processing units in the functional block diagrams do not necessarily correspond to boundaries of the physical components. The operation of a plurality of (complex) functional units may be performed by one physical component, or the operation of one functional unit may be performed by a plurality of (complex) physical components. As for the processing procedure described in the embodiment, the order of processing may be changed without contradiction. For ease of illustrating the process, the network node 10 and the user device 20 have been illustrated using functional block diagrams, but such devices may also be implemented in hardware, in software, and combinations thereof. Software that operates via a processor provided with the network node 10 according to an embodiment of the present invention and software that operates via a processor provided with the user device 20 according to an embodiment of the present invention may also be stored in a Random Access Memory (RAM), a flash memory, a Read Only Memory (ROM), an EPROM, an EEPROM, a register, a hard disk (HDD), a removable disk, a CD-ROM, a database, a server, and any other suitable storage medium, respectively.

Note that the information is not limited to the form and embodiment described in the present specification, and may be notified by another method. For example, the notification of the Information may be implemented by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), higher layer signaling (e.g., RRC (Radio Resource Control) signaling, MAC (Medium Access Control) signaling, broadcast Information (MIB (Master Information Block), SIB (System Information Block)), other signals, or a combination of these.

The forms/embodiments described in the present disclosure can also be applied to LTE (Long Term Evolution), LTE-a (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system: fourth generation mobile communication system), 5G (5th generation mobile communication system: fifth generation mobile communication system), FRA (Future Radio Access), NR (new Radio: new air interface), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11(Wi-Fi (registered trademark)), IEEE 802.16(WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), systems using other appropriate systems, and/or next generation systems extended accordingly. In addition, a plurality of systems (for example, a combination of 5G and at least one of LTE and LTE-a) may be applied in combination.

The order of the processing procedures, sequences, flows, and the like of the respective forms and embodiments described in this specification may be changed without departing from the scope of the invention. For example, for the methods described in this disclosure, elements of the various steps are presented in an exemplary order, but are not limited to the particular order presented.

In the present specification, it is assumed that the specific operation performed by the network node 10 is sometimes performed by a higher-level node (upper node) thereof, depending on the case. It is obvious that in a network including one or more network nodes (network nodes) having the network node 10, various operations performed for communication with the user equipment 20 can be performed by at least one of the network node 10 and a network node other than the network node 10 (for example, MME, S-GW, or the like is considered, but not limited thereto). In the above, the case where the other network node than the network node 10 is one is exemplified, but the other network node may be a combination of a plurality of other network nodes (e.g., MME and S-GW).

Information or signals and the like explained in the present disclosure may be output from a higher layer (or lower layer) to a lower layer (or higher layer). Or may be input or output via a plurality of network nodes.

The input or output information and the like may be stored in a specific location (for example, a memory) or may be managed in a management table. The input or output information may be overwritten, updated or appended, etc. The output information may be deleted. The entered information may also be transmitted to other devices, etc.

The determination in the present disclosure may be made by a value (0 or 1) represented by 1 bit, may be made by a Boolean value (zero or false), and may be made by comparison of numerical values (for example, comparison with a predetermined value).

Software, whether referred to as software, firmware, middleware, microcode, hardware description languages, or by other names, should be construed broadly to mean commands, command sets, code segments, program code, programs (routines), subroutines, software modules, applications, software packages, routines, subroutines (subroutines), objects, executables, threads of execution, procedures, functions, and the like.

Further, software, commands, and the like may be transceived via a transmission medium. For example, in the case where software is transmitted from a website, a server, or another remote source using at least one of a wired technology (coaxial cable, an optical fiber cable, a twisted pair cable, a Digital Subscriber Line (DSL), and the like) and a wireless technology (infrared, microwave, and the like), at least one of these wired technology and wireless technology is included in the definition of transmission medium.

Information, signals, etc. described in this disclosure may be represented using any of a variety of different technologies. For example, data, commands, instructions (commands), information, signals, bits, symbols (symbols), chips (chips), etc., which are referenced throughout the above description, may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any combination thereof.

Further, terms described in the present disclosure and terms necessary for understanding the present disclosure may be replaced with terms having the same or similar meanings. For example, at least one of the channel and the symbol may be a signal (signaling). Further, the signal may be a message. In addition, a Component Carrier (CC) may be a Carrier frequency, a cell, a frequency Carrier, or the like.

The terms "system" and "network" and the like as used in this disclosure may be used interchangeably.

Further, information, parameters, and the like described in the present disclosure may be expressed by absolute values, relative values to predetermined values, or other corresponding information. For example, the radio resource may be indicated by an index.

The names used for the above parameters are not limiting in any way. Further, the numerical expressions and the like using these parameters may be different from those explicitly shown in the present disclosure. Since various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by all appropriate names, the various names assigned to these various channels and information elements are not restrictive names in any point.

In the present disclosure, terms such as "Base Station (BS)", "radio Base Station", "Base Station apparatus", "fixed Station (fixed Station)", "NodeB", "enodeb (enb)", "gbnodeb (gnb)", "access point (access point)", "transmission point)", "reception point (reception point)", "reception point (transmission/reception point)", "cell", "sector", "cell group", "carrier", "component carrier" may be used interchangeably. A base station may also be referred to as a macrocell, a smallcell, a femtocell, a picocell, or the like.

A base station can accommodate 1 or more (e.g., 3) cells (also referred to as sectors). When a 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 of the plurality of smaller areas can also provide communication services through a base station subsystem (e.g., an indoor small base station RRH: Remote Radio Head). The term "cell" or "sector" refers to a part or the whole of the coverage area of at least one of a base station and a base station subsystem that performs communication service within the coverage area.

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

For a mobile station, those skilled in the art will sometimes also refer to the following terms: a subscriber station, a mobile unit, a subscriber unit, a wireless unit, a remote unit, a mobile device, a wireless communication device, a remote device, a mobile subscriber station, an access terminal, a mobile terminal, a wireless terminal, a remote terminal, a handset, a user agent (user agent), a mobile client, a client, or some other suitable terminology.

At least one of the base station and the mobile station may be referred to as a transmitting apparatus, a receiving apparatus, a communication apparatus, or the like. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, or the like. The moving body may be a vehicle (e.g., an automobile, an airplane, etc.), may be a moving body that moves in an unmanned manner (e.g., an unmanned aerial vehicle, an unmanned vehicle, etc.), or may be a robot (manned or unmanned). At least one of the base station and the mobile station includes a device that does not necessarily move during a communication operation. For example, at least one of the base station and the mobile station may be an Internet of Things (IoT) device such as a sensor.

In addition, the base station in the present disclosure may be replaced with a user terminal. For example, the various aspects and embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between a plurality of user apparatuses 20 (for example, communication may also be referred to as Device-to-Device (D2D), Vehicle-to-event (V2X), and the like). In this case, the function of the network node 10 may be the configuration of the user equipment 20. In addition, the expressions such as "upstream" and "downstream" may be replaced by an expression (for example, "side") corresponding to inter-terminal communication. For example, the uplink channel, the downlink channel, etc. may be replaced by the side channel.

Likewise, the user terminal in the present disclosure may be replaced with a base station. In this case, the function of the user terminal can be configured as the base station.

Terms such as "determining" and "determining" used in the present disclosure may include various operations. The terms "determining" and "decision" may include, for example, the case where the determination (judging), calculation (calculating), processing (processing), derivation (deriving), investigation (investigating), search (looking up) (for example, searching in a table, a database, or another data structure), and confirmation (ascertaining) are regarded as being performed. The "determination" and "decision" may include a matter in which reception (e.g., reception information), transmission (e.g., transmission information), input (input), output (output), and access (e.g., access to data in a memory) are performed as "determination" and "decision". The "judgment" and "decision" may include matters regarding the solution (resolving), selection (selecting), selection (breathing), establishment (evaluating), comparison (comparing), and the like as the "judgment" and "decision". That is, the terms "determining" and "deciding" may include any action. The "judgment (decision)" may be replaced with "assumption", "expectation", "consideration".

The terms "connected" and "coupled" or any variation thereof are intended to mean that 2 or more than 2 elements are directly or indirectly connected or coupled to each other, and may include 1 or more than 1 intermediate element between 2 elements that are mutually "connected" or "coupled". The coupling or connection between the elements may be physical, logical, or a combination thereof. For example, "connect" may be replaced with "access". As used in this disclosure, for 2 elements, it is contemplated that the mutual "connection" or "coupling" may be made by using at least one of 1 or more electric wires, cables, and printed electrical connections, and by using electromagnetic energy of a wavelength having a radio frequency region, a microwave region, and a light (including both visible and invisible) region, or the like, as some non-limiting and non-inclusive examples.

The Reference Signal may be referred to as Reference Signal (RS) for short, and may also be referred to as Pilot (Pilot) according to the applied standard.

As used in this disclosure, the recitation of "according to" is not intended to mean "according to only" unless otherwise indicated. In other words, the expression "according to" means both "according to" and "at least according to".

Any reference to an element using the designations "first", "second", etc. used in this disclosure is not intended to limit the number or order of such elements. These terms are used in the present disclosure as a convenient way to distinguish between 2 or more elements. Thus, references to first and second elements do not imply that only 2 elements can be assumed herein or that in any event the first element must precede the second element.

The "unit" in each device configuration described above may be replaced with a "section", "circuit", "device", or the like.

When used in this disclosure, the terms "comprising", "including" and variations thereof mean inclusion as the term "comprising". Also, the term "or" used in the present disclosure means not exclusive or.

A radio frame may consist of one or more frames in the time domain. One or more individual frames in the time domain may be referred to as a subframe. Further, a subframe may be composed of one or more slots in the time domain. The subframe may be a fixed time length (e.g., 1ms) independent of a parameter set (numerology).

The parameter set may be a communication parameter applied to at least one of transmission and reception of a certain signal or channel. The parameter set may indicate, for example, at least one of SubCarrier Spacing (SCS), bandwidth, symbol length, cyclic prefix length, Transmission Time Interval (TTI), number of symbols per TTI, radio frame structure, specific filtering processing performed by the transceiver in the frequency domain, specific windowing processing performed by the transceiver in the Time domain, and the like.

The slot may be formed of one or more symbols (ofdm (orthogonal Frequency Division multiplexing) symbol, SC-fdma (single Carrier Frequency Division multiplexing) symbol, etc.) in the time domain. The time slot may be a time unit based on a parameter set.

A timeslot may contain multiple mini-slots. Each mini-slot may be composed of one or more symbols in the time domain. In addition, a mini-slot may also be referred to as a sub-slot. A mini-slot may be composed of a smaller number of symbols than a slot. The PDSCH (or PUSCH) transmitted in a unit of time greater than the mini slot may be referred to as PDSCH (or PUSCH) mapping type (type) a. The PDSCH (or PUSCH) transmitted using the mini-slot may be referred to as PDSCH (or PUSCH) mapping type (type) B.

The radio frame, subframe, slot, mini-slot, and symbol all represent a unit of time when a signal is transmitted. The radio frame, subframe, slot, mini-slot, and symbol may each be referred to by corresponding other designations.

For example, 1 subframe may be referred to as a Transmission Time Interval (TTI), a plurality of consecutive subframes may be referred to as TTIs, and 1 slot or 1 mini-slot may be referred to as a TTI. That is, at least one of the subframe and TTI may be a subframe (1ms) in the conventional LTE, may be a period shorter than 1ms (for example, 1-13 symbols), or may be a period longer than 1 ms. The unit indicating TTI may be referred to as a slot, a mini slot, or the like, instead of a subframe.

Here, the TTI refers to, for example, the minimum time unit of scheduling in wireless communication. For example, in the LTE system, the base station performs scheduling for allocating radio resources (frequency bandwidths, transmission powers, and the like that can be used by each user equipment 20) to each user equipment 20 in units of TTIs. In addition, the definition of TTI is not limited thereto.

The TTI may be a transmission time unit of a channel-coded data packet (transport block), code block, code word, or the like, or may be a processing unit of scheduling, link adaptation, or the like. In addition, when a TTI is given, a time interval (for example, the number of symbols) to which a transport block, a code block, a codeword, and the like are actually mapped may be shorter than the TTI.

In addition, in the case where 1 slot or 1 mini-slot is referred to as TTI, 1 or more TTIs (i.e., 1 or more slots or 1 or more mini-slots) may constitute the minimum time unit for scheduling. Further, the number of slots (mini-slots) constituting the minimum time unit of the schedule is controllable.

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

In addition, for a long TTI (long TTI) (e.g., normal TTI, subframe, etc.), it may be replaced by a TTI having a time length exceeding 1ms, and for a short TTI (short TTI) (e.g., shortened TTI, etc.), it may be replaced by a TTI having a TTI length smaller than the long TTI (long TTI) and having a TTI length of 1ms or more.

A Resource Block (RB) is a resource allocation unit of time and frequency domains, and may include one or more consecutive subcarriers (subcarriers) in the frequency domain. The number of subcarriers included in the RB is independent of the parameter set, and may be the same, for example, 12. The number of subcarriers included in the RB may be decided according to the parameter set.

Further, the time domain of the RB may contain one or more symbols, and may be 1 slot, 1 mini-slot, 1 subframe, or 1TTI in length. The 1TTI, 1 subframe, etc. may be respectively composed of one or more resource blocks.

In addition, one or more RBs may be referred to as Physical Resource Blocks (PRBs), Sub-Carrier groups (SCGs), Resource Element Groups (REGs), PRB pairs, RB peers, and so on.

In addition, a Resource block may be composed of one or more Resource Elements (REs). For example, 1RE may be a 1 subcarrier and 1 symbol radio resource region.

The Bandwidth Part (BWP: Bandwidth Part) (which may be referred to as partial Bandwidth, etc.) may represent a subset of consecutive common rbs (common resource blocks) for a certain parameter set in a certain carrier. Here, the common RB may be determined by an index of an RB with reference to a common reference point of the carrier. PRBs may be defined by a certain BWP and numbered within that BWP.

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

At least one of the set BWPs may be active (active), and the UE may not assume to transmit and receive a predetermined signal/channel other than the active BWP. In addition, "cell", "carrier", and the like in the present disclosure may be replaced by "BWP".

The above-described structures of radio frames, subframes, slots, mini slots, symbols, and the like are merely examples. For example, the number of subframes included in the radio frame, the number of slots per subframe or radio frame, the number of mini-slots included in a slot, the number of symbols and RBs included in a slot or mini-slot, the number of subcarriers included in an RB, the number of symbols in a TTI, the symbol length, the Cyclic Prefix (CP) length, and other configurations may be variously changed.

In this disclosure, for example, where the articles a, an, and the in english are added by translation, the disclosure also includes where the nouns following the articles are plural.

In the present disclosure, the phrase "a is different from B" may mean "a is different from B". The term "A and B are different from C" may be used. The terms "separate," coupled, "and the like may be interpreted as similar to" different.

The aspects and embodiments described in the present disclosure may be used alone or in combination, or may be switched depending on execution. Note that the notification of the predetermined information is not limited to be performed explicitly (for example, notification of "X") but may be performed implicitly (for example, notification of the predetermined information is not performed).

In addition, UPF #2 in the present disclosure is an example of a UPF after reconfiguration. UPF #1 is an example of a UPF before reconfiguration. AF is an example of an application function. O & M is an example of a maintenance function.

While the present disclosure has been described in detail, it should be apparent to those skilled in the art that the present disclosure is not limited to the embodiments described in the present disclosure. The present disclosure can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure defined by the claims. Accordingly, the disclosure is intended to be illustrative, and not limiting.

Description of reference numerals:

10 network node

110 sending part

120 receiving part

130 setting unit

140 control part

20 user device

210 sending part

220 receiving part

230 setting unit

240 control part

1001 processor

1002 storage device

1003 auxiliary storage device

1004 communication device

1005 input device

1006 output device