Network node, terminal and communication method

Abstract

A network node has: a reception unit that receives, from an access and mobility management function (AMF), a message including a protocol data unit (PDU) session establishment request and a master node identifier corresponding to a first master node; and a transmission unit that transmits, to a user plane function (UPF), a packet forwarding control protocol (PFCP) session establishment request such that the first master node carries a quality of service (QoS) flow, the transmission unit transmitting a first message to the AMF, the first message includes a PDU session establishment permission, another master node sets a request instruction via a PDU session branch, and a master node identifier corresponding to the first master node, and the reception unit receives a second message from the AMF, the second message including information indicating the division of the QoS flow and a master node identifier corresponding to the first master node, and the first message includes a PDU session establishment permission and a PDU session branch setting request instruction. The transmission unit transmits a PFCP session change request to the UPF such that the first master node carries a part of the Qo S flow, the reception unit receives a third message from the AMF, the third message including a PDU session change request and a master node identifier corresponding to a second master node, and the transmission unit transmits a PFC session change request to the UPF such that the first master node carries a part of the Qo S flow, and the reception unit receives a PFC session change request including a PDU session change request and a master node identifier corresponding to the second master node. The second master node carries a part of the QoS flow.

Description

Technical Field

[0001] The present invention relates to a network node, a terminal and a communication method in a communication system. Background Art

[0002] 3GPP (registered trademark) (3rd Generation Partnership Project) is conducting research on wireless communication methods known as 5G or NR (New Radio) (hereinafter referred to as "5G" or "NR") to achieve further increases in system capacity, higher data transmission speeds, and lower latency within wireless networks. In 5G, various wireless technologies are being researched to meet the requirements of achieving throughput of 10 Gbps or more and keeping latency within wireless networks to 1 ms or less.

[0003] In NR, a network architecture including 5GC (5G Core Network) and NG-RAN (Next Generation-Radio Access Network) is studied. The 5GC (5G Core Network) corresponds to the core network in the network architecture of LTE (Long Term Evolution), namely EPC (Evolved Packet Core), and the NG-RAN (Next Generation-Radio Access Network) corresponds to the RAN (Radio Access Network) in the network architecture of LTE, namely E-UTRAN (Evolve d Universal Terrestrial Radio Access Network) (for example, non-patent document 1).

[0004] Prior art literature

[0005] Non-patent literature

[0006] Non-Patent Document 1: 3GPP TS 23.501 V18.0.0 (December 2022)

[0007] Non-Patent Document 2: 3GPP TR 23.700-53 V18.0.0 (December 2022)

[0008] Non-Patent Document 3: 3GPP TS 38.413 V17.3.0 (December 2022)

[0009] Non-Patent Document 4: 3GPP TS 33.501 V18.0.0 (December 2022)

[0010] Non-Patent Document 5: 3GPP TS 38.304 V17.2.0 (December 2022)

[0011] Non-Patent Document 6: 3GPP TS 23.502 V18.0.0 (2022-12)

[0012] Non-Patent Document 7: 3GPP TS 24.501 V18.1.0 (December 2022)

[0013] Non-Patent Document 8: 3GPP TS 29.244 V18.0.1 (December 2022)

[0014] Non-Patent Document 9: 3GPP TS 24.193 V18.0.0 (2022-12)

[0015] Non-Patent Document 10: 3GPP TS 38.300 V17.2.0 (2022-09) Summary of the Invention

[0016] Problems to be solved by the invention

[0017] During the 5G transition, DC (Dual Connectivity) was adopted to stabilize coverage during the initial phase of wireless system introduction. However, DC is difficult to implement in a multi-vendor environment. Therefore, in the transition to next-generation wireless systems, it is desirable to achieve stable coverage during the initial phase of introduction without using DC.

[0018] The present invention has been made in view of the above-mentioned problems, and an object of the present invention is to stabilize coverage during handover of a wireless system.

[0019] Means for solving problems

[0020] According to the disclosed technology, a network node is provided, which comprises: a receiving unit, which receives a message including a protocol data unit (PDU) session establishment request and a master node identifier corresponding to a first master node from an access and mobility management function (AMF); and a sending unit, which sends a packet forwarding control protocol (PFCP) session establishment request to a user plane function (UPF) so that the first master node carries a quality of service (QoS) flow, and the sending unit sends a first message to the AMF, the first message including a PDU session establishment permission, an indication of setting a request for other master nodes via a PDU session branch, and an identifier corresponding to the first master node. The receiving unit receives a second message from the AMF, the second message including information indicating the segmentation of the QoS flow and the master node identifier corresponding to the first master node, the sending unit sends a PFCP session change request to the UPF so that the first master node carries a part of the QoS flow, the receiving unit receives a third message from the AMF, the third message including a PDU session change request and the master node identifier corresponding to the second master node, the sending unit sends a PFCP session change request to the UPF so that the second master node carries a part of the QoS flow.

[0021] Effects of the Invention

[0022] According to the disclosed technology, coverage stabilization can be achieved during wireless system handover. BRIEF DESCRIPTION OF THE DRAWINGS

[0023] Figure 1 It is a diagram for explaining an example of a communication system.

[0024] Figure 2 This is a diagram for explaining an example of a communication system in a roaming environment.

[0025] Figure 3 This is a diagram for explaining an example of a network in the embodiment of the present invention.

[0026] Figure 4 This is a sequence diagram for explaining an example of initial setting and setting change in the embodiment of the present invention.

[0027] Figure 5 This is a sequence diagram for explaining an example of cell selection in an embodiment of the present invention.

[0028] Figure 6 This is a sequence diagram for explaining an example of a registration process in an embodiment of the present invention.

[0029] Figure 7 This is a sequence diagram for illustrating example (1) of the PDU session establishment process in an embodiment of the present invention.

[0030] Figure 8 This is a sequence diagram for illustrating example (2) of the PDU session establishment process in an embodiment of the present invention.

[0031] Figure 9 This is a timing diagram of Example (3) used to illustrate the PDU session establishment process in an embodiment of the present invention.

[0032] Figure 10 This is a timing diagram used to illustrate an example of inactivation of a PDU session in an embodiment of the present invention.

[0033] Figure 11 This is a sequence diagram for explaining an example of a terminal-initiated service request process in an embodiment of the present invention.

[0034] Figure 12 This is a sequence diagram for explaining an example of a network startup service request process in an embodiment of the present invention.

[0035] Figure 13 1 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30 in the embodiment of the present invention.

[0036] Figure 14 This is a diagram showing an example of the functional configuration of the terminal 20 in the embodiment of the present invention.

[0037] Figure 15 This is a diagram showing an example of the hardware configuration of the base station 10 and the terminal 20 in the embodiment of the present invention.

[0038] Figure 16 1 is a diagram showing an example of the structure of a vehicle 2001 in the embodiment of the present invention. DETAILED DESCRIPTION

[0039] Hereinafter, an embodiment of the present invention will be described with reference to the drawings. Note that the embodiment described below is an example, and the embodiment to which the present invention is applied is not limited to the following embodiment.

[0040] In the operation of the wireless communication system according to the embodiment of the present invention, existing technologies are appropriately used. The existing technologies are, for example, but not limited to, existing LTE. Furthermore, unless otherwise specified, the term "LTE" used in this specification has a broad meaning that includes LTE-Advanced and subsequent technologies (e.g., NR) or wireless LANs (Local Area Networks).

[0041] Furthermore, in the embodiment of the present invention, “configuring” wireless parameters and the like may be pre-configuring predetermined values, or may be configuring wireless parameters notified from the network node 30 or the terminal 20 .

[0042] Figure 1 is a diagram for explaining an example of a communication system. Figure 1 As shown, the communication system is composed of a UE (terminal terminal) 20 and multiple network nodes 30. Hereinafter, it is assumed that there is one network node 30 corresponding to each function. However, multiple functions may be implemented by one network node 30, or one function may be implemented by multiple network nodes 30. Furthermore, the "connection" described below may refer to either a logical connection or a physical connection.

[0043] RAN (Radio Access Network) is a network node 30 with a radio access function, which may include a base station 10 and is connected to the UE, AMF (Access and Mobility Management Function) and UPF (User plane function). AMF is a network node 30 with functions such as termination of the RAN interface, termination of NAS (Non-Access Stratum), registration management, connection management, reachability management, and mobility management. UPF is a network node 30 interconnected with DN (Data Network) and has functions such as a PDU (Protocol Data Unit) session point for the outside, routing and forwarding of packets, and QoS (Quality of Service) processing of the user plane. UPF and DN constitute a network slice. Multiple network slices are constructed in the wireless communication network of the embodiment of the present invention.

[0044] The AMF is connected to the UE, RAN, SMF (Session Management Function), NSSF (Network Slice Selection Function), NEF (Network Exposu reFunction), NRF (Network Repository Function), UDM (Unified Data Management), AUSF (Authentication Server Function), PCF (Policy Control Function), and AF (Application Function). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via interfaces based on their respective services, namely, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0045] SMF is a network node 30 that has functions such as session management, UE IP (Internet Protocol) address allocation and management, DHCP (Dynamic Host Configuration Protocol) function, ARP (Address Resolution Protocol) proxy, roaming function, etc. NEF is a network node 30 that has the function of notifying other NFs (Network Function) of capabilities and events. NSSF is a network node 30 that has functions such as selecting the network slice to which the UE is connected, determining the authorized NSSAI (Network Slice Selection Assistance Information), determining the set NSSAI, and determining the AMF set to which the UE is connected. PCF is a network node 30 that has the function of performing network policy control. AF is a network node 30 that has the function of controlling application servers. NRF is a network node 30 that has the function of discovering NF instances that provide services. UDM is a network node 30 that manages subscriber data and authentication data. UDM is connected to the UDR (User Data Repository) that stores this data.

[0046] Figure 2FIG is a diagram for explaining an example of a communication system in a roaming environment. Figure 2 As shown, the network is composed of a UE (terminal terminal) 20 and multiple network nodes 30. Hereinafter, it is assumed that there is one network node 30 corresponding to each function. However, multiple functions may be implemented by one network node 30, or one function may be implemented by multiple network nodes 30. Furthermore, the "connection" described below may refer to either a logical connection or a physical connection.

[0047] The RAN is a network node 30 with radio access functionality, connected to the UE, AMF, and UPF. The AMF is a network node 30 that performs functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 that connects to the DN and performs functions such as the external PDU session point, packet routing and forwarding, and user plane QoS processing. The UPF and DN constitute a network slice. Multiple network slices are constructed in the wireless communication network according to the embodiments of the present invention.

[0048] The AMF is connected to the UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEP P (Security Edge Protection Proxy). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are interconnected via their respective service-based interfaces, namely, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0049] SMF is a network node 30 that has functions such as session management, UE IP address allocation and management, DHCP function, ARP proxy, roaming function, etc. NEF is a network node 30 that has the function of notifying other NFs of capabilities and events. NSSF is a network node 30 that has functions such as selecting the network slice to which the UE is connected, determining the authorized NSSAI, determining the set NSSAI, and determining the AMF set to which the UE is connected. PCF is a network node 30 that has the function of performing network policy control. AF is a network node 30 that has the function of controlling the application server. NRF is a network node 30 that has the function of discovering NF instances that provide services. SEPP is a non-transparent proxy used to filter control plane messages between PLMNs (Public Land Mobile Network). Figure 2 The vSEPP shown is a SEPP in a visited network, and the hSEPP is a SEPP in a home network.

[0050] like Figure 2 As shown, the UE is in a roaming environment in a VPLMN (Visited PLMN), connected to the RAN and AMF. The VPLMN and HPLMN (Home PLMN) are connected via vSEPP and hSEPP. The UE can communicate with the UDM of the HPLMN via the AMF of the VPLMN, for example.

[0051] Here, during the 5G transition, DC (Dual Connectivity) was adopted to stabilize coverage during the initial phase of wireless system introduction. However, DC is difficult to implement in a multi-vendor environment. Therefore, in the transition to next-generation wireless systems, it is desirable to achieve stable coverage during the initial phase of introduction without using DC.

[0052] In addition, dual registration has also been standardized as a 5G transfer method. The purpose of introducing dual registration is to solve the interaction between EPC and E-UTRA and 5GC and NR in the absence of N26 (refer to non-patent document 1) as the interface between AMF and MME. In the case of 5GC and E-UTRA, dual registration does not have a sufficient solution for the event of registering to both EPC and 5GC via the same E-UTRA cell. Therefore, in the case where the next-generation core network is an extension of 5GC, dual registration standardized as a 5G transfer method cannot be used.

[0053] That is, when the next-generation core network is envisioned as an extension of 5GC, although it is hoped that a method of stabilizing coverage in the initial stage of introduction of the next-generation wireless system and not using DC can be achieved, such a method does not currently exist.

[0054] Therefore, when the terminal registers or connects to the network, the terminal may have two MNs (Master Nodes). Figure 3 This is a diagram for explaining an example of a network in an embodiment of the present invention. The terminal is newly introduced as follows: it has two RRC (Radio Resource Control) states, two CM (Connection Management) states, and one registration state (RM (Registration Management) state). The QoS flow can be dispersed or divided between the two MNs. In addition, the cells used in waiting and paging can be limited. Figure 3 As shown, two MNs can identify each other via AMF and select an appropriate mobile destination MN during handover.

[0055] In addition, the existing specifications related to registration define the RM-DEREGISTERED and RM-REGISTERED states. The terminal and AMF each have an RM state. The RM state transition is based on NAS signaling. For a terminal, independent RM states are defined for each access. Access can be, for example, 3GPP access or non-3GPP access.

[0056] In addition, existing specifications related to connections define the CM-IDLE and CM-CONNECTED states. The terminal and AMF each have a CM state. CM state transitions are based on RRC signals for the terminal and N2 signals for the AMF, which are the interface with the RAN. For a single terminal, separate CM states are defined for each access. Accesses include, for example, 3GPP access and non-3GPP access.

[0057] In addition, in the existing specifications, ATSSS (Access Traffic Steering, Switching, Splitting) handles the distribution and splitting of QoS flows between 3GPP access and non-3GPP access.

[0058] For example, AMF can manage one RM state and two CM states for the 3GPP access of the terminal. AMF can maintain the MN identifier, Global RAN Node ID (global RAN node ID) (refer to non-patent document 1), RAN UE NGAP (NG Application Protocol: NG application protocol) ID (refer to non-patent document 3), and AMF UE NGAP ID (refer to non-patent document 3) in each newly imported MN level terminal context, which has two in total, instead of in each access level terminal context. AMF can use the MN level terminal context for message routing between RAN-SMF, K gNB (See Non-Patent Document 4) Differentiation, derivation of CM states for each connection, and derivation of UE-CM states indicating terminal reachability. For 3GPP access, a terminal can manage one RM state and two CM states. Furthermore, the RAN UE NGAP ID is an identifier used within the RAN node to identify a UE on the NG interface, and the AMF UE NGAP ID is an identifier used within the AMF to identify a UE on the NG interface.

[0059] For example, the SMF can distribute the QoS flows of a PDU session among multiple MNs. The SMF can notify the RAN of policies and, based on the RAN's decision, distribute the QoS flows of the PDU session among multiple MNs. The SMF can request the terminal to send a PDU session change request from other MNs for an existing PDU session accessed by 3GPP. The RAN can determine the QoS flow distribution and QoS flow segmentation of the PDU session based on the policies notified by the SMF. The terminal can send a PDU session change request from the second MN to the existing PDU session accessed by 3GPP based on the instructions notified by the SMF.

[0060] For example, the RAN may set paging activation or paging deactivation. Paging deactivation indicates that a RAN node does not perform paging. When paging is deactivated, the RAN may notify the terminal of this information using broadcast information and notify the AMF of this information using an N2 message unrelated to the terminal. The AMF may not send N2 paging to a RAN with paging deactivation. The terminal may not consider cells of a RAN with paging deactivation as candidates for cell selection or cell reselection. If the terminal is camped on a cell of a RAN with paging activation as usual, it may further consider cells of a RAN with paging deactivation as candidates for cell selection or cell reselection.

[0061] For example, the RAN may, based on its settings, prioritize the handover target when there is another RAN nearby that uses a different RAT (Radio Access Technology) than the partner RAN node, the other MN in a dual MN configuration. Alternatively, when there is another RAN nearby that uses the same RAT as the partner RAN node, the RAN may prioritize the handover target. The RAN may select the handover target based on information about the partner RAN node notified by the AMF. The AMF may notify the RAN of information about the partner node. The AMF may also notify the RAN of information about the partner node when both MNs have transitioned to CM-Connected.

[0062] Figure 4 This is a sequence diagram illustrating an example of initial setup and configuration changes in an embodiment of the present invention. In step S101a, the RAN node 10A sends an NG SETUP REQUEST (see Non-Patent Document 3) to the AMF 30A. In the following step S102a, the AMF 30A sends an NG SETUP Response (NG SETUPRESPONSE) to the RAN node 10A. Here, the RAN node 10A is an example of a RAN node activated by paging.

[0063] Meanwhile, in step S101b, the RAN node 10B sends an NG SETUP request to the AMF 30A, including a paging deactivation indication with a dummy value set in the bearer TA list (Supported Tracking Area list) (see Non-Patent Document 3). In the following step S102a, the AMF 30A sends an NG SETUP response to the RAN node 10B. Here, the RAN node 10B is an example of a RAN node with paging deactivated. If the RAN is a next-generation system, the paging deactivation indication may be set. Thereafter, the AMF 30A does not use the RAN node 10B for paging.

[0064] In step S103a, the RAN node 10A sends a RAN CONFIGURATION UPDATE to the AMF 30A. In the following step S104a, the AMF 30A sends a RAN CONFIGURATION UPDATE ACKNOWLEDGE to the RAN node 10A.

[0065] Meanwhile, in step S103b, the RAN node 10B sends a RAN Settings Update including a Paging Deactivation Indication to the AMF 30A. In the following step S104b, the AMF 30A sends a RAN Settings Update Permit to the RAN node 10B. Thereafter, the AMF 30A does not use the RAN node 10B for paging.

[0066] Figure 5 This is a sequence diagram illustrating an example of cell selection in an embodiment of the present invention. In step S201, RAN node 10B transmits broadcast information to UE 20, including the information element "cellNotForPaging" indicating that paging is inactive, which is set to true (see Non-Patent Document 5). In the following step S202, UE 20 does not select the cell of RAN node 10B as a candidate for cell selection or cell reselection unless it is camped on another normal cell.

[0067] Figure 6This is a sequence diagram illustrating an example registration process in an embodiment of the present invention. In steps S301 and S302, UE 20 sends a registration request message including a new Dual MN Indication IE (Information Element) to AMF 30A via NR and NG-RAN, or via Next Generation Radio and Next Generation RAN. In the following, the RAN node corresponding to the RAT and RAN used in step S301 is referred to as RAN node 10A. UE 20 sets the newly defined UE-CM state to UE-CM-Connected. The UE-CM state is set to UE-CM-Connected even if a CM connection exists, and to UE-CM-Idle if no CM connection exists.

[0068] In the following step S303, AMF 30A stores the MN identifier corresponding to the RAN node 10A, the Global RAN Node ID corresponding to the RAN node 10A, the RAN UE NGAPID corresponding to the UE 20, and the AMF UE NGAP ID corresponding to the UE 20 in each MN-level terminal context. AMF 30A stores the MN identifier as MN#1, the Global RAN Node ID of the RAN node 10A obtained in advance during the NG SETUP procedure, the RAN UE NGAP ID obtained from the RAN node 10A, and the AMF UE NGAP ID that has been allocated or will be allocated later by the AMF 30A. AMF 30A sets the newly defined UE-CM state to UE-CM-Connected.

[0069] In addition, each MN-level terminal context may also include a ULI (User Location Information) indicating user location information. Furthermore, in existing specifications, the AMF 30A maintains a set of RAN UE NGAP ID, AMF UE NGAP ID, and ULI in each access-level terminal context (see Non-Patent Document 6).

[0070] In step S304, the AMF 30A, UE 20, and RAN node 10A perform a normal registration procedure. In step S305, the AMF 30A sends a Registration Permit to the UE 20. In step S306a, the AMF 30A sets the RM state to RM Registered. In step S307a, after the registration procedure is complete, the AMF 30A sets the CM state to CM-Idle. In other words, the AMF 30A sets the UE-CM state to UE-CM-Idle.

[0071] In step S306b, the UE 20 that has received the registration permission sets the RM state to RM registered. In step S307b, the UE 20 sets the CM state to CM-idle after the registration process is completed. That is, the UE 20 sets the UE-CM state to UE-CM-idle.

[0072] Furthermore, when the UE 20 transmits a registration request next time, it can appropriately use the available RAT and RAN regardless of the RAN node 10A used this time.

[0073] Figure 7 This is a sequence diagram of example (1) for illustrating the PDU session establishment process in an embodiment of the present invention. In steps S401 and S402, the UE 20 sends a PDU session establishment request to the AMF 30A via NR and NG-RAN or the next generation wireless and next generation RAN (see non-patent document 6). The PDU session establishment request includes a 5GSM (5GS Session Management) capability IE (see non-patent document 7). In the ATSSS-ST bit of the 5GSM capability IE, information indicating "RAN-based QoS flow splitting" is newly set. The UL NAS transmission that carries the PDU session establishment request sets the request category to "MA PDU Request" and the request subcategory to "3GPP Access Multiple Connections" (see non-patent document 6). In addition, the RAN node corresponding to the RAT and RAN used in step S401 is set to the RAN node 10A below.

[0074] In the next step S403, AMF 30A maintains the MN identifier as MN#1, the Global RAN Node ID of the RAN node 10A obtained in advance during the NG SETUP process, the RAN UE NGAP ID obtained from the RAN node 10A, and the AMF UE NGAP ID that the AMF 30A has allocated or will allocate later in each MN-level terminal context.

[0075] In the next step S404, AMF 30A selects SMF 30B (see Non-Patent Document 6). In the next step S405, AMF 30A sends an Nsmf_PDUSession_CreateSMContext Request (see Non-Patent Document 6) containing the PDU session establishment request to SMF 30B. The Nsmf_PDUSession_CreateSMContext Request contains the MN identifier of MN#1.

[0076] In the next step S406, SMF 30B considers the possibility of adding another MN, and first assumes that MN#1 sets all QoS flows, and sends a PFCP (Packet Forwarding Control Protocol) session establishment request to UPF 30C (see non-patent document 8). This PFCP session establishment request includes an established MAR IE (Create MAR IE). This established MAR IE (Create MAR IE) includes a 3GPP Access MN#1 Forwarding IE (3GPP Access MN#1 Forwarding IE). In addition, in the case of the existing ATSSS, the established MAR IE (Create MAR IE) includes a 3GPP Access Forwarding Action Information IE (3GPP Access Forwarding Action Information IE) and a non-3GPP Access Forwarding Action Information IE (Non-3GPP Access Forwarding Action Information IE) (see non-patent document 8). In the next step S407, UPF 30C sends a PFCP session establishment response to SMF 30B.

[0077] In the next step S408, SMF 30B sends a Namf_Communication_N1N2MessageTransfer message (see non-patent document 6) containing a PDU Session Resource Setup Request Transfer IE to AMF 30A. This PDU Session Resource Setup Request Transfer IE contains a multiple MN permission indication and information indicating RAN-based QoS flow splitting. This Namf_Communication_N1N2MessageTransfer message contains the MN identifier of MN#1. SMF 30B also sends a PDU Session Establishment Permit (see non-patent document 7) to UE 20 within this Namf_Communication_N1N2MessageTransfer message. This PDU Session Establishment Permit contains a PDU session branch setup request indication via another MN.

[0078] In the following step S409, the AMF 30A compares the MN identifier received from the SMF 30B as MN#1 with the locally held terminal contexts for each MN level. As a result of the comparison, the AMF 30A recognizes that MN#1 corresponds to the RAN node 10A. In the following step S410, the AMF 30A forwards the PDU Session Resource Setup Request Transfer IE in the received Namf_Communication_N1N2MessageTransfer message via an N2PDU Session Request.

[0079] In the following step S411, the RAN node 10A detects the presence of another RAN node #B near the UE 20 based on a measurement report received from the UE 20. In the following step S412, the RAN node 10A refers to information from OAM (Operations Administration and Maintenance) and determines appropriate QoS flow distribution or QoS flow splitting between itself and RAN node #B. QoS flow distribution involves allocating individual QoS flows to the RAN node 10A or another RAN node. QoS flow splitting involves splitting a single QoS flow, with one portion carried by the RAN node 10A and the remaining portion carried by another RAN node. In the case of QoS flow splitting, the RAN node 10A can set the split ratio based on instructions from the UE 20 and / or the UPF 30C. The determination made by the RAN node 10A in step S412 can be similar to that in the DC case, except that the split ratio is set based on instructions from the UE 20 and / or the UPF 30C.

[0080] Figure 8 This is a sequence diagram illustrating Example (2) of the PDU Session Establishment process in an embodiment of the present invention. In step S413, RAN node 10A establishes a QoS flow with UE 20 that determines whether the RAN node 10A will carry all or part of the QoS flow (see Non-Patent Document 6). RAN node 10A also forwards a PDU Session Establishment Permit to UE 20.

[0081] In the next step S414, the RAN node 10A sends a message including a PDU Session Resource Setup Response Transfer IE (see Non-Patent Document 6) to the AMF 30A. The QoS Flow Failed to Setup List IE included in the PDU Session Resource Setup Response Transfer IE specifies unestablished QoS flows, and the QoS flows to be split are specified in the new IE QoS Flow Partly Setup List IE. In addition to the IE QoS Flow Partly Setup List IE, the PDU Session Resource Setup Response Transfer IE also specifies a traffic ratio for the RAN node 10A.

[0082] In the next step S415, AMF 30A sends an Nsmf_PDUSession_UpdateSMContext Request (see Non-Patent Document 6) including the received PDU Session Resource Setup Response Transfer IE to SMF 30B. The Nsmf_PDUSession_UpdateSMContext Request message includes the MN identifier of MN#1.

[0083] In the following step S416, SMF 30B sends a PFCP session change request to UPF 30C to set up the QoS flow for MN#1 and, regarding the QoS flow to be split, to set the ratio of the QoS flow for MN#1 based on the QoS Flow Partly Setup List IE indicating the QoS flow for MN#1 and to set the TEID (Tunnel Endpoint Identifier) on the MN#1 side. The ratio of the QoS flow for MN#1 is set in the Update 3GPP Access MN#1 Forwarding Action Information IE included in the PFCP session change request. In the following step S417, UPF 30C sends a PFCP session change response to SMF 30B.

[0084] After establishing the QoS flow in step S413, the UE 20 sends a PDU session change request to the RAN node 10B in step S418. The UE 20 sets the same PDU session ID in the PDU session change request as in the PDU session establishment request in step S401. In the following step S419, the RAN node 10B confirms the 5G-S-TMSI (Temporary Mobile Subscriber Identity) in the received RRC message containing the PDU session change request and forwards the PDU session change request to the same AMF 30A (see Non-Patent Document 6).

[0085] In the next step S420, AMF 30A maintains the MN identifier as MN#2, the Global RAN Node ID of the RAN node 10B obtained in advance during the NG SETUP process, the RAN UE NGAP ID obtained from the RAN node 10B, and the AMF UE NGAP ID that AMF 30A has allocated or will allocate later in each MN-level terminal context.

[0086] In the following step S421, the AMF 30A sends a UE Context Change Request to the RAN node 10A. The UE Context Change Request message includes the newly defined Partner RAN Node IE. The Partner RAN Node IE can be the Global RAN Node ID or RAT category of the RAN node 10B.

[0087] In the next step S422, since the PDU session ID of the received PDU session change request is the same as that of the already established PDU session, the AMF 30A selects the same SMF 30B. In the next step S423, the AMF 30A sends an Nsmf_PDU Session_UpdateSMContext Request (see Non-Patent Document 6) containing the received PDU session change request to the SMF 30B. This Nsmf_PDU Session_UpdateSMContext Request message includes the MN identifier of MN#2.

[0088] In the next step S424, when SMF 30B receives the Nsmf_PDUSession_UpdateSMContext Request message, it confirms the QoS flow setting failure list IE (QoS Flow Failed to Setup List IE) and QoS flow partial setup list IE (QoS Flow Partly Setup List IE) received in step S414, and determines the QoS flow that needs to be set in MN#2.

[0089] In the next step S425, since the PDU session ID of the PDU session change request included in the Nsmf_PDUSession_UpdateSMContext Request message is the same as the established PDU session, the SMF 30B selects the same UPF 30C.

[0090] In the following step S426, SMF 30B sends a PFCP Session Change Request to UPF 30C to configure the QoS flow required for MN#2. In the 3GPP Access MN#2 Forwarding Action Information IE (3GPP Access MN#2 Forwarding Action Information IE) within the Update MARIE (see Non-Patent Document 8) included in this PFCP Session Change Request, the traffic ratio for MN#2 is set, derived from the traffic ratio for MN#1 listed in the QoS Flow Partly Setup List IE. In the following step S427, UPF 30C sends a PFCP Session Change Response to SMF 30B.

[0091] In the next step S428, SMF 30B recognizes that the MNs are different and sends a Namf_Communication_N1N2MessageTransfer message containing a PDU Session Resource Setup Request Transfer IE (see non-patent document 3) to AMF 30A regarding the QoS flow that needs to be set up in MN#2. The PDU Session Resource Setup Request Transfer IE contains a multiple MN disallowed indication. The Namf_Communication_N1N2MessageTransfer message contains the MN identifier of MN#2. SMF 30B simultaneously sends a PDU session change command to UE 20 within the Namf_Communication_N1N2MessageTransfer message. The PDU session change command contains an ATSSS container IE. SMF 30B sets the QoS flow distribution and splitting information between MN#1 and MN#2 in the ASSSS container IE (see non-patent document 9).

[0092] Figure 9 This is a sequence diagram of Example (3) for illustrating the PDU session establishment process in an embodiment of the present invention. In the following step S429, the AMF 30A compares the MN identifier received from the SMF 30B as MN#2 with the locally maintained terminal contexts of each MN level. As a result of the comparison, the AMF 30A recognizes that MN#2 corresponds to the RAN node 10B. In the following step S430, the AMF 30A forwards a PDU session resource establishment request including the received PDU session resource setup request transfer IE (PDU Session Resource Setup Request Transfer IE) and the PDU session change command message. The PDU session resource establishment request includes the newly defined partner RAN node. The partner RAN node IE can be the Global RAN Node ID or RAT category of the RAN node 10A.

[0093] In the following step S431, RAN node 10B establishes a QoS flow with UE 20. Simultaneously, RAN node 10B forwards a PDU session change command (see Non-Patent Document 6) to UE 20. In the following step S432, QoS-related in-terminal rules are configured using the ATSSS container IE (see Non-Patent Document 6).

[0094] In the next step S433, the RAN node 10B sends a message including the PDU Session Resource Setup Response Transfer IE (see Non-Patent Document 6) to the AMF 30A. In the next step S434, the AMF 30A sends an Nsmf_PDUSession_UpdateSMContextRequest (see Non-Patent Document 6) including the received PDU Session Resource Setup Response Transfer IE to the SMF 30B. This Nsmf_PDUSession_UpdateSMContextRequest message includes the MN identifier of MN#2.

[0095] In the next step S435, SMF 30B sends a PFCP session change request to UPF 30C to set the TEID of MN#2. In the next step S436, UPF 30C sends a PFCP session change response to SMF 30B.

[0096] Figure 10 This is a sequence diagram illustrating an example of an inactive PDU session in an embodiment of the present invention. In step S501, the RAN node 10A detects that no data is being sent. In step S502, the RAN node 10A sends a UE Context Release Request (see Non-Patent Document 6). In step S503, the AMF 30A sends a UE Context Release Command to the RAN node 10A. In step S504, the RAN node 10A sends a UE Context Release Complete to the AMF 30A.

[0097] In the next step S505, AMF 30A sets a timer to delete the information related to MN#1 in each MN-level terminal context when it expires. In addition, after the timer expires, MN#1 becomes CM-Idle in AMF 30A.

[0098] In the next step S506, AMF 30A sends Nsmf_PDUSession_UpdateSMContext Request to SMF 30B. The Nsmf_PDUSession_UpdateSMContext Request message includes the MN identifier as MN#1.

[0099] In the next step 507, SMF 30B sends a PFCP session change request to UPF 30C to release the TEID on the MN#1 side. In the next step S508, UPF 30C sends a PFCP session change response to SMF 30B.

[0100] In step S551, the RAN node 10B detects that no data is being sent. In the following step S552, the RAN node 10B sends a UE Context Release Request (see Non-Patent Document 6). In the following step S553, the AMF 30A sends a UE Context Release Command to the RAN node 10B. In the following step S554, the RAN node 10B sends a UE Context Release Complete to the AMF 30B.

[0101] In the next step S555, AMF 30A sets a timer to delete the information related to MN#2 in each MN-level terminal context upon expiration. In addition, after the timer expires, AMF 30A becomes CM-Idle for MN#2 and UE 20 becomes UE-CM-Idle for UE 20.

[0102] In the next step S556, AMF 30A sends Nsmf_PDUSession_UpdateSMContext Request to SMF 30B. The Nsmf_PDUSession_UpdateSMContext Request message includes the MN identifier as MN#2.

[0103] In the next step S557, SMF 30B sends a PFCP session change request to UPF 30C to release the TEID on the MN#2 side. In the next step S558, UPF 30C sends a PFCP session change response to SMF 30B.

[0104] Figure 11 This is a sequence diagram illustrating an example of a terminal-initiated service request process in an embodiment of the present invention. In step S601, UE 20 sends a service request to RAN node 10C (see Non-Patent Document 6). This service request message sets the Uplink Data Status IE (see Non-Patent Document 7) for the established PDU Session ID.

[0105] In the following step S602, the RAN node 10C confirms the 5G-S-TMSI in the RRC message containing the service request and forwards the service request to the same AMF 30A. In the following step S603, the AMF 30A stores the MN identifier as MN#1, the Global RAN Node ID of the RAN node 10C previously obtained in the NG SETUP procedure, the RAN UE NGAP ID obtained from the RAN node 10C, and the AMF UE NGAP ID that has been allocated or will be allocated later by the AMF.

[0106] In the next step S604, since the PDU session ID is the same as the established PDU session, the AMF 30A selects the same SMF 30B. In the next step S605, the AMF 30A sends an Nsmf_PDUSession_UpdateSMContext Request to the SMF 30B. The Nsmf_PDUSession_UpdateSMContext Request message contains the MN identifier as MN#1. Next, execute Figure 7 Steps after step S406 in .

[0107] Figure 12 This is a sequence diagram illustrating an example of a network start service request process in an embodiment of the present invention. In step S701, the UPF 30C receives incoming data (see Non-Patent Document 6). In the following step S702, the UPF 30C sends a PFCP session report request. In the following step S703, the SMF 30B sends a Namf_Communication_N1N2MessageTransfer (see Non-Patent Document 6) to the AMF 30A.

[0108] In the next step S704, the AMF 30A excludes the RAN node for which the paging inactivation indication is set by the NG SETUP request or the RAN setting update from the destination, and sends the paging to the RAN node (refer to non-patent document 6). Figure 11 Steps after step S601 in .

[0109] Furthermore, regarding the handover process, the RAN node 10A can consider measurement reports, RRM information, partner RAN nodes, and RAN configuration information obtained from OAM to determine the handover target (see Non-Patent Document 10). For example, by considering the RAN type or RAT of the partner RAN node, it is possible to configure the handover so that, during handover, one of the two MNs belongs to the NG-RAN and the other to the next-generation RAN. Furthermore, the mechanism for ensuring this configuration during cell selection may depend on the terminal's implementation.

[0110] In addition, regarding AS (Access Stratum: access layer) security, it can be expanded in K gNB The access type distinguishers used in the derivation (see Non-Patent Document 4) are: For example, MN#1 can use 3GPP access 0x01, and MN#2 can use the second 3GPP access 0x03. Thus, the integrity of the connection between the terminal and MN1 and between the terminal and MN2 is protected by different keys.

[0111] Furthermore, regarding reachability management, the above-mentioned UE-CM state may be used instead of the CM state.

[0112] Furthermore, regarding the terminal location, the ULI of MN#1, the ULI of MN#2, or the ULI of MN#1 and the ULI of MN#2 may be used instead of the ULI of each terminal.

[0113] The above embodiments enable the configuration of dual MNs using different RATs, distributing or segmenting QoS flows within the dual MNs. Furthermore, new CM state management applicable to dual MNs is possible, as well as the introduction of a paging inactivation indicator from a RAN node.

[0114] That is, coverage can be stabilized during wireless system transfer.

[0115] (Device Structure)

[0116] Next, we will describe the functional configuration examples of base station 10, network node 30, and terminal 20 that implement the above-described processes and operations. Base station 10, network node 30, and terminal 20 include functions for implementing the above-described embodiments. However, base station 10, network node 30, and terminal 20 may each include only a portion of the functions described in the embodiments.

[0117] <Base Station 10 and Network Node 30>

[0118] Figure 13 1 is a diagram showing an example of the functional configuration of the base station 10 and the network node 30. Figure 13As shown, the base station 10 includes a transmitting unit 110 , a receiving unit 120 , a setting unit 130 , and a control unit 140 . Figure 13 The functional structure shown is merely an example. As long as the operations described in the embodiments of the present invention can be implemented, the functional divisions and names of the functional units may be arbitrary. Furthermore, the network node 30 may have the same functional structure as the base station 10. Furthermore, a network node 30 having multiple distinct functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0119] The transmitter 110 includes a function of generating a signal to be transmitted to the terminal 20 or another network node 30 and transmitting the signal via wired or wireless means. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30 and obtaining, for example, higher-layer information from the received signals. A communication unit including the transmitter 110 and the receiver 120 may also be configured.

[0120] The configuration unit 130 stores pre-configured configuration information and various configuration information sent to the terminal 20 in a storage device, and reads the configuration information from the storage device as needed. The configuration information includes, for example, information related to the dual MN configuration.

[0121] As described in the embodiments, the control unit 140 performs processing related to communication within the network. Furthermore, the control unit 140 performs processing related to communication based on a dual MN configuration. Furthermore, the control unit 140 performs processing related to communication with the terminal 20. The functional units related to signal transmission within the control unit 140 may be included in the transmitter 110, while the functional units related to signal reception within the control unit 140 may be included in the receiver 120.

[0122] <Terminal 20>

[0123] Figure 14 2 is a diagram showing an example of the functional structure of the terminal 20. Figure 14 As shown, the terminal 20 includes a transmitting unit 210 , a receiving unit 220 , a setting unit 230 , and a control unit 240 . Figure 14 The functional structure shown is only an example. As long as the operations involved in the embodiments of the present invention can be implemented, the functional divisions and names of the functional units can be arbitrary. In addition, the communication device that serves as the resource holder 20 can also have the same functional structure as the terminal 20.

[0124] The transmitter 210 generates a transmission signal based on the transmission data and wirelessly transmits the transmission signal. The receiver 220 wirelessly receives various signals and obtains higher-layer signals from the received physical layer signals. Furthermore, the receiver 220 has the function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, reference signals, etc. transmitted from the network node 30. A communication unit including the transmitter 210 and the receiver 220 may also be configured.

[0125] The configuration unit 230 stores various configuration information received by the receiving unit 220 from the network node 30 in a storage device and reads it from the storage device as needed. In addition, the configuration unit 230 also stores pre-set configuration information. The configuration information includes, for example, information related to the dual MN configuration.

[0126] As described in the embodiment, the control unit 240 performs processing related to communication in the network. Functional units related to signal transmission in the control unit 240 may be included in the transmitter 210, and functional units related to signal reception in the control unit 240 may be included in the receiver 220.

[0127] (Hardware Structure)

[0128] The block diagram used in the description of the above embodiment ( Figure 13 and Figure 14 ) shows blocks in functional units. These functional blocks (structural parts) are implemented by any combination of at least one of hardware and software. In addition, there is no particular limitation on the implementation method of each functional block. That is, each functional block can be implemented using one device that is physically or logically combined, or can be implemented using multiple devices by connecting two or more physically or logically separated devices directly or indirectly (for example, using wired or wireless connections). The functional blocks can also be implemented by combining software in the above-mentioned one device or the above-mentioned multiple devices.

[0129] Functions include, but are not limited to, judging, determining, determining, calculating, calculating, processing, deriving, investigating, searching, confirming, receiving, sending, outputting, accessing, resolving, selecting, choosing, establishing, comparing, assuming, expecting, regarding, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assigning. For example, a functional block (structural unit) that performs a transmitting function is referred to as a transmitting unit or a transmitter. In short, as described above, there is no particular limitation on the implementation method.

[0130] For example, the network node 30, the terminal 20, and the like in one embodiment of the present disclosure may also function as a computer that performs the processing of the wireless communication method of the present disclosure. Figure 15 This figure shows an example of the hardware structure of a base station 10 and a terminal 20 according to one embodiment of the present disclosure. The network node 30 may have the same hardware structure as the base station 10. The base station 10 and the terminal 20 may be configured as computer devices that physically include a processor 1001, a storage device 1002, an auxiliary storage device 1003, a communication device 1004, an input device 1005, an output device 1006, and a bus 1007.

[0131] In the following description, the term "device" can be replaced with "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and the terminal 20 may include one or more of the devices shown in the figures, or may exclude some of the devices.

[0132] The various functions in the base station 10 and the terminal 20 are implemented as follows: predetermined software (programs) are read into hardware such as the processor 1001 and the storage device 1002, so that the processor 1001 performs calculations and controls the communication of the communication device 1004 or controls at least one of the reading and writing of data in the storage device 1002 and the auxiliary storage device 1003.

[0133] Processor 1001 controls the entire computer by, for example, running an operating system. Processor 1001 may also be comprised of a central processing unit (CPU) that includes interfaces with peripheral devices, a control device, a computing device, registers, and the like. For example, control unit 140 and control unit 240 described above may also be implemented by processor 1001.

[0134] In addition, the processor 1001 reads 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 performs various processes based on the program. As a program, a program that causes the computer to execute at least a part of the operations described in the above embodiments is used. For example, Figure 13 The control unit 140 of the base station 10 shown may also be implemented by a control program stored in the storage device 1002 and executed in the processor 1001. Figure 14 The control unit 240 of the terminal 20 shown can also be implemented by a control program stored in the storage device 1002 and executed by the processor 1001. Although the various processes described above are performed by a single processor 1001, the various processes described above can also be performed simultaneously or sequentially by two or more processors 1001. The processor 1001 can also be implemented by one or more chips. In addition, the program can also be transmitted from the network via a telecommunications line.

[0135] The storage device 1002 is a computer-readable recording medium and may be composed of, for example, at least one of ROM (Read Only Memory), EPROM (Erasable Programmable ROM), EEPROM (Electrically Erasable Programmable ROM), and RAM (Random Access Memory). The storage device 1002 may also be referred to as a register, cache, or main memory (main storage device). The storage device 1002 can store executable programs (program code), software modules, and the like for implementing the communication method according to one embodiment of the present disclosure.

[0136] The auxiliary storage device 1003 is a computer-readable recording medium, and can be composed 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), a Floppy (registered trademark) disk, a magnetic stripe, etc. The above-mentioned storage medium can be, for example, a database, a server, or other appropriate medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0137] Communication device 1004 is hardware (a transceiver) used to communicate between computers via at least one of a wired network and a wireless network. It is also referred to as a network device, network controller, network card, or communication module. Communication device 1004 may include, for example, a high-frequency switch, a duplexer, a filter, a frequency synthesizer, and the like to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, communication device 1004 may also implement a transceiver antenna, an amplifier, a transceiver, a transmission path interface, and the like. The transceiver may also be implemented by physically or logically separating the transmitter and receiver.

[0138] The input device 1005 is an input device that receives input from the outside (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to the outside (e.g., a display, speaker, LED light, etc.). Alternatively, the input device 1005 and the output device 1006 may be integrally formed (e.g., a touch panel).

[0139] Furthermore, the processor 1001, the storage device 1002, and other devices are connected via a bus 1007 for communicating information. The bus 1007 may be configured using a single bus or different buses between devices.

[0140] Furthermore, the base station 10 and the terminal 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), or an FPGA (Field Programmable Gate Array), and may implement some or all of the functional blocks using this hardware. For example, the processor 1001 may be implemented using at least one of these hardware components.

[0141] Figure 16 2001 shows a structural example of a vehicle. Figure 16As shown, vehicle 2001 includes a drive unit 2002, a steering unit 2003, an accelerator pedal 2004, a brake pedal 2005, a shift lever 2006, front wheels 2007, rear wheels 2008, an axle 2009, an electronic control unit 2010, various sensors 2021 to 2029, an information service unit 2012, and a communication module 2013. The various forms and embodiments described in this disclosure may also be applied to a communication device mounted on vehicle 2001, such as communication module 2013.

[0142] The driving unit 2002 is composed of, for example, an engine, a motor, or a hybrid of an engine and a motor. The steering unit 2003 includes at least a steering wheel (also referred to as a steering wheel) and is configured to steer at least one of the front wheels and the rear wheels based on the user's operation of the steering wheel.

[0143] The electronic control unit 2010 is composed of a microprocessor 2031, a memory (ROM, RAM) 2032, and a communication port (IO port) 2033. Signals from various sensors 2021 to 2029 included in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be referred to as an ECU (Electronic Control Unit).

[0144] As signals from various sensors 2021 to 2029, there are current signals from the current sensor 2021 that senses the current of the motor, speed signals of the front and rear wheels obtained by the speed sensor 2022, air pressure signals of the front and rear wheels obtained by the air pressure sensor 2023, vehicle speed signals obtained by the vehicle speed sensor 2024, acceleration signals obtained by the acceleration sensor 2025, accelerator pedal depression amount signals obtained by the accelerator pedal sensor 2029, brake pedal depression amount signals obtained by the brake pedal sensor 2026, shift lever operation signals obtained by the shift lever sensor 2027, detection signals for detecting obstacles, vehicles, pedestrians, etc. obtained by the object detection sensor 2028, etc.

[0145] The information service unit 2012 is composed of various devices such as a car navigation system, audio system, speakers, televisions, and radios that provide (output) various information such as driving information, traffic information, and entertainment information, and one or more ECUs that control these devices. The information service unit 2012 uses information obtained from external devices via the communication module 2013 and other means to provide various multimedia information and multimedia services to the passengers of the vehicle 2001. The information service unit 2012 may include input devices that receive input from the outside (e.g., a keyboard, mouse, microphone, switches, buttons, sensors, touch panels, etc.) and output devices that provide output to the outside (e.g., a display, speakers, LED lights, touch panels, etc.).

[0146] Driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents or reducing the driver's driving load, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning devices (such as GNSS), map information (such as high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyroscope systems (such as IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, AI processors, and one or more ECUs that control these devices. In addition, driving assistance system unit 2030 sends and receives various information via communication module 2013 to implement driving assistance functions or autonomous driving functions.

[0147] The communication module 2013 can communicate with the microprocessor 2031 and components of the vehicle 2001 via the communication port. For example, the communication module 2013 can transmit and receive data via the communication port 2033 with the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, shift lever 2006, front wheels 2007, rear wheels 2008, axle 2009, microprocessor 2031 in the electronic control unit 2010, memory (ROM, RAM) 2032, and sensors 2021 to 2029 included in the vehicle 2001.

[0148] The communication module 2013 is controlled by the microprocessor 2031 of the electronic control unit 2010 and is a communication device capable of communicating with external devices. For example, various information can be transmitted and received with the external device via wireless communication. The communication module 2013 can be located inside or outside the electronic control unit 2010. The external device can also be, for example, a base station or a mobile station.

[0149] The communication module 2013 can transmit at least one of the signals input to the electronic control unit 2010 from the various sensors 2021-2028, information obtained based on these signals, and information based on external (user) input received via the information service unit 2012 to an external device via wireless communication. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, and the like can also be referred to as input units that receive input. For example, the PUSCH transmitted by the communication module 2013 can include information based on these inputs.

[0150] The communication module 2013 receives various information (traffic information, signal information, inter-vehicle information, etc.) transmitted from external devices and displays it on the information service unit 2012 included in the vehicle 2001. The information service unit 2012 can also be referred to as an output unit that outputs information (for example, outputs information to a display, speaker, or other device based on the PDSCH received by the communication module 2013 (or data / information decoded from the PDSCH)). Furthermore, the communication module 2013 stores various information received from external devices in a memory 2032 accessible to the microprocessor 2031. Based on the information stored in the memory 2032, the microprocessor 2031 can also control the drive unit 2002, steering unit 2003, accelerator pedal 2004, brake pedal 2005, gear lever 2006, front wheels 2007, rear wheels 2008, axles 2009, and sensors 2021 to 2029 included in the vehicle 2001.

[0151] (Summary of Implementation Methods)

[0152] As described above, according to an embodiment of the present invention, a network node is provided, which comprises: a receiving unit, which receives a message including a protocol data unit (PDU) session establishment request and a master node identifier corresponding to a first master node from an access and mobility management function (AMF); and a sending unit, which sends a message to a user plane function (UP) F sends a packet forwarding control protocol, i.e., PFCP session establishment request, so that the first master node carries the quality of service, i.e., QoS flow. The sending unit sends a first message to the AMF, and the first message includes a PDU session establishment permission, an indication of a request to set up a branch of a PDU session to other master nodes, and a master node identifier corresponding to the first master node. The receiving unit receives a second message from the AMF, and the second message includes information indicating the segmentation of the QoS flow and the master node identifier corresponding to the first master node. The sending unit sends a PFCP session change request to the UPF, so that the first master node carries a part of the QoS flow. The receiving unit receives a third message from the AMF, and the third message includes a PDU session change request and a master node identifier corresponding to the second master node. The sending unit sends a PFCP session change request to the UPF, so that the second master node carries a part of the QoS flow.

[0153] The above structure enables the configuration of dual MNs using different RATs, distributing or splitting QoS flows within the dual MNs. Furthermore, it enables new CM state management suitable for dual MNs. This allows for stable coverage during wireless system transitions.

[0154] Alternatively, the sending unit may include multiple master node permission indications in the first message. This configuration enables the establishment of dual MNs using different RATs, and the distribution or segmentation of QoS flows within the dual MNs. Furthermore, new CM state management and RM state management applicable to dual MNs can be performed.

[0155] Alternatively, the transmitting unit may include QoS flow splitting by the radio access network (RAN) in the first message. This configuration enables the configuration of dual MNs using different RATs, and the distribution or splitting of QoS flows within the dual MNs. Furthermore, new CM state management applicable to dual MNs is possible.

[0156] In addition, according to an embodiment of the present invention, a terminal is provided, comprising: a sending unit, which sends a protocol data unit, namely a PDU session establishment request, to a network, wherein the PDU session establishment request includes information related to access traffic guidance, switching, and segmentation, namely ATSSS, which is set with information indicating quality of service, namely QoS flow segmentation, based on a radio access network, namely RAN; a receiving unit, which receives from the network a PDU session change command for changing a PDU session established by the PDU session establishment request; and a control unit, which sets in-terminal rules based on information related to QoS flow segmentation between two RAN nodes set in an ASSS container information element, namely an ASSS container IE, included in the PDU session change command.

[0157] The above structure enables the configuration of dual MNs using different RATs, distributing or splitting QoS flows within the dual MNs. Furthermore, it enables new CM state management suitable for dual MNs. This allows for stable coverage during wireless system transitions.

[0158] In addition, according to an embodiment of the present invention, a communication method is provided, wherein a network node performs the following steps: receiving a message including a protocol data unit (PDU) session establishment request and a master node identifier corresponding to a first master node from an access and mobility management function (AMF); sending a packet forwarding control protocol (PFCP) session establishment request to a user plane function (UPF) so that the first master node carries a quality of service (QoS) flow; sending a first message to the AMF, the first message including a PDU session establishment permission, an indication of a request to set up a PDU session branch to other master nodes, and a master node identifier corresponding to the first master node; receiving a second message from the AMF, the second message including information indicating the split of the QoS flow and the master node identifier corresponding to the first master node; sending a PFCP session change request to the UPF so that the first master node carries a part of the QoS flow; receiving a third message from the AMF, the third message including a PDU session change request and a master node identifier corresponding to a second master node; and sending a PFCP session change request to the UPF so that the second master node carries a part of the QoS flow.

[0159] The above structure enables the configuration of dual MNs using different RATs, distributing or splitting QoS flows within the dual MNs. Furthermore, it enables new CM state management suitable for dual MNs. This allows for stable coverage during wireless system transitions.

[0160] (Supplementary Implementation Methods)

[0161] The above describes the embodiments of the present invention, but the disclosed invention is not limited to such embodiments, and those skilled in the art should understand various variations, modifications, alternatives, replacements, etc. In order to facilitate understanding of the invention, specific numerical examples are used for description, but unless otherwise specified, these numerical values are only examples, and any appropriate values can be used. The distinction between items in the above description is not essential to the present invention. You can combine and use the matters recorded in two or more items as needed, or you can apply the matters recorded in a certain item to the matters recorded in another item (as long as there is no contradiction). The boundaries of the functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of the physical components. The actions of multiple functional units can be performed by one physical component, or the actions of one functional unit can be performed by multiple physical components. Regarding the processing procedures described in the embodiments, the order of processing can be reversed if there is no contradiction. For the convenience of explaining the processing, the base station 10 and the terminal 20 are described using a functional block diagram, but such a device can also be implemented by hardware, software, or a combination thereof. The software that operates in accordance with the embodiments of the present invention through the processor of the base station 10 and the software that operates in accordance with the embodiments of the present invention through the processor of the terminal 20 can also be stored in random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, registers, hard disk (HDD), removable disk, CD-ROM, database, server and any other appropriate storage medium.

[0162] In addition, the notification of information is not limited to the form / implementation method described in the present disclosure, and other methods may also be used. For example, the notification of information may be implemented through physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), high-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 thereof. In addition, RRC signaling may be referred to as an RRC message, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, etc.

[0163] Each form / embodiment described in the present disclosure can also be applied to a mobile communication system using LTE (Long Term Evolution), LTE-A (LTE-Advanced), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), 6th generation mobile communication system (6G), xth generation mobile communication system (xG) (xG (x is, for example, an integer or a decimal)), FRA (Future Radio Access), NR (New Radio), New radio access (NX), Future generation radio access (FX), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE At least one of IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-WideBand), Bluetooth (registered trademark), other appropriate systems, and next-generation systems that are expanded, modified, created, or specified based on these systems. Furthermore, a combination of multiple systems (for example, a combination of at least one of LTE and LTE-A with 5G) may also be used.

[0164] The processing procedures, timings, and flows of each form / implementation described in this specification may be rearranged in order unless there is a conflict. For example, the methods described in this disclosure use an illustrative order to present the elements of various steps, but are not limited to the specific order presented.

[0165] In this specification, specific actions performed by base station 10 may also be performed by its upper node, depending on the situation. In a network consisting of one or more network nodes including base station 10, it is obvious that various actions performed for communication with terminal 20 can be performed by at least one of base station 10 and other network nodes other than base station 10 (e.g., MME or S-GW, but not limited to these). While the above example illustrates a single other network node other than base station 10, the other network node may also be a combination of multiple other network nodes (e.g., MME and S-GW).

[0166] The information or signals described in this disclosure can be output from a higher layer (or lower layer) to a lower layer (or higher layer), and can also be input and output via multiple network nodes.

[0167] Input or output information can be stored in a specific location (e.g., memory) or managed using a management table. Input or output information can be overwritten, updated, or appended. Output information can also be deleted. Input information can also be sent to other devices.

[0168] The determination in the present disclosure may be performed using a value represented by one bit (0 or 1), a Boolean value (Boolean: true or false), or a comparison of numerical values (for example, comparison with a predetermined value).

[0169] Software, whether referred to as software, firmware, middleware, microcode, hardware description language, or by other names, shall be interpreted broadly to refer to instructions, sets of instructions, code, code segments, program code, programs, subroutines, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, etc.

[0170] Furthermore, software, commands, information, and the like may be transmitted and received via a transmission medium. For example, if software is transmitted from a web page, server, or other remote source using at least one of a wired technology (coaxial cable, fiber optic cable, twisted pair, digital subscriber line (DSL), etc.) and a wireless technology (infrared, microwave, etc.), at least one of these wired and wireless technologies is included within the definition of a transmission medium.

[0171] The information, signals, etc. described in this disclosure may also be represented using any of a variety of different technologies. For example, data, commands, instructions, information, signals, bits, symbols, chips, etc. that may be referred to in the entire description may be represented by voltage, current, electromagnetic waves, magnetic fields or magnetic particles, light fields or photons, or any combination thereof.

[0172] In addition, the terms used in this disclosure and those necessary for understanding this disclosure may be replaced with terms having the same or similar meanings. For example, at least one of a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may also be referred to as a carrier frequency, a cell, or a frequency carrier.

[0173] As used in this disclosure, the terms "system" and "network" are used interchangeably.

[0174] In addition, the information, parameters, etc. described in this disclosure can be expressed using absolute values, relative values relative to predetermined values, or other corresponding information. For example, wireless resources can be indicated using indexes.

[0175] The names used for the above parameters are non-limiting in any respect. Furthermore, the formulas and the like using these parameters may sometimes differ from those explicitly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable names, and therefore the names assigned to these channels and information elements are non-limiting in any respect.

[0176] In this disclosure, terms such as "base station (BS)," "wireless base station," "base station apparatus," "fixed station," "NodeB," "eNodeB (eNB)," "gNodeB (gNB)," "access point," "transmission point," "reception point," "transmission / reception point," "cell," "sector," "cell group," "carrier," and "component carrier" are used interchangeably. Base stations are also sometimes referred to as macrocells, small cells, femtocells, and picocells.

[0177] A base station can accommodate one or more (for example, three) cells. When a base station accommodates multiple cells, the base station's overall coverage area can be divided into multiple smaller areas, each of which can also provide communication services through a base station subsystem (for example, a small base station for indoor use (RRH: Remote Radio Head)). Terms such as "cell" or "sector" refer to a portion or the entire coverage area of at least one of the base station and base station subsystem that provide communication services within the coverage area.

[0178] In the present disclosure, the base station sending information to the terminal may be replaced by the base station instructing the terminal to perform control / action based on the information.

[0179] In the present disclosure, terms such as “mobile station (MS)”, “user terminal”, “user equipment (UE)”, and “terminal” may be used interchangeably.

[0180] For mobile stations, those skilled in the art sometimes also use the following terms to refer to them: subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or some other appropriate terms.

[0181] At least one of the base station and the mobile station may also be referred to as a transmitting device, a receiving device, a communication device, etc. Furthermore, at least one of the base station and the mobile station may also be a device mounted on a mobile body, the mobile body itself, etc. The mobile body refers to an object that can move, and the moving speed is arbitrary. Furthermore, of course, this also includes situations where the mobile body is stationary. Examples of mobile bodies include, but are not limited to, vehicles, transport vehicles, cars, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, two-wheeled trailers (rear cars), rickshaws, ships and other watercraft, airplanes, rockets, artificial satellites, Drones (registered trademark), multi-rotor helicopters, quadcopters, balloons, and objects mounted thereon. Furthermore, the mobile body may also be a mobile body that moves autonomously based on operating instructions. It may be a means of transportation (such as a car, airplane, etc.), a mobile body that moves unmanned (such as a drone, self-driving car, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station also includes devices that do not necessarily move during communication operations. For example, at least one of the base station and the mobile station may be an IoT (Internet of Things) device such as a sensor.

[0182] In addition, the base station in the present disclosure can also be replaced by a user terminal. For example, the various forms / implementations of the present disclosure can also be applied to a structure in which the communication between the base station and the user terminal is replaced by the communication between multiple terminals 20 (for example, it can also be called D2D (Device-to-Device: device to device), V2X (Vehicle-to-Everything: vehicle to everything system), etc.). In this case, it can also be set as a structure in which the terminal 20 has the functions of the above-mentioned base station 10. In addition, terms such as "uplink" and "downlink" can also be replaced by terms corresponding to communication between terminals (such as "side"). For example, uplink channels, downlink channels, etc. can also be replaced by side channels.

[0183] Likewise, the user terminal in the present disclosure may be replaced by a base station. In this case, the base station may also have the functions of the user terminal.

[0184] As used in this disclosure, terms such as "determining" and "determining" sometimes encompass a variety of actions. For example, "determining" and "determining" may include considering as "judging" or "determining" an event that involves judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching a table, database, or other data structure), or ascertaining. Furthermore, "determining" and "determining" may include considering as "judging" or "determining" an event that involves receiving (e.g., receiving information), transmitting (e.g., transmitting information), inputting, outputting, or accessing (e.g., accessing data in a memory). Furthermore, "determining" and "determining" may include considering as "resolving," selecting, choosing, establishing, or comparing an event that involves "resolving" or "determining" an event that involves "resolving," selecting, choosing, establishing, or comparing. That is, "judgment" and "decision" may include matters where certain actions are considered to have been "judged" or "decided." In addition, "judgment (decision)" can also be replaced by "assuming (assuming)", "expecting (expecting)", "considering (considering)", etc.

[0185] The terms "connected", "coupled" or any variation of these terms are intended to indicate any direct or indirect connection or combination between two or more elements, and may include situations where there is one or more intermediate elements between two elements that are "connected" or "coupled" to each other. The combination or connection between elements may be a physical combination or connection, a logical combination or connection, or a combination of these. For example, "access" may be used instead of "connection". As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using at least one of one or more wires, cables and printed electrical connections, and as some non-limiting and non-inclusive examples, electromagnetic energy having wavelengths in the wireless frequency domain, microwave region and light (including both visible and invisible) region may be used to "connect" or "couple" to each other.

[0186] The reference signal may be referred to as RS (Reference Signal) for short, or may be called a pilot signal depending on the applied standard.

[0187] The phrase “based on” used in this disclosure does not mean “based only on” unless explicitly stated otherwise. In other words, the phrase “based on” means both “based only on” and “based at least on.”

[0188] Any reference to an element using the terms "first," "second," etc., as used in this disclosure, does not necessarily limit the number or order of these elements. These terms may be used in this disclosure as a convenient way to distinguish between two or more elements. Therefore, a reference to a first element and a second element does not mean that only two elements can be used or that the first element must precede the second element in any form.

[0189] The “unit” in the configuration of each of the above-mentioned devices may be replaced with a “section,” “circuit,” “device,” or the like.

[0190] When the terms "include," "including," and variations thereof are used in this disclosure, these terms, like the term "comprising," are intended to be inclusive. Furthermore, the term "or" used in this disclosure does not mean an exclusive or.

[0191] In the present disclosure, when an article is added by translation, such as a, an, and the in English, the present disclosure also includes cases where the noun following the article is in a plural form.

[0192] In this disclosure, the phrase "A and B are different" can mean "A and B are different from each other." Alternatively, the phrase can mean "A and B are each different from C." Terms such as "separate" and "combined" can also be interpreted in the same way as "different."

[0193] Each form / implementation described in this disclosure may be used individually or in combination, and may be switched between them depending on the execution. Furthermore, notification of predetermined information (e.g., notification of "yes X") is not limited to being performed explicitly, but may also be performed implicitly (e.g., not notifying the predetermined information).

[0194] While the present disclosure has been described in detail above, it should be clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in various modifications and variations without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is for illustrative purposes only and does not have any limiting meaning on the present disclosure.

[0195] Description of labels

[0196] 10: Base Station

[0197] 110: Sending Department

[0198] 120: Receiving Department

[0199] 130: Setting Department

[0200] 140: Control Department

[0201] 20: Terminal

[0202] 210: Sending Department

[0203] 220: Receiving Department

[0204] 230: Setting Department

[0205] 240: Control Department

[0206] 30: Network node

[0207] 1001: Processor

[0208] 1002: Storage device

[0209] 1003: Auxiliary storage device

[0210] 1004: Communication device

[0211] 1005: Input device

[0212] 1006: Output device

Claims

1. A network node, comprising: a receiving unit that receives a message including a protocol data unit (PDU) session establishment request and a master node identifier corresponding to the first master node from an access and mobility management function (AMF); and a sending unit, which sends a packet forwarding control protocol (PFCP) session establishment request to the user plane function (UPF) so that the first master node carries the quality of service (QoS) flow, The sending unit sends a first message to the AMF, wherein the first message includes a PDU session establishment permission, a request instruction for setting up a branch of a PDU session to another master node, and a master node identifier corresponding to the first master node. The receiving unit receives a second message from the AMF, the second message including information indicating the division of the QoS flow and a master node identifier corresponding to the first master node, The sending unit sends a PFCP session change request to the UPF to make the first master node carry a part of the QoS flow, The receiving unit receives a third message from the AMF, wherein the third message includes a PDU session change request and a master node identifier corresponding to the second master node. The sending unit sends a PFCP session change request to the UPF so that the second master node carries a part of the QoS flow.

2. The network node according to claim 1, wherein: The sending unit includes a plurality of master node permission instructions in the first message.

3. The network node according to claim 1, wherein: The transmitting unit includes QoS flow segmentation by a radio access network (RAN) in the first message.

4. A terminal comprising: a sending unit configured to send a protocol data unit (PDU) session establishment request to a network, the PDU session establishment request including information related to access traffic steering, switching, and splitting (ATSSS) in which information indicating quality of service (QoS) flow splitting based on a radio access network (RAN) is set; a receiving unit configured to receive, from the network, a PDU session change command for changing the PDU session established by the PDU session establishment request; as well as The control unit sets an in-terminal rule based on information related to QoS flow splitting between two RAN nodes set in the ATSSS container information element (AT SSS container IE) included in the PDU session change command.

5. A communication method, wherein: The following steps are performed by the network nodes: receiving, from an access and mobility management function (AMF), a message including a protocol data unit (PDU) session establishment request and a primary node identifier corresponding to the first primary node; Sending a packet forwarding control protocol (PFCP) session establishment request to a user plane function (UPF) to enable the first master node to carry a quality of service (QoS) flow; Sending a first message to the AMF, the first message including a PDU session establishment permission, an indication of another master node setting up a PDU session branch, and a master node identifier corresponding to the first master node; receiving a second message from the AMF, the second message including information indicating the split of the QoS flow and a master node identifier corresponding to the first master node; Sending a PFCP session change request to the UPF to enable the first master node to carry part of the QoS flow; receiving a third message from the AMF, the third message including a PDU session change request and a master node identifier corresponding to the second master node; as well as Send a PFCP session change request to the UPF to enable the second master node to carry part of the QoS flow.

Images