Network node and communication method

Abstract

In the present invention, a first network node included in a communication system comprises: a reception unit that receives, from a second network node, a notification of a change in a user plane; and a transmission unit that transmits, to a third network node, a message including information on the change in the user plane and a destination of a QoS flow changed on the basis of the change in the user plane.

Description

Network Node and Communication Method

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

[0002] In the 5G system of 3GPP (Registered Trademark) (3rd Generation Partnership Project), a service is defined in which the SMF (Session Management Function) notifies the AF (Application Function) (e.g., P-CSCF) of a change in the user plane, and the AF notifies the SMF whether to approve the user plane change (see, for example, Non-Patent Document 1).

[0003] When the user plane changes, the destination of the QoS flow associated with the application or service using this user plane may change. Further, when the user plane changes, the SMF may need to change the packet filter in the QoS rule using the destination of the QoS flow.

[0004] 3GPP TS 23.502 V18.7.0(2024-06)

[0005] However, in the conventional standard, there is no mechanism to notify the SMF of the destination of the QoS flow changed based on the change in the user plane. Therefore, when a change in the user plane occurs, there is a risk that the application or service associated with the QoS flow cannot be properly executed.

[0006] The first network node included in the communication system in this embodiment includes a receiving unit that receives a notification of a change in the user plane path from a second network node, and a transmitting unit that transmits a message including information regarding the change in the user plane path and the destination of the QoS flow changed based on the change in the user plane path to a third network node.

[0007] According to this embodiment, when the destination of a QoS flow changes due to a change in the user plane, information regarding the user plane path change and the changed destination of the QoS flow can be appropriately notified between network nodes.

[0008] This is a diagram illustrating an example of a communication system. This is a diagram illustrating an example of a communication system in a roaming environment. This is a diagram illustrating an example of an IMS data channel network. This is a sequence diagram showing an example of the operation procedure of the communication system in Example 1. This is a diagram showing an example of the definition of AppSessionContextUpdateDataPatch in Example 1. This is a diagram showing an example of the definition of SmPolicyNotification in Example 1. This is a sequence diagram showing an example of the operation procedure of the communication system in Example 2. This is a diagram showing an example of the definition of ascReqData (AppSessionContextUpdateData) included in AppSessionContextUpdateDataPatch in Example 2. This is a diagram showing an example of the definition of SmPolicyDecision included in SmPolicyNotification in Example 2. This is a sequence diagram showing an example of the operation procedure of the communication system in Example 3. This is a diagram showing an example of the functional configuration of a base station and network node in this embodiment. This is a diagram showing an example of the functional configuration of a terminal in this embodiment. This is a diagram showing an example of the hardware configuration of a base station, terminal and network node in this embodiment. This is a diagram showing an example of the vehicle configuration in this embodiment.

[0009] This embodiment will be described below with reference to the drawings. Note that the embodiments described below are examples, and the embodiments to which the present invention applies are not limited to those described below.

[0010] In the operation of the wireless communication system of this embodiment, existing technologies are used as appropriate. Existing technologies include, for example, existing communication methods based on the 3GPP standard, such as NR (New Radio) (5G) / 5GC (5G Core network). However, existing technologies are not limited to NR / 5GC, but also include LTE, LTE-Advanced and NR (5G) and later methods, or wireless LAN (Local Area Network).

[0011] In this embodiment, "configuring" wireless parameters means that predetermined values ​​are set in advance, or that wireless parameters notified by the network node or terminal 20 are set.

[0012] Figure 1 is a diagram illustrating an example of a communication system. As shown in Figure 1, the communication system consists of a terminal 20 (UE) and multiple network nodes. Hereafter, one network node will be assigned to each function, but one network node may implement multiple functions, or multiple network nodes may implement one function. Also, the "connection" described below may be a logical connection or a physical connection.

[0013] The RAN (Radio Access Network) is a network node having wireless access functionality, which may include a base station 10, and is connected to the UE, AMF (Access and Mobility Management Function), and UPF (User plane function). The AMF is a network node having functions such as terminating the RAN interface, terminating the NAS (Non-Access Stratum), registration management, connection management, reachability management, and terminal mobility management. The UPF is a network node interconnected with the DN (Data Network) and having functions related to user plane data processing, such as PDU (Protocol Data Unit) session point to the outside, packet routing and forwarding, and user plane QoS (Quality of Service) handling. The UPF and DN constitute a network slice. In the wireless communication network of this embodiment, multiple network slices are constructed.

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

[0015] SMF is a network node with functions such as session management, IP (Internet Protocol) address allocation and management for UEs, DHCP (Dynamic Host Configuration Protocol) functionality, ARP (Address Resolution Protocol) proxy, and roaming functionality. NEF is a network node with the function of notifying other NFs (Network Functions) of capabilities and events. NSSF is a network node with functions such as selecting the network slice to which the UE connects, determining the allowed NSSAI (Network Slice Selection Assistance Information), determining the NSSAI to be set, and determining the AMF set to which the UE connects. PCF is a network node with the function of controlling network policies. AF is a network node with the function of controlling application servers. NRF is a network node with the function of discovering NF instances that provide services. UDM is a network node that manages subscriber data and authentication data. UDM is connected to UDR (User Data Repository) which holds this data.

[0016] Figure 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Figure 2, the network consists of a terminal 20 (UE) and multiple network nodes. Hereafter, one network node will be assigned to each function, however, one network node may implement multiple functions, or multiple network nodes may implement one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0017] The RAN is a network node with wireless access capabilities and is connected to the UE, AMF, and UPF. The AMF is a network node with functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node interconnected with the DN, acting as a PDU session point to the outside world, routing and forwarding packets, and handling QoS for the user plane. The UPF and DN constitute a network slice. In the wireless communication network of this embodiment, multiple network slices are constructed.

[0018] AMF is connected to UE, RAN, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, AF, and SEPP (Security Edge Protection Proxy). AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes that are interconnected via interfaces based on their respective services: Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

[0019] SMF is a network node with functions such as session management, IP address allocation and management for UEs, DHCP functionality, ARP proxy, and roaming functionality. NEF is a network node with the function of notifying other NFs of capabilities and events. NSSF is a network node with functions such as selecting the network slice to which a UE connects, determining which NSSAIs are allowed, determining which NSSAIs are configured, and determining which AMF set a UE connects to. PCF is a network node with the function of controlling network policies. AF is a network node with the function of controlling application servers. NRF is a network node with the function of discovering NF instances that provide services. SEPP is an opaque proxy that filters control plane messages between PLMNs (Public Land Mobile Networks). vSEPP shown in Figure 2 is SEPP in the visited network, and hSEPP is SEPP in the home network.

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

[0021] Figure 3 is a diagram illustrating an example of an IMS data channel network. As shown in Figure 3, the IMS data channel network consists of a terminal 20 (UE) and multiple network nodes in both the originating network and the terminating network. Hereafter, one network node will be assigned to each function, however, one network node may implement multiple functions, or multiple network nodes may implement one function. Also, the "connection" described below may be a logical connection or a physical connection. A network node may have the following functions, for example.

[0022] IMS-AGW (Access Gateway) is a network node that functions as a gateway between the UE and the IMS network, and also has functions related to voice communication access processing.

[0023] P-CSCF (Proxy-Call Session Control Function) is a network node that provides proxy functionality between the UE and IMS network, as well as access control functions for voice communications.

[0024] S-CSCF (Serving-Call Session Control Function) is a network node that has functions related to session control for the User Agent (UE).

[0025] An I-CSCF (Interrogate-Call Session Control Function) is a network node in an IMS network that serves as a connection point between networks (e.g., a caller and a caller) and has functions such as forwarding received SIP requests to its own network's S-CSCF.

[0026] The IMS AS (IP Multimedia Subsystem Application Server) is a network node in the IMS network that has functions such as communicating with the DCSF (Data Channel Signalling Function) for event notification, and receiving data channel control instructions from the DCSF and communicating with the MF (Movement Function). The IMS AS also receives registration requests for communication termination points from the DCSF, converts the received registration requests into SIP Registers, and sends them to the S-CSCF (Serving-Call Session Control Function). Furthermore, the IMS AS converts data channel establishment requests received from the DCSF into SIP INVITEs and sends them to the S-CSCF.

[0027] DCSF (Data Channel Signaling Function) is a network node that receives event reports from IMS-AS and has functions such as deciding whether or not to allow the provision of data channel services, managing bootstrap data channels, and HTTP web server functionality.

[0028] A Media Function (MF) in an IMS network is a network node that performs functions such as media resource management and data channel media traffic forwarding. The MF processes media between the Data Channel Application Server (DCAS), which is the communication termination point, and the destination termination point, based on configuration information received from the Data Channel Application Server (DCSF). The MF may also be called a Data Channel Media Function (DCMF). Furthermore, the MF may also be called a Multimedia Resource Function (MRF).

[0029] DCAS (Data Channel Application Server) is a network node in the IMS network that has functions such as being a communication termination point for media and signaling.

[0030] 3GPP specifies a service in which the User Plane Facility (SMF) notifies the Air Firm (AF) (e.g., P-CSCF) of changes to the user plane, and the AF notifies the SMF whether or not it accepts the changes to the user plane.

[0031] The mechanisms for changing the user plane include (a) changing the PSA (PDU Session Anchor) via SSC Mode 2 or SSC Mode 3, and (b) adding or changing ULCL (Uplink Classifier) / L-PSA (Local-PSA).

[0032] (a) PSA changes via SSC Mode 2 or SSC Mode 3 are mechanisms for maintaining session continuity when changing the user plane path, and are effective in maintaining low-latency and highly reliable communication for UEs moving in a MEC (Multi-access Edge Computing) environment.

[0033] (b) Addition or modification of ULCL / L-PSA is a mechanism used in MEC environments to balance UE mobility and QoS (Quality of Service).

[0034] In either case (a) or (b) above, a change in the user plane may result in a change in the destination of a specific QoS flow.

[0035] For example, in satellite constellation communications, the ULCL / L-PSA for QoS flows corresponding to voice media changes, the destination IMS AGW changes, and consequently the termination point set in the IMS AGW also changes. In edge communications, the PSA for QoS flows connecting to the EAS (Edge Application Server) changes depending on SSC mode 2 or SSC mode 3, the destination EAS for the QoS flow changes, and consequently the termination point set in the EAS also changes.

[0036] Here, in both cases (a) and (b), it is necessary to change the packet filter within the QoS rule in the terminal. Furthermore, in case (b), it is necessary to change the packet filter within the ULCL within the ULCL. Due to these packet filter changes, the SMF needs to identify the destination of the modified QoS flow, but the conventional standard does not have a mechanism to notify the SMF of the destination of the QoS flow that will be changed based on the user plane change. Furthermore, since the destination of the QoS flow is set in the PCC rule, it should be notified from the AF to the SMF via the PCF, but the conventional standard does not have a mechanism for the PCF to obtain information indicating whether the AF has approved the user plane change.

[0037] According to this embodiment, when the destination of a QoS flow changes due to a user plane change in a communication system, information regarding the user plane change and the change in the destination of the QoS flow can be appropriately notified between network nodes.

[0038] The QoS flow in this embodiment may be, for example, a QoS flow corresponding to voice media in satellite constellation communication, a QoS flow connected to an EAS (Edge Application Server) in edge communication, or a QoS flow associated with any application (service). The destination of the QoS flow is the endpoint of the data flow to which QoS is applied. By specifying the destination of the QoS flow, appropriate QoS is applied to a specific application or service.

[0039] The following describes each embodiment of this model.

[0040] Before the first step (S101, S201, S301) of the sequence diagrams for each embodiment (Figures 4, 7, and 10), the AF (e.g., P-CSCF 50) receives an Nsmf_EventExposure_Notify request from the SMF 30. The Nsmf_EventExposure_Notify request is used by the SMF 30 to notify the AF of events related to the user plane. The Nsmf_EventExposure_Notify request contains a data structure called NsmfEventExposureNotification, which contains eventNotifs and ackUri.

[0041] eventNotifs displays a list of events that have occurred and includes the parameter "event" which specifies the type of event. In this embodiment, "UP_PATH_CH" is specified for "event" to indicate that a change in the user plane path has occurred. ackUri is the URI for which AF sends acknowledgment information for the event.

[0042] Thus, in each embodiment, in advance, the SMF 30 notifies the AF (P-CSCF 50) of a URI specified by an ackUri indicating a change in the user plane path and a transmission destination of approval information for this change.

[0043] (Embodiment 1) According to Embodiment 1, the AF (for example, P-CSCF 50) receives a message notifying a change in the user plane path from the SMF 30 and recognizes that the destination of a specific QoS flow changes along with the change in the user plane path. The P-CSCF 50 transmits a message including the destination after the change of the specific QoS flow, information for approving the change in the user plane path, and an end point for receiving information for the SMF 30 to approve the change in the user plane path to the PCF 40. The change in the user plane path is an example of the change in the user plane.

[0044] An example of the operation of the communication system of Embodiment 1 is shown in FIG. 4.

[0045] In step S101, the P-CSCF 50 transmits an Npcf_PolicyAuthorization_Update request to the PCF 40. The Npcf_PolicyAuthorization_Update request is a message used for the AF (P-CSCF 50) to request the PCF 40 to update the policy.

[0046] The Npcf_PolicyAuthorization_Update request includes an AppSessionContextUpdateDataPatch.

[0047] The AppSessionContextUpdateDataPatch stores update data of the application session context. As shown in FIG. 5, the AppSessionContextUpdateDataPatch includes ascReqData, appRelocAck (=AckOfNotify), and appRelocAckUri (=ackUri).

[0048] In Embodiment 1, in AppSessionContextUpdateDataPatch, ascReqData, appRelocAck, and appRelocAckUri are set as different information elements (attributes). appRelocAck and appRelocAckUri are information elements newly added to AppSessionContextUpdateDataPatch in this embodiment.

[0049] ascReqData describes the requested updates to the service requirements of individual application session contexts. ascReqData is data that includes information such as the destination change of the QoS flow used by the application. The application session context is used to transmit the QoS requirements of the application between the AF (P-CSCF 50) and the PCF 40. ascReqData is data for updating this context and is represented, for example, by a data structure called AppSessionContextUpdateData. This data structure (Data type) includes, for example, medComponents that include QoS flow information.

[0050] appRelocAck describes the approval information of the AF related to the "UP_PATH_CH" event of the SMF 30. The "UP_PATH_CH" event is an event used when the SMF 30 notifies the AF of the change in the user plane path. appRelocAck is information indicating whether the AF has approved or not approved the change in the user plane path and is represented by a data structure called AckOfNotify. This data structure includes, for example, information indicating an affirmative response (ACKNOWLEDGEMENT) or a negative response (NEGATIVE_ACKNOWLEDGEMENT) and information indicating the reason for the response.

[0051] appRelocAckUri is a URI (Uniform Resource Identifier) ​​provided by SMF for AF authorization related to "UP_PATH_CH" in SMF 30. appRelocAckUri is the URI that AF uses to send authorization information for the "UP_PATH_CH" event to SMF 30. appRelocAckUri is represented by a data structure called AckUri. That is, the URI is specified by AckUri and is the endpoint to which authorization information is sent.

[0052] In step S102 of Figure 4, PCF 40 sends the Npcf_PolicyAuthorization_Update response to P-CSCF 50.

[0053] The Npcf_PolicyAuthorization_Update response is the message that PCF 40 uses to return a response to an AF regarding a policy update request. This response may include a status code indicating the success or failure of the request.

[0054] In step S103, PCF 40 sends an Npcf_SMPolicyControl_UpdateNotify request to SMF 30.

[0055] The Npcf_SMPolicyControl_UpdateNotify request is a message used by PCF 40 to notify SMF 30 of policy updates. The Npcf_SMPolicyControl_UpdateNotify request includes SmPolicyNotification.

[0056] SmPolicyNotification contains information for notifying of policy changes. SmPolicyNotification includes, for example, resourceUri, smPolicyDecision, appRelocAck, and appRelocAckUri, as shown in Figure 6.

[0057] In Example 1, resourceUri, smPolicyDecision, appRelocAck, and appRelocAckUri are each set as different information elements (attributes) in SmPolicyNotification. appRelocAck and appRelocAckUri are new information elements added to SmPolicyNotification in this embodiment.

[0058] The resourceUri is the resource URI of the individual SM policy resource related to the notification. It is the information used to identify which SM policy was updated within the Npcf_SMPolicyControl_UpdateNotify request.

[0059] smPolicyDecision is information about the session management policy determined by PCF 40. SmPolicyDecision includes PCC rules that contain QoS flow information. PCF 40 creates this SmPolicyDecision based on the Npcf_PolicyAuthorization_Update request received from AF (P-CSCF 50) and sends it to SMF 30.

[0060] appRelocAck describes AF (Airframe Assistance) authorization information related to the SMF 30's “UP_PATH_CH” event. The “UP_PATH_CH” event is used by SMF 30 to notify AF of a change in the user plane path. appRelocAck indicates whether AF has authorized the change in the user plane path and is represented by a data structure called AckOfNotify. This data structure includes information indicating an acknowledgment or negative acknowledgment and information indicating the reason for the response.

[0061] The same value as the appRelocAck received from AF (P-CSCF 50) in step S101 is set for appRelocAck (=AckOfNotify).

[0062] appRelocAckUri is a URI provided by SMF 30 for AF authorization related to "UP_PATH_CH" in SMF 30. appRelocAckUri is represented by a data structure called AckUri.

[0063] The same value as the appRelocAckUri received from AF in step S101 is set for appRelocAckUri (=ackUri).

[0064] In step S104 of Figure 4, SMF 30 sends an Npcf_SMPolicyControl_UpdateNotify response to PCF 40.

[0065] The Npcf_SMPolicyControl_UpdateNotify response is the message that SMF 20 uses to return a response to the PCF regarding a policy update notification. The response includes a status code indicating whether the notification was received successfully or unsuccessfully.

[0066] (Example 2) Figure 7 is a sequence diagram showing an example of the operation of the communication system in Example 2. In Figure 7, the meaning of the message name and information element name in each step is the same as the meaning of the message name and information element name in the corresponding Figure 4.

[0067] In step S201, P-CSCF 50 sends an Npcf_PolicyAuthorization_Update request to PCF 40. The Npcf_PolicyAuthorization_Update request includes an AppSessionContextUpdateDataPatch. The AppSessionContextUpdateDataPatch includes ascReqData. In Example 2, unlike Example 1, ascReqData (AppSessionContextUpdateData) includes appRelocAck (=AckOfNotify) and appRelocAckUri (=ackUri), as shown in Figure 8. Figure 8 shows an example of the definition of AppSessionContextUpdateData in Example 2.

[0068] In step S202, PCF 40 sends the Npcf_PolicyAuthorization_Update response to P-CSCF 50.

[0069] In step S203, PCF 40 sends an Npcf_SMPolicyControl_UpdateNotify request to SMF 30. The Npcf_SMPolicyControl_UpdateNotify request includes SmPolicyNotification. SmPolicyNotification includes SmPolicyDecision. In Example 2, unlike Example 1, as shown in Figure 9, SmPolicyDecision includes appRelocAck (=AckOfNotify) and appRelocAckUri (=ackUri).

[0070] In step S204, SMF 30 sends an Npcf_SMPolicyControl_UpdateNotify response to PCF 40.

[0071] (Example 3) Figure 10 is a sequence diagram showing an example of the operation of the communication system in Example 3. In Figure 10, the meaning of the message name and information element name in each step is the same as the meaning of the message name and information element name in the corresponding Figure 4 or Figure 7.

[0072] Steps S301-S302 in Figure 10 are the same as steps S101-S102 in Figure 4 (Example 1). Steps S301-S304 in Figure 10 may be the same as steps S201-S202 in Figure 7 (Example 2).

[0073] In step S303 of Figure 10, PCF 40 sends an Npcf_SMPolicyControl_UpdateNotify request (SmPolicyNotification(SmPolicyDecision)) to SMF 30. SmPolicyNotification contains information indicating the destination of the QoS flow that has been changed based on the change in the user plane path.

[0074] In step S304, SMF 30 sends an Npcf_SMPolicyControl_UpdateNotify response to PCF 40 as a response to the request in step S303.

[0075] In step S305, PCF 40 sends an Nsmf_EventExposure_AppRelocationInfo request (AckOfNotify) to SMF 30. AckOfNotify is information indicating whether the user plane path change has been approved. Thus, according to Embodiment 3, the information indicating whether the user plane path change has been approved and the destination of the changed QoS flow are sent in different messages.

[0076] In step S306, SMF 30 sends the Nsmf_EventExposure_AppRelocationInfo response to PCF 40 as a response to the request in step S305.

[0077] According to the embodiment described above, when the destination of a QoS flow changes in a communication system based on a change in the user plane path, information regarding the change in the user plane path and the changed destination of the QoS flow can be appropriately notified between network nodes.

[0078] (Device Configuration) Next, an example of the functional configuration of the base station 10, network node (e.g., SMF 30, PCF 40, P-CSCF 50), and terminal 20 that perform the processing and operations described above will be explained. The base station 10, network node, and terminal 20 include the functions that implement the embodiments described above. However, the base station 10, network node, and terminal 20 may each have only some of the functions in the embodiments.

[0079] <Base Station and Network Nodes> Figure 11 shows an example of the functional configuration of a base station 10 and a network node. As shown in Figure 11, the base station 10 has a transmitting unit 110, a receiving unit 120, a setting unit 130, and a control unit 140. The functional configuration shown in Figure 11 is merely an example. The functional classifications and names of the functional units can be anything as long as they can perform the operation according to this embodiment. Note that the network node may have the same functional configuration as the base station 10. Furthermore, a network node having multiple different functions on the system architecture may be composed of multiple network nodes separated by function.

[0080] The transmitting unit 110 includes the function of generating a signal to be transmitted to the terminal 20 or other network node and transmitting the signal by wire or wireless. The receiving unit 120 includes the function of receiving various signals transmitted from the terminal 20 or other network node and obtaining information from the received signal, for example, information of a higher layer. A communication unit including the transmitting unit 110 and the receiving unit 120 may be configured.

[0081] The setting unit 130 stores pre-configured setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads them from the storage device as needed.

[0082] The control unit 140 performs the processes described in the embodiment. The control unit 140 also performs processing related to communication with the terminal 20. The signal transmission function in the control unit 140 may be included in the transmission unit 110, and the signal reception function in the control unit 140 may be included in the reception unit 120.

[0083] <Terminal> Figure 12 shows an example of the functional configuration of terminal 20. As shown in Figure 12, terminal 20 has a transmitting unit 210, a receiving unit 220, a setting unit 230, and a control unit 240. The functional configuration shown in Figure 12 is just one example. The functional classifications and names of the functional units can be anything as long as they can perform the operation according to this embodiment. In addition, the communication device that becomes the resource holder 20 may have a functional configuration similar to that of terminal 20.

[0084] The transmitting unit 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiving unit 220 wirelessly receives various signals and obtains signals from higher layers from the received physical layer signals. The receiving unit 220 also has the function of receiving control signals or reference signals transmitted from network nodes. A communication unit including the transmitting unit 210 and the receiving unit 220 may be configured.

[0085] The setting unit 230 stores various setting information received from network nodes by the receiving unit 220 in a storage device and reads it from the storage device as needed. The setting unit 230 also stores pre-configured setting information.

[0086] The control unit 240 performs the processing described in the embodiment. The signal transmission function in the control unit 240 may be included in the transmission unit 210, and the signal reception function in the control unit 240 may be included in the reception unit 220.

[0087] (Hardware Configuration) The block diagrams (Figures 11 and 12) used in the description of the above embodiments show functional units. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method of realizing each functional block is not particularly limited. That is, each functional block may be realized using one device that is physically or logically coupled, or it may be realized using two or more physically or logically separated devices that are directly or indirectly connected (for example, using wired or wireless connections). A functional block may be realized by combining the one device or the multiple devices with software.

[0088] Functions include, but are not limited to, judgment, decision, determination, calculation, calculation, processing, derivation, investigation, exploration, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, assumption, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating (mapping), and assigning. For example, a functional block (configuration part) that enables transmission is called a transmitting unit or transmitter. In all cases, as mentioned above, the method of implementation is not particularly limited.

[0089] For example, the base station 10, network node, terminal 20, etc. in one embodiment of the present disclosure may function as a computer that processes the wireless communication method of the present disclosure. Figure 13 is a diagram showing an example of the hardware configuration of the base station 10 and terminal 20 according to one embodiment of the present disclosure. The network node may have a hardware configuration similar to that of the base station 10. The base station 10 and terminal 20 described above may be physically configured as a computer device 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, etc.

[0090] In the following explanation, the term "device" can be read as "circuit," "device," "unit," etc. The hardware configuration of the base station 10 and terminal 20 may include one or more of the devices shown in the figure, or it may be configured without some of the devices.

[0091] Each function in the base station 10 and terminal 20 is realized by loading predetermined software (programs) onto hardware such as the processor 1001 and storage device 1002, which allows the processor 1001 to perform calculations, control communication by the communication device 1004, and control at least one of the reading and writing of data in the storage device 1002 and auxiliary storage device 1003.

[0092] The processor 1001 controls the entire computer, for example, by running an operating system. The processor 1001 may consist of a central processing unit (CPU) that includes interfaces with peripheral devices, control devices, arithmetic units, registers, etc. For example, the control unit 140, control unit 240, etc., described above may be implemented by the processor 1001.

[0093] Furthermore, the processor 1001 reads programs (program code), software modules, or data from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002, and executes various processes accordingly. The program used is one that causes the computer to execute at least a part of the operations described in the above embodiment. For example, the control unit 140 of the base station 10 shown in Figure 11 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Also, for example, the control unit 240 of the terminal 20 shown in Figure 12 may be implemented by a control program stored in the storage device 1002 and operated by the processor 1001. Although the above-described processes have been explained as being executed by one processor 1001, they may be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The program may also be transmitted from the network via a telecommunications line.

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

[0095] The auxiliary storage device 1003 is a computer-readable recording medium and may consist of at least one of the following: an optical disc such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital multipurpose disk, a Blu-ray® disk), a smart card, flash memory (e.g., a card, a stick, a key drive), a floppy® disk, a magnetic strip, etc. The above-mentioned storage medium may also be a database, server, or other suitable medium that includes at least one of the storage device 1002 and the auxiliary storage device 1003.

[0096] The communication device 1004 is hardware (transmitting / receiving device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as a network device, network controller, network card, communication module, etc. The communication device 1004 may be configured to include, for example, a high-frequency switch, duplexer, filter, frequency synthesizer, etc., in order to implement at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, the transmitting and receiving antenna, amplifier section, transmitting and receiving section, transmission path interface, etc., may be implemented by the communication device 1004. The transmitting and receiving section may be implemented in a physically or logically separated manner, with a transmitting section and a receiving section.

[0097] The input device 1005 is an input device that accepts input from an external source (e.g., a keyboard, mouse, microphone, switch, button, sensor, etc.). The output device 1006 is an output device that outputs to an external source (e.g., a display, speaker, LED lamp, etc.). The input device 1005 and the output device 1006 may be configured as an integrated unit (e.g., a touch panel).

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

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

[0100] Figure 14 shows an example of the configuration of vehicle 2001. As shown in Figure 14, 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. Each aspect / embodiment described in this disclosure may be applied to a communication device mounted on vehicle 2001, for example, to the communication module 2013.

[0101] The drive unit 2002 consists 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 called a handle) and is configured to steer at least one of the front wheels and the rear wheels based on the operation of the steering wheel, which is operated by the user.

[0102] The electronic control unit 2010 consists of a microprocessor 2031, memory (ROM, RAM) 2032, and communication ports (IO ports) 2033. Signals from various sensors 2021 to 2029 installed in the vehicle 2001 are input to the electronic control unit 2010. The electronic control unit 2010 may also be called an ECU (Electronic Control Unit).

[0103] Signals from various sensors 2021 to 2029 include current signals from current sensor 2021 for sensing motor current, front and rear wheel rotation speed signals acquired by rotation speed sensor 2022, front and rear wheel air pressure signals acquired by air pressure sensor 2023, vehicle speed signals acquired by vehicle speed sensor 2024, acceleration signals acquired by acceleration sensor 2025, accelerator pedal depression signals acquired by accelerator pedal sensor 2029, brake pedal depression signals acquired by brake pedal sensor 2026, shift lever operation signals acquired by shift lever sensor 2027, and detection signals acquired by object detection sensor 2028 for detecting obstacles, vehicles, pedestrians, etc.

[0104] The Information Service Unit 2012 consists of various devices for providing (outputting) various types of information such as driving information, traffic information, and entertainment information, including a car navigation system, audio system, speakers, television, and radio, and one or more ECUs that control these devices. The Information Service Unit 2012 uses information acquired from external devices via a communication module 2013, etc., to provide various multimedia information and multimedia services to the occupants of the vehicle 2001. The Information Service Unit 2012 may include input devices that accept input from the outside (e.g., keyboard, mouse, microphone, switch, button, sensor, touch panel, etc.) and output devices that perform output to the outside (e.g., display, speaker, LED lamp, touch panel, etc.).

[0105] The driver assistance system unit 2030 consists of various devices that provide functions to prevent accidents or reduce the driver's workload, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System)), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. The driver assistance system unit 2030 also transmits and receives various information via the communication module 2013 to realize driver assistance functions or autonomous driving functions.

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

[0107] The communication module 2013 is a communication device that can be controlled by the microprocessor 2031 of the electronic control unit 2010 and can communicate with external devices. For example, it can send and receive various types of information with external devices via wireless communication. The communication module 2013 may be located either inside or outside the electronic control unit 2010. The external device may be, for example, a base station or a mobile station.

[0108] The communication module 2013 may transmit at least one of the following to an external device via wireless communication: signals from the various sensors 2021-2028 input to the electronic control unit 2010, information obtained based on said signals, and information based on input from an external source (user) obtained via the information service unit 2012. The electronic control unit 2010, the various sensors 2021-2028, the information service unit 2012, etc., may also be called input units that accept input. For example, the PUSCH transmitted by the communication module 2013 may include the information based on the above input.

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

[0110] <Note> (Note 1) A first network node included in a communication system, comprising: a receiving unit that receives notification of a user plane change from a second network node; and a transmitting unit that transmits a message to a third network node that includes information regarding the user plane change and the destination of the QoS flow changed based on the user plane change.

[0111] (Note 2) The first network node as described in Note 1, wherein the information relating to the user plane change includes approval information indicating whether the first network node has approved the user plane change and information indicating the destination of the approval information.

[0112] (Note 3) The first network node described in Note 1, wherein the second network node is a network node that manages user plane sessions, and the third network node is a network node that performs policy control.

[0113] (Note 4) The QoS flow is a QoS flow corresponding to voice media in satellite constellation communications or a QoS flow connected to an EAS (Edge Application Server) in edge communications, as described in Note 1, for the network node.

[0114] (Appendix 5) A third network node comprising: a receiving unit that receives a message from a first network node including approval information indicating whether the first network node has approved a change to the user plane, the destination of the QoS flow changed based on the change to the user plane, and information indicating the destination of the approval information; and a transmitting unit that transmits a first message to a second network node including the destination of the QoS flow after the change, wherein the destination of the approval information is a terminal point at the second network node, and the transmitting unit transmits a second message including the approval information to the terminal point.

[0115] (Appendix 6) A communication method performed by a first network node included in a communication system, comprising: receiving a notification of a change in the user plane from a second network node; and sending a message to a third network node containing information about the change in the user plane and the destination of a QoS flow changed based on the change in the user plane.

[0116] In any of the provisions of Appendix 1-6, when a user plane change results in a change in the destination of a QoS flow, network nodes can appropriately notify each other of information regarding the user plane path change and the changed destination of the QoS flow.

[0117] (Supplement to Embodiments) Although these embodiments have been described above, the disclosed invention is not limited to these embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, substitutions, etc. Specific numerical examples have been used to facilitate understanding of the invention, but unless otherwise specified, these numerical values ​​are merely examples, and any appropriate values ​​may be used. The division of items in the above description is not essential to the present invention, and matters described in two or more items may be combined as needed, and matters described in one item may be applied to matters described in another item (as long as they do not contradict each other). The boundaries of functional units or processing units in the functional block diagram do not necessarily correspond to the boundaries of physical parts. The operation of multiple functional units may be physically performed by one part, or the operation of one functional unit may be physically performed by multiple parts. The processing procedures described in the embodiments may be rearranged as long as they do not contradict each other. For the convenience of explaining the processing, the base station 10 and terminal 20 have been described using functional block diagrams, but such devices may be realized in hardware, software, or a combination thereof. The software operated by the processor of the base station 10 according to this embodiment and the software operated by the processor of the terminal 20 according to this embodiment may be stored in any suitable storage medium such as random access memory (RAM), flash memory, read-only memory (ROM), EPROM, EEPROM, register, hard disk (HDD), removable disk, CD-ROM, database, server, or other appropriate storage medium.

[0118] Furthermore, notification of information is not limited to the embodiments described herein and may be carried out by other means. For example, notification of information may be carried out by physical layer signaling (e.g., DCI (Downlink Control Information), UCI (Uplink Control Information)), upper 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 combinations thereof. Also, RRC signaling may be called RRC messages, and may be, for example, RRC Connection Setup messages, RRC Connection Reconfiguration messages, etc.

[0119] Each aspect / embodiment described in this disclosure refers to 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 (where x is, for example, an integer or 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 802.16 (WiMAX (registered trademark)), IEEE 802.20 may apply to at least one system utilizing UWB (Ultra-WideBand), Bluetooth®, or other appropriate systems, and to next-generation systems extended, modified, created, or defined based thereon. Alternatively, multiple systems may be applied in combination (e.g., a combination of at least one of LTE and LTE-A with 5G).

[0120] The processing procedures, sequences, flowcharts, etc., of each aspect / embodiment described herein may be reordered, provided they are consistent with each other. For example, the methods described herein present various step elements in an exemplary order and are not limited to that specific order.

[0121] In this specification, specific operations performed by the base station 10 may, in some cases, be performed by its upper node. In a network consisting of one or more network nodes having a base station 10, it is clear that various operations performed for communication with the terminal 20 can be performed by the base station 10 and at least one of the other network nodes (for example, an MME or S-GW, but not limited to these). Although the above example illustrates the case where there is one other network node besides the base station 10, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

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

[0123] Input and output information may be stored in a specific location (e.g., memory) or managed using a management table. Input and output information may be overwritten, updated, or appended to. Output information may be deleted. Input information may be transmitted to other devices.

[0124] The determination in this disclosure may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a numerical comparison (for example, a comparison with a predetermined value).

[0125] Software should be broadly interpreted to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, execution threads, procedures, functions, and so on, whether they are called software, firmware, middleware, microcode, hardware description languages, or by any other name.

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

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

[0128] In addition, terms used in this disclosure and terms necessary for understanding this 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). Also, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, cell, frequency carrier, etc.

[0129] The terms “system” and “network” as used in this disclosure are interchangeable.

[0130] Furthermore, the information, parameters, etc., described in this disclosure may be expressed using absolute values, relative values ​​from a given value, or other corresponding information. For example, wireless resources may be indicated by an index.

[0131] The names used for the parameters described above are not restrictive in any way. Furthermore, the formulas and other expressions using these parameters may differ from those expressly disclosed in this disclosure. Various channels (e.g., PUCCH, PDCCH, etc.) and information elements can be identified by any suitable name, and therefore, the various names assigned to these various channels and information elements are not restrictive in any way.

[0132] In this disclosure, terms such as "Base Station (BS)", "wireless base station", "base station equipment", "fixed station", "NodeB", "eNodeB (eNB)", "gNodeB (gNB)", "access point", "transmission point", "reception point", "transmission / reception point", "cell", "sector", "cell group", "carrier", and "component carrier" may be used interchangeably. Base stations may also be referred to by terms such as macrocell, small cell, femtocell, and picocell.

[0133] A base station can accommodate one or more (e.g., three) cells. If a base station accommodates multiple cells, the entire coverage area of ​​the base station can be divided into multiple smaller areas, each of which may also be provided with communication services by a base station subsystem (e.g., a Remote Radio Head (RRH)). The terms “cell” or “sector” refer to part or all of the coverage area of ​​at least one of the base station and / or base station subsystems that provide communication services in that coverage.

[0134] In this disclosure, the transmission of information by a base station to a terminal may be interpreted as the base station instructing the terminal to perform control or operation based on the information.

[0135] In this disclosure, terms such as "Mobile Station (MS)," "user terminal," "User Equipment (UE)," and "terminal" may be used interchangeably.

[0136] A mobile station may also be referred to by those skilled in the art as a subscriber station, mobile unit, subscriber unit, wireless unit, remote unit, mobile device, wireless device, wireless communication device, remote device, mobile subscriber station, access terminal, mobile terminal, wireless terminal, remote terminal, handset, user agent, mobile client, client, or several other appropriate terms.

[0137] At least one of the base station and the mobile station may be called a transmitting device, a receiving device, a communication device, etc. 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 a movable object, and its speed of movement is arbitrary. This also includes the case when the mobile body is stationary. The mobile body includes, but is not limited to, vehicles, transport vehicles, automobiles, motorcycles, bicycles, connected cars, excavators, bulldozers, wheel loaders, dump trucks, forklifts, trains, buses, handcarts, rickshaws, ships and other watercraft, airplanes, rockets, satellites, drones (registered trademark), multicopters, quadcopters, balloons, and items mounted on them. The mobile body may also be a mobile body that moves autonomously based on operation commands. It may be a vehicle (e.g., a car, an airplane, etc.), an unmanned mobile body (e.g., a drone, an autonomous vehicle, etc.), or a robot (manned or unmanned). Furthermore, at least one of the base station and the mobile station may include 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.

[0138] Furthermore, the term "base station" in this disclosure may be interpreted as "user terminal." For example, the various aspects / embodiments of this disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, D2D (Device-to-Device), V2X (Vehicle-to-Everything)). In this case, the terminals 20 may have the functions that the base station 10 has. Also, terms such as "uplink" and "downlink" may be interpreted as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, uplink channel, downlink channel, etc., may be interpreted as side channel.

[0139] Similarly, the term "user terminal" in this disclosure may be replaced with "base station." In this case, the base station may be configured to have the same functions as the user terminal described above.

[0140] As used in this disclosure, the terms “determining” and “determining” may encompass a wide variety of actions. “Determining” may include, for example, judging, calculating, computing, processing, deriving, investigating, looking up, searching, or inquiring (e.g., searching in a table, database, or other data structure), or ascertaining. “Determining” may also include receiving (e.g., receiving information), transmitting (e.g., sending information), inputting, outputting, or accessing (e.g., accessing data in memory). Furthermore, "judgment" and "decision" can include considering something as having been "judged" or "decided" after resolving, selecting, choosing, establishing, comparing, etc. In other words, "judgment" and "decision" can include considering something as having been "judged" or "decided" after some action. Also, "judgment (decision)" can be reinterpreted as "assuming," "expecting," or "considering."

[0141] The terms “connected,” “coupled,” or any variation thereof, mean any direct or indirect connection or coupling between two or more elements, and may include the presence of one or more intermediate elements between two elements that are “connected” or “coupled” with each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, “connection” may be reinterpreted as “access.” As used in this disclosure, two elements may be considered to be “connected” or “coupled” with each other using at least one of one or more wires, cables, and printed electrical connections, and, in some non-limiting and non-exclusive examples, electromagnetic energy having wavelengths in the radio frequency domain, microwave domain, and optical (both visible and invisible) domain.

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

[0143] In this disclosure, the phrase "based on" does not mean "based solely on" unless otherwise specified. In other words, the phrase "based on" means both "based solely on" and "based at least on."

[0144] Any reference to elements using the designations “first,” “second,” etc., as used in this disclosure does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient way to distinguish between two or more elements. Accordingly, references to the first and second elements do not imply that only two elements may be employed, or that the first element must precede the second element in any way.

[0145] In the configuration of each of the above devices, "means" may be replaced with "part," "circuit," "device," etc.

[0146] Where the terms “include,” “including,” and variations thereof are used in this disclosure, these terms are intended to be inclusive, as is the term “comprising.” Furthermore, the term “or” as used in this disclosure is not intended to mean exclusive OR.

[0147] In this disclosure, if articles are added through translation, such as a, an, and the in English, this disclosure may include the fact that the noun following these articles is plural.

[0148] In this disclosure, the term "A and B are different" may mean "A and B are different from each other." The term may also mean "A and B are each different from C." Terms such as "separate" and "combine" may be interpreted similarly to "different."

[0149] Each aspect / embodiment described in this disclosure may be used individually, in combination, or switched between as needed during implementation. Furthermore, notification of specific information (e.g., notification that "X is") is not limited to explicit notification, but may also be implicit (e.g., by not providing such notification).

[0150] Although the present disclosure has been described in detail above, it will 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 modified and altered forms without departing from the intent and scope of the present disclosure as defined by the claims. Therefore, the descriptions in the present disclosure are illustrative and not intended to be restrictive in any way.

[0151] This patent application claims priority based on Japanese Patent Application No. 2024-195507, filed on November 7, 2024, and the entire contents of Japanese Patent Application No. 2024-195507 are incorporated herein by reference.

[0152] 10 Base station 110 Transmitting unit 120 Receiving unit 130 Setting unit 140 Control unit 20 Terminal 210 Transmitting unit 220 Receiving unit 230 Setting unit 240 Control unit 30 Network node 1001 Processor 1002 Storage device 1003 Auxiliary storage device 1004 Communication device 1005 Input device 1006 Output device 2001 Vehicle 2002 Drive unit 2003 Steering unit 2004 Accelerator pedal 2005 Brake pedal 2006 Shift lever 2007 Front wheel 2008 Rear wheel 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 Rotation speed sensor 2023 Air pressure sensor 2024 Vehicle speed sensor 2025 Acceleration sensor 2026 Brake pedal sensor 2027 Shift lever sensor 2028 Object detection sensor 2029 Accelerator pedal sensor 2030 Driver assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (I / O port)

Claims

1. A first network node included in a communication system, comprising: a receiving unit that receives notification of a user plane change from a second network node; and a transmitting unit that transmits a message to a third network node that includes information regarding the user plane change and the destination of a QoS flow changed based on the user plane change.

2. The first network node according to claim 1, wherein the information relating to the user plane change includes approval information indicating whether the first network node has approved the user plane change and information indicating the destination of the approval information.

3. The first network node according to claim 1, wherein the second network node is a network node that manages user plane sessions, and the third network node is a network node that performs policy control.

4. The network node according to claim 1, wherein the QoS flow is a QoS flow corresponding to voice media in satellite constellation communication or a QoS flow connected to an EAS (Edge Application Server) in edge communication.

5. A third network node comprising: a receiving unit that receives a message from a first network node including approval information indicating whether the first network node has approved a change to the user plane, the destination of the QoS flow changed based on the change to the user plane, and information indicating the destination of the approval information; and a transmitting unit that transmits a first message to a second network node including the destination of the QoS flow after the change, wherein the destination of the approval information is a terminal point at the second network node, and the transmitting unit transmits a second message including the approval information to the terminal point.

6. A communication method performed by a first network node included in a communication system, comprising: receiving a notification of a user plane change from a second network node; and sending a message to a third network node containing information about the user plane change and the destination of a QoS flow changed based on the user plane change.

Images