CN112690039B - network node - Google Patents

Abstract

The network node has: a control unit that determines execution of the reconfiguration of UPF (User Plane Function); and a transmitting unit that transmits a reconfiguration instruction including a PDU (Protocol Data Unit) session ID and an address of SMF (Session Management Function) related to the reconfigured UPF to AMF (Access and Mobility Management) via the SMF or directly.

Description

Network node

Technical Field

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

Background

In 3GPP (3 rd Generation Partnership Project: third generation partnership project), in order to achieve further increase in system capacity, further increase in data transmission speed, further decrease in delay in a Radio section, and the like, a Radio communication system called 5G or NR (New Radio: new air interface) (hereinafter, this Radio communication system is referred to as "5G" or "NR") has been studied. In 5G, various wireless technologies have been studied in order to meet the requirement that a throughput (throughput) of 10Gbps or more is achieved and that a delay in a wireless section is 1ms or less.

In NR, a network architecture including 5GC (5G Core Network:5G core network) corresponding to EPC (Evolved Packet Core: evolved packet core) which is a core network in network architecture of LTE (Long Term Evolution: long term evolution) and NG-RAN (Next Generation-Radio Access Network: next Generation-radio access network) corresponding to E-UTRAN (Evolved Universal Terrestrial Radio Access Network: evolved universal terrestrial radio access network) which is RAN (Radio Access Network: radio access network) in network architecture of LTE has been studied (for example, non-patent document 1).

Prior art literature

Non-patent literature

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

Disclosure of Invention

Problems to be solved by the invention

In performing reconfiguration of a PDU (Protocol Data Unit: protocol data unit) session, the timing of the reconfiguration of the SMF (Session Management Function: session management function) and UPF (User Plane Function: user plane function) is ambiguous in the case of multiple network architectures and triggers for the reconfiguration are envisaged.

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

Means for solving the problems

According to the disclosed technology, there is provided a network node having: a control unit that determines the execution of reconfiguration of UPF (User Plane Function: user plane function); and a transmitting unit that transmits an instruction for reconfiguration including a PDU (Protocol Data Unit: protocol data unit) session ID and an address of an SMF (Session Management Function: session management function) related to the reconfigured UPF to an AMF (Access and Mobility Management: access and mobility management) via the SMF or directly.

Effects of the invention

According to the disclosed technology, reconfiguration of PDU sessions 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 timing diagram for illustrating an example of PDU session reconfiguration.

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

Fig. 5 is a diagram showing 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 illustrating an example (1) of PCF/AF trigger-based PDU session reconfiguration in an embodiment of the present invention.

Fig. 10 is a timing diagram illustrating an example (2) of PCF/AF trigger-based PDU session reconfiguration in an embodiment of the present invention.

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

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

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

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

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

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

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

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

Fig. 19 is a diagram showing an example of a functional configuration of the user device 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 device 20 in the embodiment of the present invention.

Detailed Description

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.

The conventional technology can be used appropriately when the wireless communication system according to the embodiment of the present invention is operated. However, this prior art is, for example, but not limited to, existing LTE. Further, the term "LTE" as used in this specification has a broad meaning including LTE-Advanced and beyond (e.g., NR) or wireless LAN (Local Area Network: local area network) unless otherwise indicated.

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

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) of EPC (Evolved Packet Core: evolved Packet Core), 5GC (5G Core Network:5G Core network), etc., a UPF (User Plane Function: user plane function), a UE (User Equipment). The UPF is a Network node 10 having functions of a session point for an external PDU (Protocol Data Unit: protocol Data unit) connected to a DN (Data Network), routing and forwarding (forwarding) of a packet, 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 any reason for the same UE and the same AP (Access Point), in SSC (Session and Service Continuity: session and service continuity) mode 2, all PDU sessions are disconnected before a new PDU session is established. On the other hand, in SSC mode 3, after a new PDU session is established, the 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 is composed of a UE, which is a user equipment 20, and a plurality of network nodes 10. In the following, 1 network node 10 is associated with each function, but a plurality of functions may be realized by 1 network node 10, or 1 function may be realized 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 radio access enabled network node 10 connected to a UE, an AMF (Access and Mobility Management Function: access and mobility management functions) and a UPF (User Plane Function: user plane functions). The AMF is a network node 10 having functions of registration management, connection management, reachability management, mobility management, and the like, such as a terminal of a RAN interface, a terminal of a NAS (Non-Access Stratum), and the like. The AMF is connected to the RAN and the SMF (Session Management Function: session management function).

UPF is a network node 10 with functionality for external PDU (Protocol Data Unit) session points, routing and forwarding of packets, qoS (Quality of Service) handling of user plane, etc., interconnected with DN (Data Network). In the example shown in fig. 2, DN has DC (Data Center) #1 and DC #2. In addition, DC#1 includes application server V2X-App#1a, and DC#2 includes application server V2X-App#1b.

The SMF is a network node 10 having functions of session management, IP (Internet Protocol) address allocation and management of UEs, DHCP (Dynamic Host Configuration Protocol: dynamic host configuration protocol) function, ARP (Address Resolution Protocol: address resolution protocol) proxy, roaming function, and the like. The SMF is connected to the UPF and PCF (Policy Control Function: policy control function)/NEF (Network Exposure Function: network exposure function).

The NEF is a Network node 10 having a Function of notifying other NFs (Network functions) 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: application function). The AF is a network node 10 having a function of controlling an application server. AF is connected to DC#1 and DC#2.

In the network shown in fig. 2, an example in which reconfiguration of the UPF is triggered by AF is explained. Suppose 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, based on 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 timing diagram for illustrating an example of PDU session reconfiguration. Fig. 3 is an example of timing for reconfiguration of a PDU session for SSC mode 3. SMF#1 manages UPF#1, and SMF#2 manages UPF#2. When a PDU session is established between the UE and the upf#1, the smf#1 decides that a reconfiguration of the UPF and the SMF is required. Next, smf#1 notifies the AMF and the UE of a change of the PDU session. Next, a PDU session establishment procedure of upf#2 started by the UE is performed. After the PDU session is established between the UE and UPF#2, the PDU session of 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 described in which reconfiguration of the UPF is triggered by the SMF in the network shown in fig. 4. The DNN (Data Network Name: data network name) contains the application server. Suppose that the UE has established a PDU session of SSC mode 3 with the application server V2X-App #1a contained in DNN. Here, the SMF decides to move the UE connection to upf#2 according to 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 included in the DNN is not changed.

As described above, the SMF decides that a reconfiguration of the UPF is required, and this decision constitutes a trigger for the reconfiguration process of the UPF.

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

Case #1 (Case # 1) shown in fig. 5 is PDU session switching of SSC mode 3 between UPFs controlled by different SMFs. Case #2 (Case # 2) shown in fig. 5 is PDU session switching of SSC mode 3 between UPFs controlled by the same SMF. Solid arrows represent old PDU sessions and 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), in the Case of switching 2 UPFs by 1 SMF, the SMF change may not be performed for the lifetime of the PDU session. Here, how the handover of the PDU session is performed is not clear. For example, details of the timing of deciding the notification of AF, AMF, or SMF have not been 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 trigger

Due to any event at the application side, the AF indicates a reconfiguration of the UPF to the SMF via the PCF. For example, npcf_smplicycorol_updatenotify shown in fig. 6 is a message constituting a trigger.

2) O & M (Operation & maintence: operation and maintenance) trigger

In the event that UPF #1 is not available for maintenance or the like, O & M indicates a reconfiguration of the UPF to the SMF. A message based on O & M triggering (e.g., maintenance notification (maintenance notification), etc.) is input to the SMF.

3) AMF trigger

In the timing of Handover, registration procedure, mobility event notification (Handover, registration procedure, mobility event notification), the SMF decides on the reconfiguration of the UPF in SSC-3 based on the trigger from the AMF. For example, nsmf_pduse_updatecdcontrol shown in fig. 6 is a message constituting a trigger.

By the above-described trigger, the SMF decides 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/reception between the UE and the UPF1 is switched to the UL/DL data transmission/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 in the embodiment of the present invention is a network including 2 SMFs of smf#1 and smf#2. As in Case #1 (Case # 1) of fig. 5, one of the architectures is that different UPFs are controlled by different SMFs. The structure of connection of the AMF and the SMF is a structure in which the AMF is connected to the smf#2 and the smf#2 is connected to the smf#1. That is, AMF is not directly connected to SMF#1. The network shown in fig. 7 is hereinafter 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 of smf#1and smf#2. As shown in Case #1 (Case # 1) of fig. 5, one of the architectures is that different UPFs are controlled by different SMFs. The structure of connection of the AMF and the SMF is a structure in which the AMF is connected to the smf#1and the smf#1 is connected to the smf#2. That is, AMF is not directly connected to SMF#2. The network shown in fig. 8 is hereinafter referred to as architecture #2.

Fig. 9 is a timing diagram illustrating an example (1) of PCF/AF trigger-based PDU session reconfiguration in an embodiment of the present invention. Regarding the user plane data in the start state shown in fig. 9, a state in which upf#1 is an Anchor point (Anchor) but upf#2 is forwarding traffic as well, a PDU session of the UE with upf#2 already exists. Fig. 9 is a sequence executed in the architecture #1 shown in fig. 7, and illustrates the operation of the SSC pattern 3. In addition, fig. 9 is a timing 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 informs the reconfiguration of DN to smf#1 via PCF (AF Request for relocation,2.Npcf_smpolicy control_updatenotify). Next, smf#1 decides to move the session to smf#2and upf#2 (3.Determine that Session need to move to SMF#2and UPF#2: it is decided that the session needs to be moved to smf#2and upf#2). Then, smf#1 forwards (Forward) an indication for AMF (4. Nsmf_servicerelocation) to smf#2. Nsmf_servicerelocation contains the UE ID, PDU session ID, reconfiguration indication. Next, smf#2 notifies the AMF of the instruction to be forwarded and the address of smf#2 as the movement destination (5.namf_communication_n1n2message transfer). Next, the AMF sends a handover indication of the PDU session to the UE, receives a request for establishment of a new PDU session from the UE (6.PDU Session Modification Command:PDU session modification command, 7.PDU Session Est Req). Next, the AMF selects smf#2 according to an instruction from smf#1 (8.AMF Selects the SMF#2due to indication by SMF#1and forwards both the old&New PDU Sessions ID:AMF selects smf#2 according to an instruction of smf#1, and forwards both the old PDU session ID and the new PDU session ID). Next, the AMF notifies the smf#2 by including the PDU session establishment and release request in the PDU session IDs of both the old and new parties (9.PDU Session Req). Next, smf#2selects upf#2 as a new anchor point (10.SMF#2selects the UPF#2due the indication,that it knows the UE already connected UPF#2:SMF#2 selects upf#2, which knows that the UE has connected to upf#2, according to the indication). Since the PDU session of upf#2 with the UE already exists, the timing of PDU session establishment is not performed but reconfigured. In addition, after the PDU session of upf#2 with the UE is reconfigured, the old PDU session is released.

Fig. 10 is a timing diagram illustrating an example (2) of PCF/AF trigger-based PDU session reconfiguration in an embodiment of the present invention. Fig. 10 is a sequence executed in the architecture #2 shown in fig. 7, illustrating an operation of the SSC pattern 3. In addition, fig. 10 is a timing 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 the "Forward to smf#2 (Forward) instruction for AMF (4. Nsmf_servicerelocation)" of the timing in fig. 9 is deleted is the timing shown in fig. 10. In architecture #2, SMF #1 has a direct path with the AMF, so SMF #1 directly informs the AMF of a reconfiguration indication (5. Namf_communication_n1n2message transfer) containing the address of SMF #2 without informing the AMF via SMF # 2.

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

The O & M notifies the smf#1 of maintenance of upf#1 (1b.O&M Trigger for UPF#1maintenance notification:O&M triggers maintenance notification for upf#1). Next, smf#1 decides to move the session to smf#2and upf#2 (1b.Determine that Session need to move to SMF#2and UPF#2: it is decided that the session needs to be moved to smf#2and upf#2). Then, smf#1 forwards (Forward) an indication for AMF (4. Nsmf_servicerelease) to smf#2. Nsmf_servicerelease contains the UE ID, PDU session ID, release indication to select smf#2and not smf#1. Then, smf#2 notifies AMF of an instruction of forwarded (Forward) and an instruction of not selecting smf#1 (5. Namf_communication_n1n2message transfer). Next, the PDU session is released (3.PDU Session Release:PDU session release) by the smf#1 and the UE. Next, a new PDU session establishment request is received from the UE (4.PDU Session Est Req). Next, the AMF selects smf#2 based on the instruction from smf#1 (5.AMF Selects the SMF#2due to indication by SMF#1:AMF selects smf#2 based on the instruction from smf#1). Next, the AMF notifies the smf#2 of the PDU session establishment request (6.PDU Session Req). Next, a PDU session is established between the UE and UPF#2 (PDU Session established with UPF #2: PDU session established with UPF#2).

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

The timing after deleting the timing "Forward (Forward) to smf#2 instruction (4. Nsmf_servicerelease) for AMF" in fig. 11 is the timing shown in fig. 12. In architecture #2, SMF #1 has a direct path with the AMF, so SMF #1 directly informs the AMF of a reconfiguration indication containing the address of SMF #2 without informing the AMF via SMF #2 (2. Namf_communication_n1n2message transfer).

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

The O & M notifies the smf#1 of maintenance of upf#1 (1b.O&M Trigger for UPF#1maintenance notification:O&M triggers maintenance notification for upf#1). Next, smf#1 decides to move the session to smf#2and upf#2 (1b.Determine that Session need to move to SMF#2and UPF#2: it is decided that the session needs to be moved to smf#2and upf#2). Then, smf#1 forwards (Forward) an indication for AMF (4. Nsmf_servicerelocation) to smf#2. Nsmf_servicerelocation contains the UE ID, PDU session ID, reconfiguration indication. Thereafter, step #5 (5.namf_communication_n1n2message transfer) to step #9 (9.PDU Session Req) of fig. 9 is performed.

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

The O & M notifies the smf#1 of maintenance of upf#1 (1b.O&M Trigger for UPF#1maintenance notification:O&M triggers maintenance notification for upf#1). Next, smf#1 decides to move the session to smf#2and upf#2 (1b.Determine that Session need to move to SMF#2and UPF#2: it is decided that the session needs to be moved to smf#2and upf#2). Next, smf#1 notifies the AMF of a reconfiguration instruction (5.namf_communication_n1n2message transfer) including the address of smf#2. 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 timing diagram for explaining an example (3) of PCF/AF trigger-based PDU session reconfiguration in an embodiment of the present invention. As in Case #2 (Case # 2) of fig. 5, fig. 15 is a timing sequence performed in an architecture in which different UPFs are controlled by the same SMF, and reconfiguration of the UPF 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 (1.Creation of the AF request:AF creation of request). Subsequently, the AF notifies the NEF of the SSC pattern (2. Nnef_trafficinfluence_update (e.g. SSC patterns)). The reconfiguration of the UPF is performed in the notified SSC mode. Next, NEF and UDR (Unified Data Repository) update UE group information (3a.Updating the information: update information) and respond to AF (3b.nnef_trafficinfluence_updateresponse). Next, the UDR instructs the PCF to switch PDU sessions (4. Nudr_dm_notify). Next, the PCF instructs the SMF to switch PDU sessions (5. Npcf_smpolicy control_updatenotify). The SMF then performs the reconfiguration of the UPF (the UPF reconfiguration of the PDU session of 6.UPF relocation ofSSC 3PDU session:SSC 3) in accordance with the timing shown in fig. 3 or 6.

Fig. 16 is a timing diagram for explaining an example (4) of PCF/AF trigger-based PDU session reconfiguration in an embodiment of the present invention. As in Case #2 (Case # 2) of fig. 5, fig. 16 is a timing sequence performed in an architecture in which different UPFs are controlled by the same SMF, and reconfiguration of the UPF 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 does not direct the PCF via UDR to indicate directly the received indication from AF (1.NEF receives Nnef_Traf ficInfluence_Create/Update/Delete Request from AF: NEF receives the nnef_ Traf ficInfluence _create/Update/Delete Request from AF) (4. Npcf_policy authorization_create/Update/Delete Request: npcf_policy_create/Update/Delete Request). In addition, the BSF (Binding Support Function: binding support function) is an NF service having a function of registering or deregistering a customer of the NF service with the PCF.

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

The UPF periodically notifies the SMF or O & M of Load information (1 a. Load information (Load info)), 1b. Load information (Load info)). Then, O & M instructs the SMF to delete or move PDU sessions of UPF#1 in SSC mode 3 (2 a. Reduce/move SSC 3PDU Session from UPF#1: reduce/move PDU of SSC 3 from UPF#1). Next, the SMF decides to move the PDU session to upf#2 in SSC mode 3 (2b.SMF determine:SMF decision). Thereafter, the PDU session is reconfigured for UPF#2 in accordance with the timing of FIG. 3 or FIG. 6.

In addition, SSC pattern 3 is "make before break: the concept of on-off before on (accept). That is, when the session is moved between IP anchors, the session of the UE is not interrupted during the lifetime of the PDU session. That is, the change of the IP address of the session can be handled.

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

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

(device Structure)

Next, a functional configuration example of the network node 10 and the user device 20 that execute the above-described processing and operation will be described. The network node 10 and the user equipment 20 comprise the functions implementing the embodiments described above. However, the network node 10 and the user device 20 may each have only a part of the functions in 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 transmitting unit 110, a receiving 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 functional sections and the functional distinction may be arbitrary as long as the operations according to the embodiments of the present invention can be executed. Furthermore, a network node 10 having a plurality of different functions on the system architecture may be constituted by a plurality of network nodes 10 separated by each function.

The transmitting unit 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 device 20 and acquiring, for example, higher-layer information from the received signals. The transmitting unit 110 also 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 the preset setting information and various setting information transmitted to the user device 20 in a storage device, and reads the setting information from the storage device as necessary. The content of the setting information is, for example, information on session management or the like.

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

< user device 20 >)

Fig. 19 is a diagram showing an example of a functional configuration of the user device 20. As shown in fig. 19, the user device 20 includes a transmitting unit 210, a receiving 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 functional sections and the functional distinction may be arbitrary as long as the operations according to the embodiments of the present invention can be executed.

The transmitting unit 210 generates a transmission signal from the transmission data, and transmits the transmission signal wirelessly. The receiving unit 220 receives various signals wirelessly and acquires a higher layer signal from the received physical layer signal. The reception unit 220 also 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 transmitting unit 210 transmits PSCCH (Physical Sidelink Control Channel: physical side link control channel), PSSCH (Physical Sidelink Shared Channel: physical side link shared channel), PSDCH (Physical Sidelink Discovery Channel: physical side link discovery channel), PSBCH (Physical Sidelink Broadcast Channel: physical side link broadcast channel), or the like to the other user device 20, and the receiving unit 120 receives PSCCH, PSSCH, PSDCH, the PSBCH, or the like from the other user device 20. The transmitting unit 210 and the receiving unit 220 have a wireless LAN or a wired LAN transmitting/receiving function.

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 a storage device, and reads out 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 on session management or the like.

As described in the embodiment, the control unit 240 performs processing related to PDU session establishment for the user plane. Further, the control unit 240 performs processing related to reconfiguration of the PDU session. The transmission unit 210 may include a function unit related to signal transmission in the control unit 240, and the reception unit 220 may include a function unit related to signal reception in the control unit 240.

(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 (structures) are realized by any combination of at least one of hardware and software. The implementation means of each functional block is not particularly limited. That is, each functional block may be realized by one device physically and/or logically combined, or may be realized by two or more devices physically and/or logically separated and directly and/or indirectly (for example, by wired and/or wireless) connected, by these multiple devices. The software may also be combined with the above-described device or devices to implement the functional blocks.

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

For example, the network node 10, the user device 20, and the like in one embodiment of the present disclosure may each function as a computer that performs the processing of the wireless communication method of the present disclosure. Fig. 20 is a diagram showing an example of a hardware configuration of the network node 10 and the user device 20 according to one embodiment of the present disclosure. The network node 10 and the user device 20 may be configured as computer devices 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 addition, in the following description, the term "means" may be replaced with "circuit", "device", "unit", or the like. The hardware configuration of the network node 10 and the user device 20 may be configured to include one or more of the illustrated devices, or may be configured to not include a part of the devices.

The functions in the network node 10 and the user device 20 are implemented by the following methods: by reading predetermined software (program) in hardware such as the processor 1001 and the storage device 1002, the processor 1001 performs an operation, and controls communication by 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, for example, causes an operating system to operate, and controls the entire computer. The processor 1001 may be configured by a central processing unit (CPU: central Processing Unit) including an interface with peripheral devices, a control device, an arithmetic device, a register, and the like. For example, the control unit 140, the control unit 240, and the like described above may be realized 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, thereby executing various processes. 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 implemented 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 described as being executed by 1 processor 1001, the above-described various processes may be executed simultaneously or sequentially by 2 or more processors 1001. 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 by at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM: erasable programmable ROM), EEPROM (Electrically Erasable Programmable ROM: electrically erasable programmable ROM), RAM (Random Access Memory: random access Memory), and the like, for example. The storage device 1002 may also 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 a communication method according to an embodiment of the present disclosure.

The auxiliary storage device 1003 is a computer-readable recording medium, and may be configured of at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a Floppy disk, a magneto-optical disk (for example, a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk, a smart card, a flash memory (for example, a card, a stick, a Key drive (Key drive)), a Floppy (registered trademark) disk, a magnetic stripe, and the like.

The communication device 1004 is hardware (transceiver) 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, for example. The communication device 1004 is configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, and the like in order to realize at least one of frequency division multiplexing (FDD: frequency Division Duplex) and time division multiplexing (TDD: time Division Duplex), for example. For example, a transmitting/receiving antenna, an amplifier section, a transmitting/receiving section, a transmission path interface, and the like can be realized by the communication device 1004. For the transmitting/receiving section, the transmitting section and the receiving section may be physically and/or logically separately installed.

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

The processor 1001 and the storage device 1002 are connected by a bus 1007 for communicating information. The bus 1007 may be formed of a single bus or may be formed of 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: digital Signal Processor), an ASIC (Application Specific Integrated Circuit: application specific integrated circuit), a PLD (Programmable Logic Device: programmable logic device), and an FPGA (Field Programmable Gate Array: field programmable gate array), or may be configured to implement a part or all of the functional blocks by the hardware. For example, the processor 1001 may be installed by at least 1 of these hardware.

(summary of embodiments)

As described above, according to an embodiment of the present invention, there is provided a network node having: a control unit that determines the execution of reconfiguration of UPF (User Plane Function: user plane function); and a transmitting unit that transmits an instruction for reconfiguration including a PDU (Protocol Data Unit: protocol data unit) session ID and an address of an SMF (Session Management Function: session management function) related to the reconfigured UPF to an AMF (Access and Mobility Management: access and mobility management) via the SMF or directly.

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

In the case where the indication of reconfiguration is sent to the AMF via the SMF, the address of the SMF is given 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 the PDU session related to the reconfigured UPF may not be performed in the execution of the instruction of the reconfiguration. With this structure, unnecessary network timing can be prevented from being performed.

The network node may have a receiving portion that receives an indication of a reconfiguration of the UPF from the application function or the 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 instruction for reconfiguration of a UPF is received from the maintenance function, in the case of SSC (Session and Service Continuity: session and service continuity) mode 2, PDU sessions relating to UPF before reconfiguration are cut off before reconfiguration is completed, and in the case of SSC mode 3, PDU sessions relating to UPF before reconfiguration are cut off after reconfiguration is completed. With this configuration, the timing of cutting off the PDU session before reconfiguration can be controlled according to the SSC mode.

(supplement of the embodiment)

While the embodiments of the present invention have been described above, the disclosed invention is not limited to the embodiments, and those skilled in the art will appreciate various modifications, corrections, substitutions, and the like. Specific numerical examples are used to facilitate understanding of the present invention, but these numerical examples are merely examples unless otherwise indicated, and any suitable values may be used. The distinction between 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 required, or items described in one item may be applied to items described in other items (unless contradiction arises). The boundaries of functional units or processing units in the functional block diagrams do not necessarily correspond to the boundaries of physical components. The operation of the plurality of (plural) functional units may be performed by one physical component, or the operation of one functional unit may be performed by a plurality of physical (plural) components. With regard to the processing procedures described in the embodiments, the order of processing may be exchanged without contradiction. For ease of illustration, the network node 10 and the user device 20 are illustrated using functional block diagrams, but such devices may also be implemented in hardware, in software, and combinations thereof. The software that is operated by the processor provided by the network node 10 according to the embodiment of the present invention and the software that is operated by the processor provided by the user device 20 according to the embodiment of the present invention may also be stored in Random Access Memory (RAM), flash memory, read Only Memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), a removable disk, a CD-ROM, a database, a server, and any other suitable storage medium, respectively.

The information notification is not limited to the form and embodiment described in the present specification, and may be performed by other methods. For example, the notification of the information may be implemented by physical layer signaling (e.g., DCI (Downlink Control Information: downlink control information), UCI (Uplink Control Information: uplink control information)), higher layer signaling (e.g., RRC (Radio Resource Control: radio resource control) signaling, MAC (Medium Access Control: medium access control) signaling, broadcast information (MIB (Master Information Block: master information block), SIB (System Information Block: system information block)), other signals, or a combination of these.

The various forms/embodiments described in this disclosure may also be applied to LTE (Long Term Evolution: long term evolution), LTE-a (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4 th generation mobile communication system: fourth generation mobile communication system), 5G (5 th generation mobile communication system: fifth generation mobile communication system), FRA (Future Radio Access, future wireless access), NR (new Radio: new air port), 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-wide-band), bluetooth (registered trademark), systems using other suitable systems, and/or next generation systems extended accordingly. Further, 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 processing procedures, time sequences, flow, and the like of the respective modes/embodiments described in the present specification can be replaced without contradiction. For example, for the methods described in this disclosure, elements of the various steps are presented in an exemplified order, but are not limited to the particular order presented.

In the present specification, the specific operation performed by the network node 10 may be performed by an upper node (upper node) thereof, as the case may be. It is apparent that in a network composed of one or more network nodes (network nodes) having the network node 10, various actions performed for communication with the user equipment 20 can be performed by at least one of the network node 10 and other network nodes (for example, consider an MME or S-GW or the like, but not limited thereto) other than the network node 10. The case where other network nodes than the network node 10 are one is exemplified in the above, but the other network nodes may be a combination of a plurality of other network nodes (e.g., MME and S-GW).

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

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

The determination in the present disclosure may be performed by a value (0 or 1) represented by 1 bit, may be performed by a Boolean value (true or false), and may be performed by a comparison of numerical values (e.g., a comparison with a predetermined value).

With respect to software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names, should be broadly interpreted to refer to a command, a set of commands, code, a code segment, program code, a program (program), a subroutine, a software module, an application, a software package, a routine, a subroutine, an object, an executable, a thread of execution, a procedure, a function, or the like.

Further, software, commands, etc. may be transmitted and received via a transmission medium. For example, in the case where software is transmitted from a website, server, or other remote source using at least one of a wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL: digital Subscriber Line), etc.) and a wireless technology (infrared, microwave, etc.), at least one of the wired technology and the wireless technology is included in the definition of transmission medium.

Information, signals, etc., illustrated in this disclosure may be represented using any of a variety of different technologies. For example, data, commands, instructions (command), information, signals, bits, symbols, chips (chips), and the like, which are referred to in the above description as a whole, may be represented by voltages, currents, electromagnetic waves, magnetic fields or particles, optical fields or photons, or any combination of these.

Further, the terms described 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 the channel and symbol may be a signal (signaling). Further, the signal may be a message. In addition, the component carrier (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.

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

The names used for the above parameters are non-limiting in any point. Further, the numerical formulas and the like using these parameters may also differ 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 non-limiting names at any point.

In the present disclosure, terms such as "Base Station (BS)", "radio Base Station", "Base Station apparatus", "fixed Station", "NodeB", "eNodeB (eNB)", "gndeb (gNB)", "access point", "transmission point (transmission point)", "reception point", "transmission point", "reception point", "cell", "sector", "cell group", "carrier", "component carrier", and the like may be used interchangeably. A base station is also sometimes referred to as a macrocell, a microcell, a femtocell, a picocell, or the like.

A base station can accommodate 1 or more (e.g., 3) cells (also referred to as sectors). In the case of a base station accommodating a plurality of cells, the coverage area of the base station can be divided into a plurality of smaller areas, each of which can also provide communication services through a base station subsystem (e.g., a small base station RRH: remote Radio Head (remote radio head) for indoor use). The term "cell" or "sector" refers to a part or the whole of a coverage area of at least one of a base station and a base station subsystem that perform communication services within the coverage area.

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

For mobile stations, those skilled in the art are sometimes referred to by the following terms: a subscriber station, mobile unit (mobile unit), subscriber unit, wireless unit, remote unit, mobile device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile 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 the mobile body, the mobile body itself, or the like. The mobile body may be a vehicle (e.g., an automobile, an airplane, etc.), a mobile body that moves unmanned (e.g., an unmanned plane, an unmanned vehicle, etc.), or a robot (manned or unmanned). At least one of the base station and the mobile station also includes a device that does not necessarily have to move during a communication operation. For example, at least one of the base station and the mobile station may be an internet of things (Internet of Things: ioT) device of a sensor or the like.

Further, the base station in the present disclosure may be replaced with a user terminal. For example, the various 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, may also be referred to as Device-to-Device (D2D), vehicle-to-evaluation (V2X), or the like). In this case, the function of the network node 10 may be defined as the structure of the user device 20. Further, the expressions of "upstream" and "downstream" and the like may be replaced by expressions (e.g., "side") corresponding to communication between terminals. For example, the upstream channel, downstream channel, etc. may be replaced by side channels.

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

The terms "determining" and "determining" used in the present disclosure may include various operations. The terms "determine" and "determining" may include, for example, cases where "determination" and "determining" are regarded as matters of determining (determining), calculating (calculating), processing (processing), deriving (deriving), investigating (searching), searching (searching in a table, a database or other data structure), and confirming (approving). Further, "determining" or "deciding" may include a matter that receives (e.g., receives information), transmits (e.g., transmits information), inputs (input), outputs (output), accesses (e.g., accesses data in a memory) as "determining" or "deciding". Further, "judging" and "deciding" may include matters of solving (resolving), selecting (selecting), selecting (setting), establishing (establishing), comparing (comparing), and the like as matters of "judging" and "deciding". That is, the terms "determine" and "determining" may include terms that "determine" and "determine" any action. Further, "judgment (decision)" may be replaced with "assumption", "expectation", and "consider (confirm)".

The terms "connected," "coupled," or any variation of these terms are intended to denote any direct or indirect connection or coupling between 2 or more elements, and may include cases where 1 or more intermediate elements exist between 2 elements that are "connected" or "coupled" to each other. The coupling or connection between the elements may be a physical coupling or connection, a logical coupling or connection, or a combination of these. For example, "connection" may be replaced with "access". As used in this disclosure, it is contemplated that for 2 elements, the interconnection "or" coupling "may be made by using at least one of 1 or more wires, cables, and printed electrical connections, and as some non-limiting and non-inclusive examples, by using electromagnetic energy such as electromagnetic energy having wavelengths in the wireless frequency domain, the microwave region, and the optical (including both visible and invisible) region.

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

The use of the terms "according to" and "according to" in this disclosure is not intended to mean "according to" unless otherwise indicated. In other words, the term "according to" means "according to only" and "according to at least" both.

Any reference to elements using references such as "first," "second," etc. used in this disclosure, is not intended to limit the number or order of such elements in its entirety. These calls are referred to as simple methods of distinguishing between 2 or more elements and are used in this disclosure. Thus, references to first and second elements do not indicate that only 2 elements can be taken herein or that in any aspect the first element must precede the second element.

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

When the terms "include", "comprising" and variations thereof are used in this disclosure, these terms are meant to be inclusive as if they were the term "comprising". Also, the term "or" as used in this disclosure means not exclusive or.

A radio frame may be made up of one or more frames in the time domain. One or more of the frames in the time domain may be referred to as subframes. Further, a subframe may be composed of one or more slots in the time domain. A subframe may be a fixed length of time (e.g., 1 ms) 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 represent, for example, at least one of a subcarrier spacing (SCS: subCarrier Spacing), a bandwidth, a symbol length, a cyclic prefix length, a transmission time interval (TTI: transmission Time Interval), a number of symbols per TTI, a radio frame structure, a specific filtering process performed by the transceiver in the frequency domain, a specific windowing process performed by the transceiver in the time domain, and the like.

A slot may be formed from one or more symbols (OFDM (Orthogonal Frequency Division Multiplexing) symbols, SC-FDMA (Single Carrier Frequency Division Multiple Access) symbols, etc.) in the time domain. A slot may be a unit of time based on a set of parameters.

A slot may contain multiple mini-slots. Each mini-slot may be made up of one or more symbols in the time domain. In addition, the mini-slot may also be referred to as a sub-slot. Mini-slots may be made up of a fewer number of symbols than slots. PDSCH (or PUSCH) transmitted in units of time greater than the mini-slot may be referred to as PDSCH (or PUSCH) mapping type (type) a. PDSCH (or PUSCH) transmitted using mini-slots may be referred to as PDSCH (or PUSCH) map type (type) B.

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

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

Here, TTI refers to, for example, a scheduled minimum time unit in wireless communication. For example, in the LTE system, the base station performs scheduling for each user device 20 to allocate radio resources (bandwidth, transmission power, and the like that can be used in each user device 20) in TTI units. In addition, the definition of TTI is not limited thereto.

The TTI may be a transmission time unit of a data packet (transport block), a code block, a codeword, or the like after channel coding, 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) in which a transport block, a code block, a codeword, or the like is actually mapped may be shorter than the TTI.

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

A TTI having a time length of 1ms may be referred to as a normal TTI (TTI in LTE release 8-12), a general TTI, a long TTI (long TTI), a general subframe, a long (long) subframe, a slot, etc. A TTI that is shorter than a normal TTI may be referred to as a shortened TTI, a short TTI (short TTI), a partial or fractional TTI, a shortened subframe, a short (short) subframe, a mini-slot, a sub-slot, a slot, etc.

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

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

Further, the time domain of the RB may contain one or more symbols, which may be 1 slot, 1 mini slot, 1 subframe, or 1TTI in length. A 1TTI, a 1 subframe, etc. may each be composed of one or more resource blocks.

In addition, one or more RBs may be referred to as Physical resource blocks (PRB: physical RBs), subcarrier groups (SCG: sub-Carrier groups), resource element groups (REG: resource Element Group), PRB pairs, RB peering.

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

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

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

At least one of the set BWP may be active, and the UE may not contemplate transmitting and receiving a predetermined signal/channel outside the active BWP. In addition, "cell", "carrier", etc. in the present disclosure may be replaced by "BWP".

The above-described structure of the radio frame, subframe, slot, mini-slot, symbol, etc. is merely an example. For example, the number of subframes included in a 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 the like may be variously changed.

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

In the present disclosure, the term "a is different from B" may mean that "a is different from B. The term "a and B are different from C" may also be used. The terms "separate," coupled, "and the like may also be construed as" different.

The embodiments described in the present disclosure may be used alone, in combination, or switched according to execution. Note that the notification of the predetermined information is not limited to being performed explicitly (for example, notification of "yes" or "X"), and 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 reconfigured UPF. Upf#1 is an example of UPF before reconfiguration. AF is an example of an application function. O & M is an example of a maintenance function.

The present disclosure has been described in detail above, but it should be 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 can be implemented as modifications and variations without departing from the spirit and scope of the present disclosure as defined by the description of the claims. Accordingly, the description of the present disclosure is intended to be illustrative, and not in any limiting sense.

Description of the reference numerals:

10. network node

110. Transmitting unit

120. Receiving part

130. Setting part

140. Control unit

20. User device

210. Transmitting unit

220. Receiving part

230. Setting part

240. Control unit

1001. Processor and method for controlling the same

1002. Storage device

1003. Auxiliary storage device

1004. Communication device

1005. Input device

1006. Output device

Claims (5)

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

a control unit that determines the reconfiguration of a UPF, which is a user plane function; and

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

2. The network node of claim 1, wherein,

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

3. The network node of claim 1, wherein,

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

4. The network node of claim 1, wherein,

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

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

5. The network node of claim 4, wherein,

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