Network node and base station

Abstract

A network node according to the present invention comprises a storage unit that stores QoS parameter values that include a first average window value and are associated with a codec type and a bit rate that is used for the codec, a reception unit that receives information that indicates a combination of a codec type and a bit rate from a first network node, a control unit that determines the QoS parameter value stored at the storage unit that includes a first average window value and is associated with a codec type and a bit rate that corresponds to the combination, and a transmission unit that transmits the determined QoS parameter value that includes an average window value to a second network node.

Description

Network Nodes and Base Stations

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

[0002] The 3GPP (registered trademark) (3rd Generation Partnership Project) is considering the specification of IVAS (Immersive Voice and Audio Services), a new voice codec to be used in a wireless communication system known as 5G or NR (New Radio).

[0003] 3GPP TS 26.253 V1.0.0 (2023-12)

[0004] The algorithm delay of IVAS is 32-38 ms, and the voice data generation interval of IVAS is 20 ms (see, for example, Non-Patent Document 1). To take advantage of the low latency of the IVAS algorithm and achieve low-latency voice communication, it is necessary to reserve radio resources every 20 ms. However, conventional standards do not specify a method for periodically reserving radio resources.

[0005] Furthermore, IVAS operates at multiple bit rates ranging from 13.2 to 512 kbps (see, for example, Non-Patent Document 1). While high bit rates and low delay are desirable for voice communications, it may be necessary to lower the bit rate or increase the delay depending on the wireless resource situation. Conventional standards allow for the creation of alternative QoS profiles for bit rates, but do not allow for the creation of alternative QoS profiles that increase delay, i.e., widen the averaging window.

[0006] The present invention has been made in view of the above points, and makes it possible to set an averaging window in a QoS profile, thereby making it possible to more effectively utilize IVAS.

[0007] The network node in this embodiment includes a memory unit that stores QoS parameter values, including a first average window value, associated with a codec type and a bit rate used for the codec; a receiver unit that receives information indicating a combination of a codec type and a bit rate from a first network node; a controller unit that determines QoS parameter values, including the first average window value, associated with the codec type and the bit rate stored in the memory unit and corresponding to the combination; and a transmitter unit that transmits the determined QoS parameter values, including the first average window value, to a second network node.

[0008] According to this embodiment, it is possible to set an averaging window in a QoS profile, and IVAS can be used more effectively.

[0009] FIG. 1 is a diagram showing an example of a communication system in the present embodiment. FIG. 2 is a diagram showing an example of a communication system architecture in the present embodiment. FIG. 3 is a sequence diagram showing an example of an IMS registration procedure in the present embodiment. FIG. 4 is a sequence diagram showing an example of an IMS voice outgoing procedure in the present embodiment. FIG. 5 is a sequence diagram showing an example of an IMS voice outgoing procedure in the present embodiment. FIG. 6 is a sequence diagram showing an example of a notification control procedure in the present embodiment. FIG. 7 is a diagram showing an example of the functional configuration of a base station in the present embodiment. FIG. 8 is a diagram showing an example of the functional configuration of a terminal in the present embodiment. FIG. 9 is a diagram showing an example of the hardware configuration of a base station and a terminal in the present embodiment. FIG. 10 is a diagram showing an example of the configuration of a vehicle in the present embodiment.

[0010] The present embodiment will be described below 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.

[0011] In the operation of the wireless communication system of this embodiment, existing technology is used as appropriate. However, the existing technology is, for example, the existing LTE, but is not limited to the existing LTE. Furthermore, the term "LTE" used in this specification has a broad meaning including LTE-Advanced and systems after LTE-Advanced (e.g., NR), or wireless LAN (Local Area Network), unless otherwise specified.

[0012] Furthermore, in this embodiment, "configuring" radio parameters etc. may mean that predetermined values ​​are pre-configured, or that radio parameters notified from the network node 30 or the terminal 20 are set.

[0013] Fig. 1 is a diagram illustrating an example of a communication system. As shown in Fig. 1, the communication system is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

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

[0015] The AMF is connected to the 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). The AMF, SMF, NSSF, NEF, NRF, UDM, AUSF, PCF, and AF are network nodes 30 that are mutually connected via interfaces based on their respective services, Namf, Nsmf, Nnssf, Nnef, Nnrf, Nudm, Nausf, Npcf, and Naf.

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

[0017] Fig. 2 is a diagram illustrating an example of a communication system in a roaming environment. As shown in Fig. 2, the network is composed of a UE, which is a terminal 20, and multiple network nodes 30. Hereinafter, it is assumed that one network node 30 corresponds to each function, but multiple functions may be realized by one network node 30, or multiple network nodes 30 may realize one function. Furthermore, the "connection" described below may be a logical connection or a physical connection.

[0018] The RAN is a network node 30 having a radio access function, and is connected to the UE, the AMF, and the UPF. The AMF is a network node 30 having functions such as RAN interface termination, NAS termination, registration management, connection management, reachability management, and mobility management. The UPF is a network node 30 having functions such as a PDU session point to the outside that interconnects with the DN, packet routing and forwarding, and user plane QoS handling. The UPF and the DN constitute a network slice. In the wireless communication network of this embodiment, multiple network slices are constructed.

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

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

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

[0022] The 3GPP Service and System Aspects Working Group 4 (SA4) is currently working on the specification of a new voice codec, IVAS.

[0023] The algorithm delay of IVAS is 32 to 38 ms, and the voice data generation interval of IVAS is 20 ms. To realize low-latency voice communication by taking advantage of the low latency of the IVAS algorithm, radio resources must be periodically reserved every 20 ms. However, conventional standards do not specify a method for periodically reserving radio resources. Considering the case where a caller in a voice communication moves within and between cells, a method using an averaging window to periodically reserve radio resources is effective.

[0024] In the conventional standard, the P-CSCF cannot notify the PCF of the average window value for each QoS flow, and the PCF cannot generate the average window value. As a result, the SMF cannot receive information about the average window from the PCF, and therefore cannot request the RAN to periodically reserve radio resources.

[0025] In conventional standards, the PCF derives the QoS-related information required for creating PCC rules using a QoS correspondence table from information regarding the requested bit rate and codec obtained from the P-CSCF, but the PCF does not derive the average window value.

[0026] IVAS operates at multiple bit rates ranging from 13.2 to 512 kbps. While high bit rates and low delay are desirable for voice communications, radio resource availability may necessitate lower bit rates and / or higher delays.

[0027] When switching to an alternative QoS profile, the terminal is notified of corresponding QoS-related information. The terminal renegotiates in SDP based on this information. However, in conventional standards, the P-CSCF cannot request an alternative QoS profile from the PCF, and the alternative QoS profile in the PCC rule generated by the PCF and the alternative QoS profile received by the gNB lacks an averaging window setting.

[0028] Thus, conventional standards allow for the creation of alternative QoS profiles for bit rates, but do not allow for the creation of alternative QoS profiles that increase delay, i.e., widen the averaging window.

[0029] According to this embodiment, a method is provided that enables setting of an averaging window in an alternative QoS profile in order to more effectively utilize IVAS. In this embodiment, the following changes and functions are made to the conventional standard.

[0030] According to this embodiment, IVAS information is included in the subscriber information stored in the HSS and / or UDR. The IVAS information includes multiple contracted bit rates and desired QoS settings during congestion for each contracted bit rate. The desired QoS settings during congestion also include an averaging window setting. The S-CSCF checks whether the contents of the SDP set by the terminal are within the range of the contract indicated in the subscriber information.

[0031] The carrier may notify the terminal of the contracted bit rate(s) in advance by using OMA DM, etc. The calling terminal may refer to this information and set the SDP offer.

[0032] According to this embodiment, an averaging window can be set in a QoS profile. The PCF may have a QoS correspondence table related to IVAS. The QoS correspondence table includes an item for the averaging window. When the PCF receives a requested bit rate and codec (IVAS) from the P-CSCF, it generates a PCC rule including an item for the averaging window from the QoS correspondence table.

[0033] According to this embodiment, an averaging window can be set in an alternative QoS profile. The PCF generates an alternative QoS profile including an averaging window item based on the desired QoS setting during congestion and sets the profile in the PCC rule. The RAN (e.g., a base station) processes the alternative QoS profile including the averaging window item.

[0034] <IMS Registration Procedure> FIG. 3 is a sequence diagram showing an example of an IMS registration procedure in this embodiment.

[0035] In step S101, the terminal 20 transmits a Register to the P-CSCF 30D via the base station 10. In step S102, the P-CSCF 30D transmits a Register to the S-CSCF 30E.

[0036] In step S103, the S-CSCF 30E transmits an Nhss_ImsUECM_Registration request (registration request) to the HSS 30F.

[0037] In step S104, HSS 30F transmits to S-CSCF 30E an Nhss_ImsUECM_Registration response (registration response) in response to the received Nhss_ImsUECM_Registration request.

[0038] In step S105, the S-CSCF 30E transmits an Nhss_ImsSDM_Get request (subscriber data acquisition request) to the HSS 30F to acquire subscriber information.

[0039] In this embodiment, the HSS 30F holds subscriber information including IVAS information. The IVAS information includes a contracted bit rate and a desired QoS setting during congestion for each contracted bit rate. The contracted bit rate included in the IVAS information may be, for example, a plurality of contracted bit rates. The desired QoS during congestion includes an averaging window setting. The UDR may store the subscriber information including the IVAS information.

[0040] In step S106, the HSS 30F transmits an Nhss_ImsSDM_Get response (subscriber data get response) including the subscriber information to the S-CSCF 30E. In the example of FIG.

[0041] In step S107, the S-CSCF 30E acquires the IVAS information from the received subscriber information.

[0042] In step S108, the S-CSCF 30E transmits a 200OK to the P-CSCF 30D.

[0043] In step S109, the P-CSCF 30D transmits 200OK to the terminal 20 via the base station 10.

[0044] As described above, according to this embodiment, the S-CSCF 30E can obtain subscriber information including IVAS information.

[0045] <IMS Voice Call Procedure> FIGS. 4A and 4B are sequence diagrams showing an example of an IMS voice call procedure in this embodiment.

[0046] 4A , the PCF 30B holds a QoS correspondence table including one or more QoS parameter values ​​associated with codec types (e.g., IVAS) and bit rates (e.g., bit rate A). The codec type is information indicating a codec such as IVAS or EVS (Enhanced Voice Services). The codec type is not limited to IVAS or EVS, and may be another codec.

[0047] The QoS parameter values ​​are, for example, Guaranteed bit-rate for uplink (kbps), Maximum bit-rate for uplink (kbps), Guaranteed bit-rate for downlink (kbps), and Maximum bit-rate for downlink (kbps). In this embodiment, the QoS parameter values ​​include an averaging window value. That is, the QoS correspondence table includes an averaging window value. The PCF 30B is not limited to the table format of the QoS correspondence table, and may store QoS parameter values ​​associated with codec types and bit rates, or may acquire QoS parameter values ​​associated with codec types and bit rates from another device that stores QoS parameter values ​​associated with codec types and bit rates.

[0048] In step S201, the terminal 20 transmits a SIP INVITE (SDP offer) to the P-CSCF 30D via the base station 10. The SIP INVITE includes the IVAS codec and bit rates A and B. In step S202, the P-CSCF 30D transmits the SIP INVITE to the S-CSCF 30E.

[0049] S-CSCF 30E determines whether or not both bit rates A and B included in the SIP INVITE are included in the subscriber information acquired in step S107 of Fig. 3. S-CSCF 30E checks whether or not the content of the SDP set by the terminal is within the range of the contract indicated by the subscriber information.

[0050] If S-CSCF 30E determines that bit rates A and B included in the SIP INVITE are included in the subscriber information, it transmits the SIP INVITE to I-CSCF 30G.

[0051] In step S205, the operation on the terminating network side is executed.

[0052] In step S206, the I-CSCF 30G sends a SIP 183 Session Progress (SDP answer) to the S-CSCF 30E. The SIP 183 Session Progress includes the IVAS codec and bit rate A.

[0053] In step S207, the S-CSCF 30E sends a SIP 183 Session Progress including the IVAS codec and bit rate A to the P-CSCF 30D.

[0054] In step S208, the P-CSCF 30D transmits a SIP 183 Session Progress including the IVAS codec and bit rate A to the terminal 20 via the base station 10.

[0055] 4B, the P-CSCF 30D transmits an Npcf_PolicyAuthorization_Create request (policy authorization creation request) to the PCF 30B. The policy authorization creation request includes the IVAS codec and bit rate A.

[0056] After step S209, if different congestion-time desired QoS settings are to be set for each subscriber, in step S210, the PCF 30B transmits a Nudr_DM_Query request to the UDR 30C. The UDR 30C may retain, for each subscriber (subscriber identification information), a QoS parameter value including an average window value or a list including multiple QoS parameter values ​​including an average window value. In the example of FIG. 4B , the UDR 30C retains a list for each subscriber, and the list includes a congestion-time desired QoS setting (parameter value) including "bit rate Ar1, average window value Aw1" and a congestion-time desired QoS setting including "bit rate Ar2, average window value Aw2." The Nudr_DM_Query request is a request signal for acquiring the above-mentioned list including subscriber identification information. In this embodiment, a use order or priority may be assigned to multiple QoS parameter values ​​including average window values.

[0057] In step S211, the UDR 30C transmits to the PCF 30B a Nudr_DM_Query response including a list corresponding to the subscriber identification information included in the Nudr_DM_Query request.

[0058] In step S212, PCF 30B acquires, from the Nudr_DM_Query response, as information indicating a combination of a codec type and a bit rate for each subscriber, a congestion-time desired QoS setting including "bit rate Ar1, average window value Aw1" and a congestion-time desired QoS setting including "bit rate Ar2, average window value Aw2" that correspond to the combination of the codec type IVAS and the bit rate A. In this way, PCF 30B may determine the congestion-time desired QoS setting corresponding to the subscriber (subscriber identification information).

[0059] After step S209, if the same desired QoS setting during congestion is to be set regardless of the subscriber, in step S213, PCF 30B refers to the QoS correspondence table it holds and determines a desired QoS setting during congestion including "bit rate Ar1, average window value Aw1" and a desired QoS setting during congestion including "bit rate Ar2, average window value Aw2" that correspond to the combination of IVAS and bit rate A included in the policy authorization creation request.

[0060] After step S212 or S213, in step S214, the PCF 30B sets the required QoS information including the average window value and the alternative QoS information including the average window value in the PCC rule.

[0061] In step S215, the PCF 30B sends an Npcf_SMPolicyControl_UpdateNotify request including a PCC rule to the SMF 30A. The PCC rule includes required QoS information including an average window value and alternative QoS information including an average window value.

[0062] In step S216, the SMF 30A transmits a PDU Session Resource Modify Request Transfer (QoS Flow Level QoS Parameters (GBR QoS Flow Information)) including the QoS information and the alternative QoS information to the base station 10. The QoS information and the alternative QoS information each include an average window value.

[0063] <Notification Control Procedure> FIG. 5 is a sequence diagram showing an example of a notification control procedure in this embodiment.

[0064] In step S301, when the QoS required by the m-th QoS profile does not satisfy the radio resources, the base station 10 may determine that the QoS required by the m-th substitute QoS profile can satisfy the radio resources.

[0065] The base station 10 may reserve first radio resources that satisfy a first QoS parameter set (first QoS parameter values), and then reserve second radio resources if the first QoS parameter set does not satisfy the second radio resources and the second QoS parameter set (second QoS parameter values) satisfies the second radio resources.

[0066] In step S302, the base station 10 transmits a PDU Session Resource Notify Transfer (Notification Cause (not fulfilled), Current QoS Parameters Set Index (m)) to the SMF 30A. The PDU Session Resource Notify Transfer includes information (index) indicating the current QoS parameter set satisfied by the radio resources. For example, when the QoS parameter set satisfied by the radio resources is changed, the PDU Session Resource Notify Transfer includes information indicating the changed QoS parameter set.

[0067] In step S303, the SMF 30A transmits an Npcf_SMPolicyControl_Update request to the PCF 30B.

[0068] In step S304, the SMF 30A transmits a PDU session modification command (Authorized QoS flow descriptions) to the terminal 20.

[0069] In step S305, the terminal 20 recognizes the change in QoS and performs SDP renegotiation.

[0070] The above-described embodiment enables the setting of an averaging window in a QoS profile, which was not defined in conventional standards, and allows IVAS to be used more effectively.

[0071] (Device Configuration) Next, a description will be given of an example of the functional configuration of the base station 10, network node 30, and terminal 20 that perform the processes and operations described above. The base station 10, network node 30, and terminal 20 include functions for performing the above-described embodiments. However, the base station 10, network node 30, and terminal 20 may each include only a part of the functions of the embodiments.

[0072] <Base Station 10 and Network Node 30> Fig. 6 is a diagram showing an example of the functional configuration of the base station 10. As shown in Fig. 6, 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 Fig. 6 is merely an example. As long as the operation according to this embodiment can be performed, the names of the functional divisions and functional units may be any. Note that the network node 30 may have the same functional configuration as the base station 10. Furthermore, a network node 30 having multiple different functions in the system architecture may be composed of multiple network nodes 30 separated by function.

[0073] 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 by wire or wirelessly. The receiver 120 includes a function of receiving various signals transmitted from the terminal 20 or another network node 30 and acquiring, for example, information of a higher layer from the received signal.

[0074] The setting unit 130 stores preset setting information and various setting information to be transmitted to the terminal 20 in a storage device, and reads the information from the storage device as needed. The content of the setting information includes, for example, settings related to the operations described in the embodiments.

[0075] As described in the embodiments, the control unit 140 performs processing related to the operations described in the embodiments. The control unit 140 also performs processing related to communication with the terminal 20. A functional unit related to signal transmission in the control unit 140 may be included in the transmitting unit 110, and a functional unit related to signal reception in the control unit 140 may be included in the receiving unit 120.

[0076] <Terminal 20> Fig. 7 is a diagram showing an example of the functional configuration of the terminal 20. As shown in Fig. 7, the 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 Fig. 7 is merely an example. The names of the functional divisions and functional units may be any names as long as they can perform the operations according to this embodiment.

[0077] The transmitter 210 creates a transmission signal from the transmission data and transmits the transmission signal wirelessly. The receiver 220 receives various signals wirelessly and acquires higher layer signals from the received physical layer signals. The receiver 220 also has a function of receiving NR-PSS, NR-SSS, NR-PBCH, DL / UL control signals, reference signals, and the like transmitted from the network node 30. The transmitter 210 may transmit using a backscattering method.

[0078] The setting unit 230 stores various setting information received from the network node 30 by the receiving unit 220 in a storage device and reads it from the storage device as needed. The setting unit 230 also stores setting information that is set in advance. The content of the setting information is, for example, settings related to the operations described in the embodiments.

[0079] The control unit 240 performs processing related to the operations described in the embodiments as described in the embodiments. The control unit 240 also performs processing related to the capacity-enhanced cell. The function unit related to signal transmission in the control unit 240 may be included in the transmitting unit 210, and the function unit related to signal reception in the control unit 240 may be included in the receiving unit 220.

[0080] The terminal 20 may have a power receiving unit that receives radio waves transmitted from a base station or the like, and may have hardware that receives and stores power.

[0081] (Hardware Configuration) The block diagrams (FIGS. 6 and 7) used to explain the above embodiments show functional blocks. These functional blocks (components) are realized by any combination of at least one of hardware and software. Furthermore, the method for realizing each functional block is not particularly limited. That is, each functional block may be realized using a single device that is physically or logically coupled, or may be realized using two or more physically or logically separated devices that are connected directly or indirectly (for example, using wires, wirelessly, etc.) and these multiple devices. The functional block may be realized by combining software with the single device or the multiple devices.

[0082] Functions include, but are not limited to, judgment, determination, assessment, calculation, computation, processing, derivation, investigation, search, confirmation, reception, transmission, output, access, resolution, selection, selection, establishment, comparison, assumption, expectation, consideration, broadcasting, notifying, communicating, forwarding, configuring, reconfiguring, allocating, mapping, and assignment. For example, a functional block (component) that performs transmission is called a transmitting unit or transmitter. As mentioned above, there are no particular limitations on how these functions are implemented.

[0083] For example, the network node 30, the terminal 20, etc. according to an embodiment of the present disclosure may function as a computer that performs processing of the wireless communication method of the present disclosure. Fig. 8 is a diagram illustrating an example of the hardware configuration of the base station 10 and the terminal 20 according to an embodiment of the present disclosure. The network node 30 may have the same hardware configuration as the base station 10. The above-described base station 10 and the terminal 20 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.

[0084] In the following description, the term "apparatus" can be interpreted as a circuit, a device, a unit, etc. The hardware configuration of the base station 10 and the terminal 20 may be configured to include one or more of the apparatuses shown in the drawings, or may be configured to exclude some of the apparatuses.

[0085] Each function in the base station 10 and the terminal 20 is realized by loading specified software (programs) onto hardware such as the processor 1001, the memory device 1002, etc., so that the processor 1001 performs calculations, controls communication by the communication device 1004, and controls at least one of reading and writing data in the memory device 1002 and the auxiliary memory device 1003.

[0086] The processor 1001 controls the entire computer by running, for example, an operating system. The processor 1001 may be configured as a central processing unit (CPU) including an interface with peripheral devices, a control device, an arithmetic unit, a register, etc. For example, the above-mentioned control unit 140, control unit 240, etc. may be realized by the processor 1001.

[0087] Furthermore, the processor 1001 reads programs (program codes), software modules, data, etc. from at least one of the auxiliary storage device 1003 and the communication device 1004 into the storage device 1002 and executes various processes in accordance with the programs. The programs used are those that cause a computer to execute at least some of the operations described in the above-described embodiments. For example, the control unit 140 of the base station 10 shown in FIG. 6 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. Furthermore, for example, the control unit 240 of the terminal 20 shown in FIG. 7 may be implemented by a control program stored in the storage device 1002 and running on the processor 1001. While the above-described various processes have been described as being executed by one processor 1001, they may also be executed simultaneously or sequentially by two or more processors 1001. The processor 1001 may be implemented by one or more chips. The programs may also be transmitted from a network via a telecommunications line.

[0088] The storage device 1002 is a computer-readable recording medium and may be configured, for example, by at least one of a read-only memory (ROM), an erasable programmable read-only memory (EPROM), an electrically erasable programmable read-only memory (EEPROM), a random access memory (RAM), etc. The storage device 1002 may also be called a register, a cache, a main memory, etc. The storage device 1002 can store executable programs (program codes), software modules, etc. for implementing a communication method according to an embodiment of the present disclosure.

[0089] The secondary storage device 1003 is a computer-readable recording medium, and may be, for example, at least one of an optical disk such as a CD-ROM (Compact Disc ROM), a hard disk drive, a flexible disk, a magneto-optical disk (e.g., a compact disk, a digital versatile disk, a Blu-ray (registered trademark) disk), a smart card, a flash memory (e.g., a card, a stick, a key drive), a floppy (registered trademark) disk, a magnetic strip, etc. The above-mentioned storage medium may be, for example, a database, a server, or other appropriate medium including at least one of the storage device 1002 and the secondary storage device 1003.

[0090] The communication device 1004 is hardware (transmission / reception device) for communicating between computers via at least one of a wired network and a wireless network, and is also referred to as, for example, a network device, a network controller, a network card, a communication module, etc. The communication device 1004 may be configured to include a high-frequency switch, a duplexer, a filter, a frequency synthesizer, etc. to realize at least one of frequency division duplex (FDD) and time division duplex (TDD). For example, a transmission / reception antenna, an amplifier unit, a transmission / reception unit, a transmission path interface, etc. may be realized by the communication device 1004. The transmission / reception unit may be implemented as a transmission unit and a reception unit that are physically or logically separated.

[0091] The input device 1005 is an input device (e.g., a keyboard, a mouse, a microphone, a switch, a button, a sensor, etc.) that receives input from the outside. The output device 1006 is an output device (e.g., a display, a speaker, an LED lamp, etc.) that outputs to the outside. Note that the input device 1005 and the output device 1006 may be integrated into one device (e.g., a touch panel).

[0092] 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 may be configured using different buses between each device.

[0093] 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 application specific integrated circuit (ASIC), a programmable logic device (PLD), or a field programmable gate array (FPGA), and some or all of the functional blocks may be realized by the hardware. For example, the processor 1001 may be implemented using at least one of these pieces of hardware.

[0094] Fig. 9 shows an example configuration of a vehicle 2001. As shown in Fig. 9, the 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 the present disclosure may be applied to a communication device mounted on the vehicle 2001, and may be applied to the communication module 2013, for example.

[0095] The drive unit 2002 is configured, for example, by 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 operated by the user.

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

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

[0098] The information service unit 2012 is composed of various devices, such as a car navigation system, an audio system, speakers, a television, and a radio, for providing various types of information such as driving information, traffic information, and entertainment information, and one or more ECUs for controlling these devices. The information service unit 2012 provides various types of multimedia information and multimedia services to the occupants of the vehicle 2001 by using information acquired from external devices via the communication module 2013, etc.

[0099] The driving assistance system unit 2030 is composed of various devices that provide functions for preventing accidents and reducing the driving burden on the driver, such as millimeter-wave radar, LiDAR (Light Detection and Ranging), cameras, positioning locators (e.g., GNSS, etc.), map information (e.g., high-definition (HD) maps, autonomous vehicle (AV) maps, etc.), gyro systems (e.g., IMU (Inertial Measurement Unit), INS (Inertial Navigation System), etc.), AI (Artificial Intelligence) chips, and AI processors, as well as one or more ECUs that control these devices. In addition, the driving assistance system unit 2030 transmits and receives various information via the communication module 2013 to realize the driving assistance function or the autonomous driving function.

[0100] 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 transmits and receives data via the communication port 2033 to and from 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 and memory (ROM, RAM) 2032 in the electronic control unit 2010, and sensors 2021 to 29, which are provided in the vehicle 2001.

[0101] 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 an external device. For example, it transmits and receives various information to and from the external device 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, a mobile station, or the like.

[0102] The communication module 2013 transmits, via wireless communication to an external device, a current signal from the current sensor that is input to the electronic control unit 2010. The communication module 2013 also transmits, via wireless communication to an external device, the rotation speed signals of the front and rear wheels acquired by a rotation speed sensor 2022, the air pressure signals of the front and rear wheels acquired by an air pressure sensor 2023, the vehicle speed signal acquired by a vehicle speed sensor 2024, the acceleration signal acquired by an acceleration sensor 2025, the accelerator pedal depression amount signal acquired by an accelerator pedal sensor 2029, the brake pedal depression amount signal acquired by a brake pedal sensor 2026, the shift lever operation signal acquired by a shift lever sensor 2027, and detection signals for detecting obstacles, vehicles, pedestrians, etc. acquired by an object detection sensor 2028, all of which are input to the electronic control unit 2010.

[0103] The communication module 2013 receives various information (traffic information, traffic signal information, vehicle distance information, etc.) transmitted from external devices and displays it on the information service unit 2012 provided in the vehicle 2001. The communication module 2013 also stores the various information received from the external devices 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 to 2029, etc. provided in the vehicle 2001.

[0104] (Summary of embodiment) As described above, a network node (e.g., PCF) in this embodiment may include: a storage unit that stores QoS parameter values ​​associated with a codec type and a bit rate used for the codec, the QoS parameter values ​​including a first average window value; a receiving unit that receives information indicating a combination of a codec type and a bit rate from a first network node (e.g., P-CSCF); a control unit that determines QoS parameter values ​​including the first average window value that correspond to the combination and are associated with the codec type and the bit rate stored in the storage unit; and a transmitting unit that transmits the determined QoS parameter values ​​including the average window value to a second network node (e.g., SMF).

[0105] According to this embodiment, the storage unit provided in the network node may further store QoS parameter values ​​including a second average window value, and a usage order may be assigned to the QoS parameter values ​​including the first average window value and the QoS parameter values ​​including the second average window value.

[0106] According to this embodiment, the control unit provided in the network node may determine a QoS parameter value including the second average window value associated with the codec type and the bit rate stored in the memory unit corresponding to the combination.

[0107] According to this embodiment, the transmitter may transmit a list acquisition request including subscriber identification information to a third network node that manages a list including, for each subscriber, QoS parameter values ​​including the first average window value and QoS parameter values ​​including the second average window value, the receiver may receive the list corresponding to the subscriber identification information, and the controller may use the list to determine QoS parameter values ​​including the first average window value and QoS parameter values ​​including the second average window value that correspond to the combination.

[0108] The codec type in this embodiment may be IVAS.

[0109] The base station in this embodiment includes: a receiving unit that receives, from a network node (e.g., an SMF), a list including QoS parameter values ​​including a first average window value and a QoS parameter value including a second average window value; a control unit that reserves a first radio resource that satisfies the QoS parameter value including the first average window value; and a communication unit that communicates with the network node; wherein the control unit reserves the second radio resource if the second radio resource does not satisfy the QoS parameter value including the first average window value but satisfies the QoS parameter value including the second average window value, and the communication unit may transmit information indicating that the second radio resource has been reserved to the network node.

[0110] The above configuration enables the setting of an averaging window in a QoS profile, which was not defined in conventional standards, and allows IVAS to be used more effectively.

[0111] (Supplementary Notes on the Embodiments) Although the present embodiment has been described above, the disclosed invention is not limited to such embodiments, and those skilled in the art will understand various modifications, alterations, alternatives, and replacements. While specific numerical examples have been used to facilitate understanding of the invention, 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. Two or more items may be combined as needed, and items described in one item may apply to items described in another item (as long as there is no contradiction). Boundaries between functional units or processing units in functional block diagrams do not necessarily correspond to physical component boundaries. The operations of multiple functional units may be physically performed by a single component, or the operations of a single functional unit may be physically performed by multiple components. The order of processing steps described in the embodiments may be reversed as long as there is no contradiction. For convenience of processing description, the network node 30 and the terminal 20 have been described using functional block diagrams. However, such devices may be realized by hardware, software, or a combination thereof. The software operated by the processor of the network node 30 according to this embodiment and the software operated by the processor of the terminal 20 according to this embodiment may each 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 or any other suitable storage medium.

[0112] Furthermore, the notification of information is not limited to the aspects / embodiments described in the present disclosure, and may be performed using other methods. For example, the notification of information may be performed by physical layer signaling (e.g., Downlink Control Information (DCI) and Uplink Control Information (UCI)), higher layer signaling (e.g., Radio Resource Control (RRC) signaling, Medium Access Control (MAC) signaling, broadcast information (Master Information Block (MIB) and System Information Block (SIB)), other signals, or a combination thereof. Furthermore, the RRC signaling may be referred to as an RRC message, and may be, for example, an RRC Connection Setup message, an RRC Connection Reconfiguration message, or the like.

[0113] Each aspect / embodiment described in the present disclosure may be applied to at least one of systems using LTE (Long Term Evolution), LTE-Advanced (LTE-A), SUPER 3G, IMT-Advanced, 4G (4th generation mobile communication system), 5G (5th generation mobile communication system), FRA (Future Radio Access), NR (New Radio), W-CDMA (registered trademark), GSM (registered trademark), CDMA2000, UMB (Ultra Mobile Broadband), IEEE 802.11 (Wi-Fi (registered trademark)), IEEE 802.16 (WiMAX (registered trademark)), IEEE 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems enhanced based on these. Furthermore, a combination of multiple systems (e.g., a combination of at least one of LTE and LTE-A with 5G, etc.) may also be applied.

[0114] Each aspect / embodiment described in the present disclosure may be implemented using any of the following standards: LTE (Long Term Evolution), LTE-Advanced (LTE-A), 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 number)), 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.17 (WiMAX (registered trademark)), IEEE 802.19 (WiMAX (registered trademark)), IEEE 802.20 (WiMAX (registered trademark)), IEEE 802.21 (Wi-Fi (registered trademark)), IEEE 802.22 (WiMAX (registered trademark)), IEEE 802.23 (WiMAX (registered trademark)), IEEE 802.24 (WiMAX (registered trademark)), IEEE 802.25 (WiMAX (registered trademark)), IEEE 802.26 (WiMAX (registered trademark)), IEEE 802.27 (WiMAX (registered trademark)), IEEE 802.28 (WiMAX (registered trademark)), IEEE 802.29 (WiMAX (registered trademark)), IEEE 802.30 (WiMAX (registered trademark)), IEEE 802.31 (Wi-Fi (registered trademark)), IEEE 802.32 (WiMAX (registered trademark)), IEEE 802.33 (WiMAX (registered trademark)), IEEE 802.34 ( The present invention may be applied to at least one of systems using 802.20, UWB (Ultra-Wide Band), Bluetooth (registered trademark), or other suitable systems, and next-generation systems that are extended, modified, created, or defined based on these systems. The present invention may also be applied to a combination of multiple systems (e.g., a combination of LTE and / or LTE-A with 5G).

[0115] The order of the procedures, sequences, flowcharts, etc. of each aspect / embodiment described herein may be rearranged unless it is consistent. For example, the methods described in this disclosure present elements of various steps using an example order and are not limited to the particular order presented.

[0116] In this specification, a specific operation that is described as being performed by the network node 30 may also be performed by its upper node in some cases. In a network consisting of one or more network nodes including the network node 30, it is clear that various operations performed for communication with the terminal 20 may be performed by at least one of the network node 30 and another network node other than the network node 30 (for example, an MME or an S-GW, etc., are possible, but are not limited to these). Although the above example illustrates a case where there is one other network node other than the network node 30, the other network node may be a combination of multiple other network nodes (for example, an MME and an S-GW).

[0117] The information, signals, etc. described in the present disclosure may be output from a higher layer (or a lower layer) to a lower layer (or a higher layer), or may be input / output via multiple network nodes.

[0118] Input and output information may be stored in a specific location (for example, memory) or may be managed using a management table. Input and output information may be overwritten, updated, or added to. Output information may be deleted. Input information may be transmitted to another device.

[0119] In the present disclosure, the determination may be made by a value represented by one bit (0 or 1), by a Boolean value (true or false), or by a comparison of numerical values ​​(e.g., comparison with a predetermined value).

[0120] Software shall be construed broadly to mean instructions, instruction sets, code, code segments, program code, programs, subprograms, software modules, applications, software applications, software packages, routines, subroutines, objects, executable files, threads of execution, procedures, functions, etc., whether referred to as software, firmware, middleware, microcode, hardware description language, or otherwise.

[0121] Software, instructions, information, etc. may also be transmitted or received over a transmission medium. For example, if software is transmitted from a website, server, or other remote source using wired technologies (such as coaxial cable, fiber optic cable, twisted pair, Digital Subscriber Line (DSL)), and / or wireless technologies (such as infrared, microwave), then these wired and / or wireless technologies are included within the definition of transmission media.

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

[0123] Note that terms described 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 a channel and a symbol may be a signal (signaling). Furthermore, a signal may be a message. Furthermore, a component carrier (CC) may be called a carrier frequency, a cell, a frequency carrier, etc.

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

[0125] Furthermore, the information, parameters, etc. described in the present disclosure may be expressed using absolute values, may be expressed using relative values ​​from a predetermined value, or may be expressed using other corresponding information. For example, a radio resource may be indicated by an index.

[0126] The names used for the above-described parameters are not intended to be limiting in any way. Furthermore, the mathematical expressions using these parameters may differ from those explicitly disclosed in this disclosure. The various channels (e.g., PUCCH, PDCCH, etc.) and information elements may be identified by any suitable names, and therefore the various names assigned to these various channels and information elements are not intended to be limiting in any way.

[0127] In the present disclosure, terms such as "base station (BS)," "radio base station," "base station device," "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. A base station may also be referred to by terms such as a macrocell, a small cell, a femtocell, and a picocell.

[0128] A base station can accommodate one or more (e.g., three) cells. When a base station accommodates multiple cells, the overall coverage area of ​​the base station can be partitioned into multiple smaller areas, and each smaller area can 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 the entire coverage area of ​​a base station and / or base station subsystem that provides communication services within that coverage area.

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

[0130] 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 some other suitable terminology.

[0131] At least one of the base station and the mobile station may be referred to as a transmitting device, a receiving device, a communication device, etc. At least one of the base station and the mobile station may be a device mounted on a mobile body, the mobile body itself, etc. The mobile body 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). At least one of the base station and the mobile station may also 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.

[0132] Furthermore, a base station in the present disclosure may be read as a user terminal. For example, the aspects / embodiments of the present disclosure may be applied to a configuration in which communication between a base station and a user terminal is replaced with communication between multiple terminals 20 (which may be called, for example, Device-to-Device (D2D) or Vehicle-to-Everything (V2X)). In this case, the terminal 20 may be configured to have the functions of the above-described network node 30. Furthermore, terms such as "uplink" and "downlink" may be read as terms corresponding to terminal-to-terminal communication (for example, "side"). For example, terms such as an uplink channel and a downlink channel may be read as a side channel.

[0133] Similarly, the user terminal in the present disclosure may be read as a base station, in which case the base station may be configured to have the functions of the user terminal described above.

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

[0135] The terms "connected," "coupled," or any variation thereof, refer to 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" to each other. The coupling or connection between elements may be physical, logical, or a combination thereof. For example, "connected" may be read as "access." As used in this disclosure, two elements may be considered to be "connected" or "coupled" to each other using one or more wires, cables, and / or printed electrical connections, as well as electromagnetic energy having wavelengths in the radio frequency range, microwave range, and optical (both visible and invisible) range, as some non-limiting and non-exhaustive examples.

[0136] The reference signal may be abbreviated as RS (Reference Signal) or may be called a pilot depending on the applicable standard.

[0137] As used in this disclosure, the phrase "based on" does not mean "based only on," unless expressly stated otherwise. In other words, the phrase "based on" means both "based only on" and "based at least on."

[0138] As used in this disclosure, any reference to an element using a designation such as "first," "second," etc. does not generally limit the quantity or order of those elements. These designations may be used in this disclosure as a convenient method of distinguishing between two or more elements. Thus, a reference to a first and a second element does not imply that only two elements may be employed or that the first element must in some way precede the second element.

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

[0140] When the terms "include," "including," and variations thereof are used in this disclosure, these terms are intended to be inclusive, similar to the term "comprising." Furthermore, when the term "or" is used in this disclosure, it is not intended to be an exclusive or.

[0141] In this disclosure, where articles are added by translation, such as a, an, and the in English, the disclosure may include that the nouns following these articles are in the plural form.

[0142] In the present 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 "coupled" may also be interpreted in the same way as "different."

[0143] The aspects / embodiments described in this disclosure may be used alone, in combination, or switched depending on the implementation. Notification of predetermined information (e.g., notification that "X is true") is not limited to explicit notification, but may be implicit (e.g., not notifying the predetermined information).

[0144] Although the present disclosure has been described in detail above, it is clear to those skilled in the art that the present disclosure is not limited to the embodiments described herein. The present disclosure can be implemented in modified and altered forms without departing from the spirit and scope of the present disclosure as defined by the claims. Therefore, the description of the present disclosure is intended to be illustrative and does not have any limiting meaning on the present disclosure.

[0145] 10 Base station 110 Transmitter 120 Receiver 130 Setting unit 140 Control unit 20 Terminal 210 Transmitter 220 Receiver 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 wheels 2008 Rear wheels 2009 Axle 2010 Electronic control unit 2012 Information service unit 2013 Communication module 2021 Current sensor 2022 RPM sensor 2023 Tire 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 Driving assistance system unit 2031 Microprocessor 2032 Memory (ROM, RAM) 2033 Communication port (IO port)

Claims

1. A network node comprising: a memory unit that stores QoS parameter values, including a first average window value, associated with a codec type and a bit rate used for the codec; a receiver unit that receives information indicating a combination of a codec type and a bit rate from a first network node; a controller that determines QoS parameter values, including the first average window value, associated with the codec type and the bit rate stored in the memory unit and corresponding to the combination; and a transmitter unit that transmits the determined QoS parameter values, including the average window value, to a second network node.

2. The network node according to claim 1, wherein the storage unit further stores QoS parameter values including a second averaging window value, and a usage order is assigned to the QoS parameter values including the first averaging window value and the QoS parameter values including the second averaging window value.

3. The network node according to claim 2, wherein the control unit determines a QoS parameter value including the second average window value associated with the codec type and the bit rate stored in the memory unit corresponding to the combination.

4. The network node according to claim 3, wherein the transmitter transmits a list acquisition request including subscriber identification information to a third network node that manages a list including, for each subscriber, QoS parameter values including the first average window value and QoS parameter values including the second average window value; the receiver receives the list corresponding to the subscriber identification information; and the controller uses the list to determine QoS parameter values including the first average window value and QoS parameter values including the second average window value that correspond to the combination.

5. The network node according to claim 1, wherein the codec type is IVAS (Immersive Voice and Audio Services).

6. A base station comprising: a receiving unit that receives from a network node a list including QoS parameter values including a first average window value and QoS parameter values including a second average window value; a control unit that reserves a first radio resource that satisfies the QoS parameter values including the first average window value; and a communication unit that communicates with the network node, wherein the control unit reserves the second radio resource if the second radio resource does not satisfy the QoS parameter values including the first average window value and satisfies the QoS parameter values including the second average window value; and the communication unit transmits information indicating that the second radio resource has been reserved to the network node.

Images