Apparatus and method for processing service policies in a wireless communication system

Abstract

A fifth (5G) generation or pre-5G communication system for supporting higher data transmission rates than fourth (4G) generation communication systems such as Long Term Evolution (LTE) is disclosed. An object of the present disclosure is to handle parameter information and policies for providing services in a wireless communication system, and a method of operating a base station may include: obtaining mapping information regarding quality of service related to direct communication between a first system and a second system; and using the mapping information to perform a handover between the quality of service of the first system and the quality of service of the second system.

Description

Technical Field

[0001] The present disclosure generally relates to wireless communication systems, and more particularly, to devices and methods for processing policy and parameter information for providing services in wireless communication systems. Background Art

[0002] To meet the growing demand for wireless data services after the commercialization of the fourth-generation (4G) communication system, efforts have been made to develop an advanced fifth-generation (5G) communication system or pre-5G communication system. For this reason, the 5G communication system or pre-5G communication system is referred to as a super 4G network communication system or a post-long term evolution (LTE) system.

[0003] To achieve high data rates, the 5G communication system considers its implementation in the extremely high frequency (mmWave) band (e.g., 60 GHz band). To mitigate the propagation path loss and to extend the propagation distance in the extremely high frequency band, the 5G communication system is discussing beamforming, massive multiple-input multiple-output (MIMO), full-dimensional (FD)-MIMO, array antennas, analog beamforming, and massive antenna technologies.

[0004] In addition, for network enhancement of the system, the 5G communication system is developing technologies such as evolved small cells, advanced small cells, cloud radio access network (RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multi-point (CoMP), and receive interference cancellation. In addition, the 5G system is also developing hybrid frequency shift keying and quadrature amplitude modulation (FQAM) and sliding window superposition coding (SWSC) as advanced compiled modulation (ACM) schemes, and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and sparse code multiple access (SCMA) as advanced access technologies.

[0005] Compared with existing 4G systems, the 5G system is considering supporting various services. For example, the most representative services are enhanced mobile broadband (eMBB), ultra-reliable and low-latency communication (URLLC), massive machine type communication (mMTC), evolved multimedia broadcast / multicast service (eMBMS), etc. A system that provides URLLC services may be referred to as a URLLC system, while a system that provides eMBB services may be referred to as an eMBB system. In this document, the terms service and system are used interchangeably.

[0006] Meanwhile, the Internet is evolving from a human - centric connected network in which humans create and consume information to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. Internet of Everything (IoE) technology, which combines IoT technology with big data processing technology by connecting to a cloud server, is also emerging. To implement IoT, technical elements such as sensing technology, wired and wireless communication and network infrastructure, service interface technology, and security technology are required, and technologies such as sensor networks for connecting between objects, machine - to - machine (M2M), and machine - type communication (MTC) have been recently studied. The IoT environment can provide intelligent Internet technology (IT) services that create new value in human life by collecting and analyzing data generated from connected objects. Through the integration and combination of existing IT with various industries, IoT can be applied to fields such as smart homes, smart buildings, smart cities, smart cars or connected vehicles, smart grids, healthcare, smart appliances, and advanced medical services.

[0007] Therefore, various attempts are being made to apply 5G communication systems to IoT networks. For example, technologies such as sensor networks, M2M, and MTC are implemented by schemes such as beamforming, MIMO, and array antennas, which are 5G communication technologies. Applying cloud radio access network (RAN) as the aforementioned big data processing technology can be said to be an example of the convergence of 5G technology and IoT technology.

[0008] Vehicle - to - everything (V2X) is a general term referring to all kinds of communication schemes applicable to road vehicles, and can provide various additional services in combination with the development of wireless communication technology in addition to initial safety use cases. The wireless access in vehicular environment (WAVE) standard based on Institute of Electrical and Electronics Engineers (IEEE) 802.11p and IEEE P1609 has been standardized as a V2X service provision technology. However, WAVE, as a dedicated short - range communication (DSRC) technology, has limitations because the message transmission distance between vehicles is restricted.

[0009] To overcome this limitation, the 3rd Generation Partnership Project (3GPP) is working on cellular - based V2X technology standards. Release 14 / Release 15 has completed the LTE - based evolved packet system (EPS) V2X standard, and Release 16 is working on the new radio (NR) - based 5th generation system (5GS) V2X standardization. SUMMARY OF THE INVENTION

[0010] TECHNICAL PROBLEM

[0011] Based on the above discussion, the present disclosure provides an apparatus and method for effectively processing policy and parameter information for providing services in a wireless communication system.

[0012] In addition, the present disclosure provides an apparatus and a method for providing mapping information of quality of service (QoS) parameters for direct communication in a wireless communication system.

[0013] In addition, the present disclosure provides an apparatus and a method for switching QoS parameters for direct communication in a wireless communication system.

[0014] Solution to the problem

[0015] According to various embodiments of the present disclosure, an operation method of a base station in a wireless communication system may include: obtaining mapping information of quality of service related to direct communication between a first system and a second system; and using the mapping information to switch between the quality of service of the first system and the quality of service of the second system.

[0016] According to various embodiments of the present disclosure, an operation method of a terminal in a wireless communication system may include: obtaining mapping information of quality of service related to direct communication between a first system and a second system; and using the mapping information to switch between the quality of service of the first system and the quality of service of the second system.

[0017] According to various embodiments of the present disclosure, a base station device in a wireless communication system may include at least one transceiver and at least one processor connected to the at least one transceiver, and the at least one processor may be controlled to obtain mapping information of quality of service related to direct communication between a first system and a second system, and use the mapping information to switch between the quality of service of the first system and the quality of service of the second system.

[0018] According to various embodiments of the present disclosure, a terminal device in a wireless communication system may include a transceiver and at least one processor connected to the transceiver, and the at least one processor may be controlled to obtain mapping information of quality of service related to direct communication between a first system and a second system, and use the mapping information to switch between the quality of service of the first system and the quality of service of the second system.

[0019] Advantageous effects of the invention

[0020] According to various embodiments of the present disclosure, the apparatus and method can effectively operate direct communication between different systems by using information of mapping information of quality of service related to direct communication between a first system and a second system.

[0021] The effects that can be obtained from the present disclosure are not limited to the effects mentioned above, and other effects not mentioned can be clearly understood by those skilled in the art of the present disclosure through the following description. Brief description of the drawings

[0022] Figure 1 Shows the structure of a first communication system according to an embodiment of the present disclosure.

[0023] Figure 2 Shows the structure of a second communication system according to an embodiment of the present disclosure.

[0024] Figure 3 Shows the interworking structure between communication systems according to an embodiment of the present disclosure.

[0025] Figure 4 Shows the configuration of network entities in a wireless communication system according to an embodiment of the present disclosure.

[0026] Figure 5 Shows the configuration of a terminal in a wireless communication system according to an embodiment of the present disclosure.

[0027] Figure 6 Shows a flowchart of using mapping information of quality of service in a wireless communication system according to an embodiment of the present disclosure.

[0028] Figure 7 Shows a flowchart of providing mapping information of quality of service in a wireless communication system according to an embodiment of the present disclosure.

[0029] Figure 8a Shows a process for a base station to obtain service policy / parameter information from the network of a first communication system during an initial registration process in a wireless communication system according to an embodiment of the present disclosure.

[0030] Figure 8b Shows a process for a terminal to obtain service policy and parameter information from the network of a first communication system in a wireless communication system according to an embodiment of the present disclosure.

[0031] Figure 9a Shows a process for a terminal and a base station to obtain service policy / parameter information from the network of a second communication system during an initial registration process in a wireless communication system according to an embodiment of the present disclosure.

[0032] Figure 9b Shows a process for a terminal to obtain service policy / parameter information from the network in response to a request from the network of a second communication system in a wireless communication system according to an embodiment of the present disclosure.

[0033] Figure 9c Shows a process for a terminal to obtain service policy / parameter information from the network of a second communication system in response to a terminal request in a wireless communication system according to an embodiment of the present disclosure.

[0034] Figure 10Illustrates a process for a terminal to request and obtain radio resources for direct communication from a network entity of a second communication system in a wireless communication system according to an embodiment of the present disclosure.

[0035] Figure 11 Illustrates a process for a terminal to request and obtain radio resources for direct communication from a network entity of a first communication system in a wireless communication system according to an embodiment of the present disclosure.

[0036] Figure 12 Illustrates a process for establishing a connection between a base station and a second communication system in a wireless communication system according to an embodiment of the present disclosure.

[0037] Figure 13 Illustrates a process for establishing a connection between a base station and a first communication system in a wireless communication system according to an embodiment of the present disclosure.

[0038] Figure 14a Illustrates a process for a terminal to obtain system information from a network in a wireless communication system according to an embodiment of the present disclosure.

[0039] Figure 14b Illustrates another process for a terminal to obtain system information from a network in a wireless communication system according to an embodiment of the present disclosure. Detailed Description

[0040] The terms used in the present disclosure are used to describe specific embodiments and are not intended to limit the scope of other embodiments. The singular form may include plural forms unless it is explicitly indicated differently. All terms used herein, including technical and scientific terms, may have the same meaning as those commonly understood by those skilled in the art to which the present disclosure pertains. Among the terms used in the present disclosure, terms defined in a general dictionary may be interpreted to have the same or similar meaning as in the context of the relevant field, and, unless explicitly defined in the present disclosure, it should not be ideally or overly interpreted as having a formal meaning. In some cases, even the terms defined in the present disclosure should not be interpreted to exclude embodiments of the present disclosure.

[0041] In various embodiments to be described below of the present disclosure, hardware methods are described as examples. However, since various embodiments of the present disclosure include technologies using both hardware and software, various embodiments of the present disclosure do not exclude software-based methods.

[0042] In the following, the present disclosure relates to an apparatus and method for processing policy and parameter information for providing services in a wireless communication system. In particular, the present disclosure describes a technique for switching between parameters for direct communication (e.g., PC5 communication, Proximity Services (ProSe), sidelink communication, Vehicle-to-Everything (V2X) communication) between user equipments (UEs) in a wireless communication system.

[0043] The terms used in the following description for identifying access nodes, the terms for representing network entities, the terms for representing messages, the terms for representing interfaces between network entities, and the terms for representing various identification information are for illustration purposes. Accordingly, the present disclosure is not limited to the terms to be described, and other terms may be used to represent entities having the same technical meaning.

[0044] For the sake of simplicity in the following description, the present disclosure uses the terms and names defined in the specifications of the Evolved Packet System (EPS) system and the Fifth Generation (5G) system, which are used as illustrations, to describe various embodiments. The various embodiments of the present disclosure can be easily modified and applied to other communication systems.

[0045] When describing embodiments of the present disclosure in detail, the communication standards defined by the Third Generation Partnership Project (3GPP) should be mainly targeted. However, the main subject of the present disclosure can be applied to other communication systems with a similar technical background with slight modifications without significantly departing from the scope of the present disclosure, and the scope of the present disclosure will be determined by those skilled in the art of the present disclosure.

[0046] When describing embodiments of the present disclosure in detail, vehicle communication services will be mainly targeted. However, the main subject of the present disclosure can be applied to other services provided in the EPS network or 5G network with slight modifications without significantly departing from the scope of the present disclosure, and the scope of the present disclosure will be determined by those skilled in the art of the present disclosure.

[0047] Figure 1 The structure of a first communication system according to an embodiment of the present disclosure is shown. According to the embodiment, Figure 1 The shown first communication system may be a mobile communication system based on the Long Term Evolution (LTE) standard.

[0048] Refer to Figure 1, The first communication system includes an evolved Node B (eNB) 120, a Mobility Management Entity (MME) 125, a Serving / PDN Gateway (S / P-GW) 130, a Home Subscriber Server (HSS) 135, a V2X Control Function (CF) 140, and a V2X Application Server (AS) 145. The S / P-GW 130 can be divided into a Serving Gateway (S-GW) and a PDN Gateway (P-GW). The eNB 120 can be referred to as a "base station", "Evolved Universal Mobile Telecommunications System Terrestrial Radio Access Network (E-UTRAN)", "Radio Access Network (RAN) node", or other terms with equivalent technical meanings.

[0049] User Equipments (UEs) 110a, 110b, 110c, or 110d access an external network through the eNB 120 and the S / P-GW 130. It is necessary to generate a Packet Data Network (PDN) connection for the UEs 110a, 110b, 110c, or 110d to send and receive data through the S / P-GW 130, and one PDN connection can include one or more EPS bearers. The UEs 110a, 110b, 110c, or 110d can be referred to as "terminals", "mobile stations", "subscriber stations", "remote terminals", "wireless terminals", or "user equipments", or other terms with equivalent technical meanings. For the following description, the present disclosure uses UE110a among the UEs 110a, 110b, 110c, or 110d to describe embodiments, and the other UEs 110b, 110, and 110d can operate similarly.

[0050] An Application Function (AF) is a device that exchanges application-related information with a user at the application level. The V2X AS 145 is a device for providing application-level V2X services. The V2X AS 145 can include an AF function.

[0051] The eNB 120 is a RAN node and corresponds to the Radio Network Controller (RNC) of the UTRAN system and the Base Station Controller (BSC) of the Global System for Mobile Communications (GSM) Enhanced Data Rate GSM Evolution (EDGE) Radio Access Network (GERAN) system. The eNB 120 is connected to the UE 110a through a radio channel and performs a role similar to that of an existing RNC / BSC.

[0052] In LTE, each user service including real-time services such as Voice over Internet Protocol (VoIP) based on the Internet Protocol is provided through a shared channel. Therefore, a device for collecting and scheduling the context information of the UE 110a is required, and the eNB 120 can be used as a scheduler.

[0053] The S / P-GW 130 is a device that provides data bearers and generates or removes data bearers under the control of the MME 125. The MME 125 is a device that manages various control functions, and one MME 125 can be connected to multiple eNBs including the eNB 120.

[0054] The HSS 135 is a device that stores and manages the subscription information of UEs including the UE 110a. The subscription information can be referred to as "UE subscription information" or "terminal subscription information". Additionally, the HSS 135 can store the subscription information for providing V2X services. is an example of the V2X service-related subscription information managed by the HSS 135.

[0055] [Table 1]

[0056]

[0057] The V2X CF 140 is a device that manages service policies and parameter information to provide V2X services. and show examples of the V2X service policies and parameter information managed by the V2X CF 140. The UE 110a can Figure 8a establish a PDN connection with the V2X CF 140 via the eNB 120 and the S / P-GW 130 after completing registration in the network as shown in the process, and obtain the V2X service policies and parameter information from the V2X CF 140. Alternatively, the V2X service policies and parameter information shown in or can be pre-configured in the UE 110a, and the UE 110a can use the pre-configured information. is an example of the V2X service policies and parameters for direct communication (e.g., ProSe).

[0058] [Table 2]

[0059]

[0060]

[0061] When describing the embodiments of the present disclosure, the QoS-related parameters defined in the 5G system can be referred to as "5G service quality indicator (5QI)" or "PC5 5QI (PQI)", and '5QI' and 'PQI' can be used interchangeably. is an example of the V2X service policies and parameters for network communication (e.g., Uu communication).

[0062] [Table 3]

[0063]

[0064] To provide LTE PC5 communication, a quality of service (QoS) model based on ProSe per-packet priority (PPPP) / ProSe per-packet reliability (PPPR) can be used. QoS parameters for LTE PC5 communication can include PPPP and PPPR. PPPP can include a value indicating a priority level. For example, PPPP can be expressed as a value ranging from '1' to '8'. If PPPP is '1', its priority can be determined to be higher than that of PPPP with a value of '2'. PPPR can include a value indicating a reliability level. For example, PPPR can be expressed as a value ranging from '1' to '8'. If PPPR is "1", a higher reliability than that of PPPR with a value of '2' can be determined to be required.

[0065] To provide New Radio (NR) PC5 communication, a QoS model based on PQI can be used. The QoS parameter for NR PC5 communication, i.e., PQI, can include at least one of a priority level, a packet delay budget, a packet error rate, an average window, and a maximum data burst volume. Additionally, to provide NR PC5 communication, a communication range value can be used together with PQI. The following shows an example of PQI. is an example of 5QI values defined in the 3GPP standard.

[0066] [Table 4]

[0067]

[0068]

[0069]

[0070]

[0071] According to an embodiment of the present disclosure, information related to mapping between a PPPP / PPPR-based QoS model for LTE PC5 communication and a PQI-based QoS model for NR PC5 communication (hereinafter referred to as'mapping information') can be defined. For example, the mapping information can be defined as "QoS-related policies / parameters" in . Specifically, the mapping information can be defined as "mapping between PPPP and 5QI" and "mapping between PPPR and 5QI" as shown in . The mapping information can be determined according to at least one of the following various schemes.

[0072] According to an embodiment, in order to determine a PPP P mapping that can be used interchangeably with the priority level of the PQI, a PPP P value or value range mapped to the priority level value or value range among the PQIs may be defined. For example, the priority level values '7' and '15' may be mapped to the PPP P value '1'. As another example, the priority level values from '0' to '20' may be mapped to the PPP P value '1'.

[0073] According to an embodiment, in order to determine a PPP P mapping that can be used interchangeably with the packet delay budget of the PQI, a packet delay budget for the PPP P mapping may be defined. A packet delay budget value or value range that is a PQI mapped to the packet delay budget value or a value range mapped to the PPP P may be defined. For example, the packet delay budget value mapped to the PPP P value '1' is defined as '110 ms', and the packet delay budget value '110 ms' derived from the PPP P may map the packet delay budget value as the PQI to '110b ms'. As another example, the packet delay budget value '110 ms' derived from the PPP P may be mapped to the range from '0 ms' to '110 ms' as the packet delay budget value of the PQI.

[0074] According to an embodiment, in order to determine a PPP R mapping that can be used interchangeably with the packet error rate of the PQI, a PPP R value or value range mapped to the packet error rate or value range as the PQI may be defined. For example, the packet error rate values '10-6' and '10-5' may be mapped to the PPP R value '1'. As another example, the packet error rate values from '10-6' to '10-5' may be mapped to the PPP R value '1'.

[0075] According to an embodiment, a PPP P value and / or a PPP R value mapped to the PQI value may be defined to determine the PPP P or PPP R that can be used interchangeably with the PQI value (e.g., the 5QI value corresponding to ). For example, the PQI value '1' may be mapped to the PPP P value '1' and / or the PPP R value '5'.

[0076] Mapping information between the LTE QoS model (e.g., PPP P / PPP R) and the NR QoS model (e.g., PQI) may be defined as in the various examples above, and the LTE QoS model and the NR QoS model may be sent to at least one of the terminal and the base station through Figures 8a to 9c the process.

[0077] Figure 2 The structure of a second communication system according to an embodiment of the present disclosure is shown. According to an embodiment, Figure 2 the second communication system shown may be a 5G-based mobile communication system.

[0078] Reference Figure 2 The second communication system includes a next-generation node B (gNB) 210, an access and mobility management function (AMF) 215, a session management function (SMF) 220, a user plane function (UPF) 225, a unified data management (UDM) 235, a unified data repository (UDR) 230, a policy control function (PCF) 240, a network exposure function (NEF) 245, and an application function (AF) 250. The gNB 210 may be referred to as a "base station", "next-generation RAN (NG-RAN)", "RAN node", or other terms with equivalent technical meanings.

[0079] UEs 110a, 110b, 200a, and 200b access an external network through the gNB 210 and the UPF 225. To enable a UE to send and receive data through the UPF 225, a PDU session needs to be established, and a PDU session may include one or more QoS flows. The UEs 110a, 110b, 200a, or 200b may be referred to as a 'terminal','mobile station','subscriber station', 'remote terminal', 'wireless terminal', or 'user equipment', or other terms with equivalent technical meanings. For the following description, the present disclosure uses UE 110a among the UEs 110a, 110b, 200a, and 200b to describe embodiments, and the other UEs 110b, 200a, and 200b may operate similarly.

[0080] The gNB 210 is a RAN node and corresponds to the eNB of the EPC system. The gNB 210 is connected to the UE 110a through a radio channel and performs a role similar to that of an existing RNC / BSC. In 5G, since each user service, including real-time services such as VoIP over the Internet Protocol, is served through a shared channel, a device for collecting and scheduling the context information of the UE 110a is required, and this device is managed by the gNB 210.

[0081] The AMF 215 is a device that manages various control functions, and one AMF 215 may be connected to multiple base stations. The UPF 225 is a device that provides a data bearer and creates or removes a PDU session under the control of the SMF 220. The UDM 235 is a device that stores and manages the subscription information of the UE 110a. Additionally, the UDM 235 may store subscription information for providing V2X services. shows an example of the V2X service-related subscription information managed by the UDM 235.

[0082] The PCF 240 is a device that controls the policies related to the QoS of the user, and the policy and charging control (PCC) rules corresponding to the policies are sent and applied to the SMF 220 and the UPF 225. Additionally, the PCF 240 can manage the service policies and parameter information for providing V2X services. and show examples of the V2X service policies and parameter information managed by the PCF 240. The V2X service policies and parameter information can be stored in the UDR 230. The PCF 240 can obtain the V2X service policies and parameter information from the UDR 230. The UE 110a can obtain the V2X service policies and parameter information from the PCF 240 through Figure 5 the process shown. Alternatively, the V2X service policies and parameter information shown in and can be pre-configured in the terminal, and the terminal can use the pre-configured information. The AF 250 is a device that exchanges application-related information with the user at the application level. The V2XAS 145 is a device for providing application-level V2X services. The V2X AS 145 can include the AF 250 function.

[0083] Figure 3 shows the interworking structure between communication systems according to an embodiment of the present disclosure. According to the embodiment, Figure 3 the structure shown can be an interworking structure between an LTE-based mobile communication system and a 5G-based mobile communication system (e.g., NR).

[0084] Referring to Figure 3 , for the interworking between the first communication system and the second communication system, the SGW 300, the UPF+PG-U 305, the SMF+PGW-C 510, the v-PCF 315, the HSS+UDM 320, and the v-V2X CF 325 can be deployed together with the first communication system and the second communication system.

[0085] Figure 4 shows the configuration of network entities in a communication system according to an embodiment of the present disclosure. The configuration shown in Figure 4 can be understood as a configuration of the eNB 120, the MME 125, the S / P-GW 130, the HSS 135, the V2X CF 140, the gNB 210, the AMF 215, the SMF 220, the UPF 225, the UDM 235, the UDR 230, the PCF 240, the NEF 245, and the AF 250. Terms such as "~ unit" or "~ device" used hereinafter indicate a unit for processing at least one function or operation, and can be implemented using hardware, software, or a combination of hardware and software.

[0086] Referring to Figure 4, the network entity includes a communication unit 410, a storage unit 420, and a control unit 430.

[0087] The communication unit 410 provides an interface for communicating with other devices in the network. That is, the communication unit 410 converts the bit stream sent from the network entity to other devices into a physical signal, and converts the physical signal received from other devices into a bit stream. That is, the communication unit 410 can send and receive signals. Therefore, the communication unit 410 can be referred to as a modem, a transmitter, a receiver, or a transceiver. At this time, the communication unit 410 enables the network entity to communicate with other devices or systems via a backhaul connection (e.g., a wired backhaul or a wireless backhaul) or via the network.

[0088] The storage unit 420 stores a basic program for operating the network entity, an application program, and data such as setting information. The storage unit 420 may include a volatile memory, a non-volatile memory, or a combination of a volatile memory and a non-volatile memory. The storage unit 420 provides the stored data according to the request of the control unit 430.

[0089] If Figure 4 the network entity is a base station (e.g., eNB 120 or gNB 210), then the network entity may further include a wireless communication unit. The wireless communication unit performs the function of sending and receiving signals through a radio channel. For example, the wireless communication unit performs the conversion function between the baseband signal and the bit string according to the physical layer standard of the system. For example, in data transmission, the wireless communication unit generates complex symbols by encoding and modulating the transmitted bit stream. In addition, in data reception, the wireless communication unit restores the received bit stream by demodulating and decoding the baseband signal.

[0090] In addition, the wireless communication unit up-converts the baseband signal to a radio frequency (RF) band signal, transmits it via an antenna, and down-converts the RF band signal received via the antenna to a baseband signal. To this end, the wireless communication unit may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), etc. In addition, the wireless communication unit may include multiple transmit / receive paths. In addition, the wireless communication unit may include at least one antenna array having multiple antenna elements.

[0091] In terms of hardware, the wireless communication unit may include a digital unit and an analog unit, and the analog unit may include multiple sub-units according to the operating power and operating frequency. The digital unit may be implemented with at least one processor (e.g., a digital signal processor (DSP)).

[0092] The wireless communication unit transmits and receives signals as described above. Accordingly, all or part of the wireless communication unit may be referred to as a "transmitter," "receiver," or "transceiver." Additionally, in the following description, transmission and reception through a radio channel are used in the sense of including the above-described processing of the wireless communication unit.

[0093] The control unit 430 controls the general operations of the network entity. For example, the control unit 430 transmits and receives signals through the communication unit 410. Additionally, the control unit 430 records data in the storage unit 420 and reads data from the storage unit 420. To this end, the control unit 430 may include at least one processor. According to various embodiments, the control unit 430 may control the network entity to perform operations according to various embodiments to be described.

[0094] Figure 5 The configuration of a terminal in a communication system according to an embodiment of the present disclosure is shown. The Figure 5 illustrated configuration may be understood as the configuration of UE 110a, 110b, 110c, 11d, 200a, or 200b. Terms such as "~ unit" or "~ device" used hereinafter indicate a unit for processing at least one function or operation, and may be implemented using hardware, software, or a combination of hardware and software.

[0095] Referring to Figure 5 , the terminal includes a communication unit 510, a storage unit 520, and a control unit 530.

[0096] The communication unit 510 may perform functions for transmitting and receiving signals through a radio channel. For example, the communication unit 510 performs a conversion function between a baseband signal and a bit string according to the physical layer standard of the system. For example, in data transmission, the communication unit 510 generates complex symbols by encoding and modulating the transmitted bit string. Additionally, in data reception, the communication unit 510 restores the received bit string by demodulating and decoding the baseband signal. Additionally, the communication unit 510 up-converts the baseband signal to an RF band signal, transmits it via an antenna, and down-converts the RF band signal received via the antenna to a baseband signal. For example, the communication unit 510 may include a transmit filter, a receive filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, etc.

[0097] In addition, the communication unit 510 may include multiple transmit and receive paths. Furthermore, the communication unit 510 may include at least one antenna array having multiple antenna elements. In terms of hardware, the communication unit 510 may include digital circuitry and analog circuitry (e.g., a radio frequency integrated circuit (RFIC)). Herein, the digital circuitry and the analog circuitry may be implemented as a single package. Additionally, the communication unit 510 may include multiple RF chains. Moreover, the communication unit 510 may perform beamforming.

[0098] The communication unit 510 transmits and receives signals as described above. Accordingly, all or part of the communication unit 510 may be referred to as a "transmitter", "receiver", or "transceiver". Additionally, in the following description, transmission and reception via a radio channel are used to mean the above-described processing including the communication unit 510.

[0099] The storage unit 520 stores a basic program for operating the terminal, applications, and data such as setting information. The storage unit 520 may include a volatile memory, a non-volatile memory, or a combination of a volatile memory and a non-volatile memory. The storage unit 520 provides the stored data according to a request from the control unit 530.

[0100] The control unit 530 controls general operations of the terminal. For example, the control unit 530 transmits and receives signals through the communication unit 510. Additionally, the control unit 530 records data in the storage unit 320 and reads data from the storage unit 320. The control unit 530 may perform functions of a protocol stack required by a communication standard. To this end, the control unit 530 may include at least one processor or microprocessor, or may be part of a processor. Additionally, part of the communication unit 510 and the control unit 530 may be referred to as a communication processor (CP). According to various embodiments, the control unit 530 may control the terminal to perform operations according to various embodiments to be described.

[0101] Figure 6 A flowchart showing mapping information for using QoS in a wireless communication system according to an embodiment of the present disclosure is shown. Figure 6 A method of operating a device using QoS mapping information is shown. For example, the device may be a base station (e.g., eNB 120 or gNB 210) or a UE (e.g., UE 110a, 110b, 110c, 110d, 200a, or 200b).

[0102] Refer to Figure 6, in step 601, the device obtains QoS mapping information between different systems. The QoS mapping information may include at least one of the following: information notifying that a switch between parameters indicating the QoS required for communication in the first system and the second system is allowed, information indicating the correspondence between parameters indicating the QoS required for communication in the first system and the second system, and information indicating the switching rule between parameters indicating the QoS required for communication in the first system and the second system. For example, one of the first system and the second system may be a system based on the LTE standard as shown in Figure 1 shown, and the other may be a system based on the NR standard as shown in Figure 2 shown. The QoS mapping information can be obtained through a unique process for providing mapping information or a process for other purposes (e.g., a process for registering in the network, a process for accessing the network, or a process for updating the tracking area (TA)).

[0103] In step 603, the device uses the mapping information to perform operations related to direct communication. For example, the device can use the mapping information to switch the QoS parameters of the first system to the QoS parameters of the second system. The switched QoS parameters can be used for various operations related to direct communication. For example, the switched QoS parameters can be used for resource allocation, resource request, service availability determination, etc.

[0104] As in the embodiment described with reference to Figure 6 the device can obtain QoS mapping information between the first system and the second system. In this regard, the device can send to the network capability information notifying the ability to perform operations related to direct communication based on the QoS mapping information. That is, since unnecessary signaling overhead is caused by still providing the mapping information to the device even when the mapping information is unavailable, the device can still notify the network of the necessity of the mapping information by sending capability information reporting that the mapping information is available.

[0105] As in the embodiment described with reference to Figure 6 the device can switch the QoS parameters of the first system to the QoS parameters of the second system.

[0106] According to an embodiment, if the device is a base station, the device can receive from the terminal a message requesting resource allocation for direct communication, and switch the QoS parameters of the first system included in the message to the QoS parameters of the second system. For example, the device can select a system suitable for direct communication based on the link states of the first system and the second system, and switch the QoS parameters for resource allocation according to the selection.

[0107] According to another embodiment, if the device is a UE, the device may switch the QoS parameters of the first system generated by the application to the QoS parameters of the second system. As an example, in order to perform directed communication in a system other than the system corresponding to the QoS parameters provided by the application, the device may switch the QoS parameters generated by the application. As another example, if a system for providing services for each application is defined but the QoS parameters provided by the application do not correspond to the defined system, the device may switch the QoS parameters generated by the application.

[0108] Figure 7 is a flowchart of mapping information for providing QoS in a wireless communication system according to an embodiment of the present disclosure. Figure 7 shows an operation method of a device for providing QoS mapping information. For example, the device may be a core network entity (e.g., HSS 135, MME 125, V2X CF 140, S / P-GW 130, UDR 230, PCF 240, or AMF 215) or a base station (e.g., eNB 120 or gNB 210).

[0109] Referring to Figure 7 , in step 701, the device generates a message including QoS mapping information between different systems. The QoS mapping information may include at least one of the following: information notifying that a switch between parameters indicating QoS required for communication in the first system and the second system is allowed, information indicating correspondence between parameters indicating QoS required for communication in the first system and the second system, and information indicating a switching rule between parameters indicating QoS required for communication in the first system and the second system. For example, one of the first system and the second system may be a system based on the LTE standard as shown in Figure 1 , and the other may be a system based on the NR standard as shown in Figure 2 . The message including the QoS mapping information may be generated by a request from another device or may be generated by the device's determination.

[0110] In step 703, the device transmits the message including the QoS mapping information. The message including the QoS mapping information may be transmitted through a unique process for providing mapping information or a process for other purposes (e.g., a process for registering in the network, a process for accessing the network, or a process for updating the TA).

[0111] According to various embodiments, an operation method of a base station in a wireless communication system may include: obtaining information on QoS mapping related to direct communication between a first system and a second system; and using the mapping information to switch between the QoS of the first system and the QoS of the second system.

[0112] In some embodiments, obtaining mapping information may include: sending a first message for registering a terminal to a higher network entity; receiving a second message as a response to the first message; and obtaining mapping information from the second message.

[0113] In some embodiments, the method further includes: receiving a first message from a terminal requesting resources for direct communication; and sending a second message notifying a result of resource allocation, and the second message may be generated based on QoS parameters related to direct communication included in the first message and mapping information.

[0114] In some embodiments, the method further includes: sending a first message for establishing a connection with a network to a higher network entity; and receiving a second message as a response to the first message from the higher network entity, and the first message may include capability information of a base station related to QoS mapping.

[0115] In some embodiments, the capability information may include information indicating the presence or absence of cross-radio access technology (RAT) PC5 control capability.

[0116] In some embodiments, an operating method of a terminal in a wireless communication system may include: obtaining QoS mapping information related to direct communication between a first system and a second system; and using the mapping information to switch between QoS of the first system and QoS of the second system.

[0117] In some embodiments, the method further includes: sending a first message requesting resources for direct communication to a base station; and receiving a second message notifying a result of resource allocation, and the first message may include QoS parameters of the first system or the second system.

[0118] In some embodiments, the first message may indicate whether the resources requested based on at least one of a message type, an indication, a destination address value, and QoS parameters included in the first message are first system resources or second system resources.

[0119] According to various embodiments, a base station device in a wireless communication system includes at least one transceiver and at least one processor connected to the at least one transceiver, and the at least one processor may be controlled to obtain mapping information of QoS related to direct communication between a first system and a second system, and use the mapping information to perform a switch between QoS of the first system and QoS of the second system.

[0120] In some embodiments, the at least one processor may be controlled to send a first message for registering a terminal to a higher network entity, receive a second message as a response to the first message, and obtain mapping information from the second message.

[0121] In some embodiments, at least one processor controls to receive, from a terminal, a first message requesting resources for direct communication, and to send a second message notifying an allocation result of the resources, and may generate the second message based on QoS parameters and mapping information related to direct communication included in the first message.

[0122] In some embodiments, at least one processor controls to send, to a higher network entity, a first message for establishing a connection with the network, and to receive, from the higher network entity, a second message as a response to the first message, and the first message may include capability information of a base station related to QoS mapping.

[0123] In some embodiments, the capability information may include information indicating the presence or absence of cross-RAT PC5 control capability.

[0124] In some embodiments, a terminal device in a wireless communication system includes a transceiver and at least one processor connected to the transceiver, and the at least one processor may control to obtain information on QoS mapping related to direct communication between a first system and a second system, and to perform switching between the QoS of the first system and the QoS of the second system by using the mapping information.

[0125] In some embodiments, at least one processor controls to send, to a base station, a first message requesting resources for direct communication, and to receive a second message notifying an allocation result of the resources, and the first message may include QoS parameters of a first system or a second system.

[0126] In some embodiments, the first message may indicate whether the requested resources are first system resources or second system resources based on at least one of a message type, an indication, a destination address value, and QoS parameters included in the first message.

[0127] Hereinafter, the present disclosure describes specific examples of providing, obtaining, and using mapping information of QoS parameters between different systems. In the following description, messages having specific names are mentioned for convenience of description, but do not limit the present disclosure.

[0128] Figure 8a A process for a base station to obtain service policy / parameter information from a network of a first communication system during an initial registration process in a wireless communication system according to an embodiment of the present disclosure is shown. Figure 8a The shown process is a process for UE 110a to register with a network, and the registration process may be referred to as network attachment. A default EPS bearer is created during network attachment, so an always-on IP connection is possible.

[0129] According to Figure 8a, in step 801, UE 110a may send an initial attachment request message to eNB 120. UE 110a may use a radio resource control (RRC) connection setup complete message to send the attachment request message to eNB 120.

[0130] In step 803, eNB 120 may send an initial attachment request message to MME 125 for access. eNB 120 may use an initial UE message as an S1-MME control message to send the attachment request message. The initial attachment request message may include UE capability information supported by UE 110a. The UE capability information may include at least one of a V2X capability indication, an LTE PC5 capability, and an NR PC5 capability. The initial attachment request message may be included in an S1 application protocol (S1AP) initial UE message and delivered to MME 125. eNB 120 may deliver an initial UE message including the V2X support capability information (e.g., V2X support, cross-RAT PC5 control capability information) of eNB 120 to MME 125. According to another embodiment, a tracking area update (TAU) message may be used instead of the initial attachment request message.

[0131] In step 805, MME 125 may send a message (e.g., a UE subscription request message) requesting the subscription information of UE 110a to HSS 135. In step 807, HSS 135 may respond to MME 125 with a response message (e.g., a UE subscription response message) including the UE subscription information. The subscription information of UE 110a may include at least one of the items shown in . According to an embodiment of the present disclosure, HSS 135 may store the V2X service policy and parameter information for direct communication (e.g., ProSe) shown in . The subscription information responded to MME 125 by HSS 135 may include at least some of the V2X service policy and parameter information for direct communication (e.g., ProSe) shown in .

[0132] Next, in step 809, MME 125 may send an S1AP initial context setup request message including an attachment accept message or a TAU accept message to eNB 120. MME 125 may determine the information included in the initial context setup request message and provided to eNB 120 based on the UE capability and eNB capability (RAN capability) information received in step 803.

[0133] According to an embodiment, if the UE capability includes a V2X capability indication and the eNB capability includes V2X support, the initial context setup request message may include at least one of a V2X service authorization indication (e.g., a of Table 1) and a UE-PC5-aggregated maximum bit rate (AMBR) for LTE PC5 (e.g., b of Table 1).

[0134] According to another embodiment, if the UE capability includes a V2X capability indication and an NR PC5 capability, and the eNB capability includes V2X support and cross-RAT PC5 control, the initial context setup request message may include at least one of the following: a V2X service authorization indication (e.g., a of ), a UE-PC5-AMBR for LTE PC5 (e.g., b of Table 1), a UE-PC5-AMBR for NR PC5 (e.g., c of ), a cross-RAT PC5 control authorization (e.g., e of ), and V2X service policy and parameter information for direct communication (e.g., ProSe) (e.g., at least one of the items of ).

[0135] In step 811, the eNB 120 sends an RRC connection reconfiguration message including an attachment accept message to the UE 110a. Next, although not depicted in Figure 8a , the UE 110a sends an RRC connection reconfiguration complete message to the eNB 120, and the eNB 120 sends an initial context setup response message to the new MME 125. Next, in step 813, the UE 110a sends a direct transfer message including an attachment complete message to the eNB 120. In step 815, the eNB 120 delivers the attachment complete message to the new MME 125.

[0136] Figure 8b A process for a terminal to obtain service policy and parameter information from a network of a first communication system in a wireless communication system according to an embodiment of the present disclosure is shown. Figure 8b A process for a terminal to obtain V2X service policy and parameter information is shown. According to Figure 8b the process shown, after completing registration at the network through Figure 8a the process shown, the UE 110a may establish a PDN connection with the V2X CF 140 through the eNB 120 and the S / P-GW 130, and obtain V2X service policy and parameter information from the V2X CF 140.

[0137] Referring to Figure 8b, in step 817, the HSS 135 may receive V2X-related subscription information and service policy / parameter information from the V2X CF 140. In step 819, the UE 110a may send a V2X policy provisioning request message to the V2X CF 140. The V2X policy provisioning request message may include UE capabilities (e.g., LTE PC5 capabilities, NR PC5 capabilities, etc.). In step 821, the V2X CF 140 that receives the V2X policy provisioning request message may reply with a V2X policy provisioning response message. The V2X policy provisioning response message may include at least some of the V2X service policy and parameter information shown in and .

[0138] In the embodiment described with reference to Figure 8b in step 817, the HSS 135 and the V2X CF 140 may exchange UE subscription information and service policy / parameter information related to V2X. Referring to Figure 8a and Figure 8b , step 817 is performed after the network registration of the UE 110a. However, according to another embodiment, step 817 may be performed before the network registration of the UE 110a, i.e., before step 801. Additionally, if there is a change in the UE subscription information and service policy / parameter information related to V2X, the HSS 135 or the V2X CF 140 may update the information by triggering step 817.

[0139] Figures 9a to 9c shows a process for a terminal to obtain service policy / parameter information (e.g., the V2X service policy parameters shown in ) from a network according to an embodiment of the present disclosure.

[0140] Figure 9a shows a process for a terminal and a base station to obtain service policy / parameter information from a network of a second communication system during an initial registration process in a wireless communication system according to an embodiment of the present disclosure. Figure 9a shows the signaling between the UE 110a, the gNB 210, the AMF 215, the PCF 240, the UDM 235, and the UDR 230. Herein, the gNB 210 may be referred to as 'access network (An)' or 'RAN'.

[0141] Referring to Figure 9a, in step 901, the UDM 235 may send the subscription information of the UE 110a to the PCF 240. For example, if the subscription information of the UE 110a stored in the UDM 235 is updated, the UDM 235 may provide the updated subscription information. In step 903, the UDR 230 may send policy-related information (e.g., V2X service parameters) to the PCF 240. For example, if the policy-related information stored in the UDR 230 is updated, the UDR 230 may provide the updated policy-related information. In Figure 9a , it is shown that step 901 and step 903 are performed before the subsequent steps. However, according to another embodiment, at least one of step 901 and step 903 may be omitted, or may be performed at different times. That is, step 901 and step 903 may be performed independently of the registration process of the UE110a.

[0142] In step 905, the UE 110a may send a registration request message to the gNB 210. In step 907, the gNB 210 may send a registration request message to the AMF 215. In step 909, the AMF 215 that receives the registration request message from the UE 110a via the gNB 210 may request the UE subscription information of the UE 110a from the UDM 235 by signaling with the UDM 235 and obtain the subscription information. In step 911, the AMF 215 may request the policy information related to the UE 110a from the PCF240 by signaling with the PCF 240 and obtain the policy information.

[0143] In step 905, the UE 110a may include the UE capability information supported by the UE 110a and / or the UE policy container (e.g., V2X policy) information in the registration request message, and thus send the capability information and / or the UE policy container information to the gNB 210. The gNB 210 may deliver the registration request message received from the UE 110a to the AMF 215. At this time, if the UE110a supports the V2X service, the information indicating that the UE 110a supports the V2X service may be provided to the AMF 215 by being included in the UE capability information (e.g., V2X capability indication). In addition, the information indicating that the UE 110a supports PC5 communication may be provided to the AMF 215 by being included in the UE LTE PC5 capability and UE NR PC5 capability information.

[0144] The registration request message sent in step 907 can be delivered to the AMF 215 by being included in the Next Generation Application Protocol (NGAP) initial UE message sent by the gNB 210 to the AMF 215. The gNB 210 can include gNB 210 support capability information in the initial UE message, for example, V2X support and inter-RAT PC5 control.

[0145] In step 909, the AMF 215 can request the subscription information of the UE 105a from the UDM 235, and the UDM 235 can send a message requesting the subscription information to the UDR 230. The message for requesting the subscription information of the UE 110a can include identification information indicating the UE 110a (for example, the subscriber permanent identifier (SUPI) of the UE 110a, 5G globally unique temporary identifier (GUTI), international mobile subscriber identity (IMSI), etc.). The UDR 230 can reply to the UDM 235 with a DM query response message including the subscription information of the UE 110a. The UDM 235 that has received the UE subscription information can reply to the AMF 215 with a UE subscription response message. The UE subscription response message can include at least one of the UE subscription information of the V2X services shown in : (for example, the V2X service authorization information of the UE 110a, the V2X capability of the UE 110a, the PC5 LTE capability of the UE 110a, the PC5 NR capability of the UE 110a, the inter-RAT PC5 control authorization information of the UE 110a, etc.).

[0146] According to an embodiment, if the AMF 215 determines that the UE 110a supports V2X services based on the UE capability information received from the UE 110a, the AMF 215 can select the PCF 240 that supports V2X services. In step 911, the AMF 215 can request the policy information related to the UE 110a from the selected PCF 240. The message sent in step 911 can include the UE policy container (for example, V2X policy) information received by the AMF 215 from the UE 110a.

[0147] The PCF 240 can use one of various methods to obtain the V2X service parameters to be applied to the UE 110a from the UDR 230. For example, in step 903, if V2X service parameter updates are required, the UDR 230 can provide the V2X service parameters to the PCF 240. As another example, in step 911, the PCF 240 can request and obtain the V2X service parameters from the UDR 230. According to an embodiment, the V2X service parameters provided by the UDR 230 to the PCF 240 can include the V2X service policy and parameter information shown in and .

[0148] Meanwhile, in step 911, the PCF 240 may receive the subscriber information of the UE 110a and information on the functionality or capabilities supported by the UE 110a. That is, in step 911, the AMF 215 may provide the UE capability information and / or UE subscription information obtained from the UDM 235 to the PCF 240.

[0149] In step 911, the PCF 240 provides the AMF 215 with policy information to be applied to the UE 110a, and parameters for V2X services obtained from the UDR 230 may be included in the policy information. If the PCF 240 sends the parameter policy information for V2X services to the AMF 215, the PCF 240 may configure the policy container according to the following method.

[0150] According to an embodiment, the PCF 240 may include the policy / parameter information related to LTE PC5 among the V2X service policies and parameters in for direct communication (e.g., ProSe) into one policy container. Additionally, the PCF 240 may include the policy / parameter information related to NR PC5 among the V2X service policies and parameters in for direct communication (e.g., ProSe) into one policy container. Additionally, the PCF 240 may include the V2X service policy and parameter information in for network communication (e.g., Uu communication) into one policy container. The PCF 240 may specify a policy part ID indicating the V2X service policy and parameter information to the V2X policy and include it in the policy container. The PCF 240 may notify, through the policy part ID, that the corresponding policy information is a policy for V2X and that the V2X service policy and parameter information are included.

[0151] In steps 913 and 915, the AMF 215 may deliver a registration acceptance message including the parameter information for V2X services obtained from the PCF 240 to the UE 110a via the gNB 210. At this time, the AMF 215 may determine the information to be provided to the gNB 210 using the registration acceptance message included in the NGAP initial context setup message and the information to be provided to the UE 110a using and including the registration acceptance message based on the UE capability and RAN capability information received in step 907.

[0152] According to an embodiment, if the UE capability includes a V2X capability indication and an NR PC5 capability, and the gNB capability includes V2X support, the registration acceptance message sent in step 913 may include at least one of the following: a V2X service authorization indication (e.g., a) of , a UE-PC5-AMBR for NR PC5 (e.g., c) of , a list of PLMNs for the UE 110a to use PC5 communication (e.g., d) of , a cross-RAT PC5 control authorization (e.g., e) of , and a policy container including policy / parameter information related to NR PC5 among the V2X service policies and parameters for direct communication (e.g., ProSe) of .

[0153] According to an embodiment, if the UE capability includes a V2X capability indication, an LTE PC5 capability, and an NR PC5 capability, and the gNB capability includes V2X support and cross-RAT PC5 control, the registration acceptance sent in step 913 may include at least one of the following: a V2X service authorization indication (e.g., a) of , a UE-PC5-AMBR for LTE PC5 (e.g., b) of , a UE-PC5-AMBR for NR PC5 (e.g., c) of , a list of PLMNs for the UE 110a to use PC5 communication (e.g., d) of , a cross-RAT PC5 control authorization (e.g., e) of , a policy container including policy / parameter information related to LTE PC5 among the V2X service policies and parameters for direct communication (e.g., ProSe) of , and a policy container including policy / parameter information related to NR PC5 among the V2X service policies and parameters for direct communication (e.g., ProSe) of .

[0154] Alternatively, in steps 917 and 919, the AMF 215 may deliver to the UE 110a, through a separate process, the parameter information for V2X services received from the PCF 240. The parameter information for providing V2X services included in the registration acceptance message sent in steps 913 and 915 or the UE policy delivery message sent in steps 917 and 919 may include at least one of the service policy / parameter information described in this disclosure. At this time, in steps 917 and 919, the parameter information for V2X services included in the NGAP downlink non-access stratum (NAS) transport message and the NAS message for the AMF 215 to provide policy information to the terminal may be determined in a manner similar to that in steps 913 and 915. In step 917, the AMF 215 may deliver an NGAP UE context modification request message to the gNB 210. The NGAP UE context modification request message is a message for changing the context information of the terminal configured in the gNB 210, and the gNB 210 stores and applies, in the context of the terminal, the parameter information for V2X services received through the NGAP UE context modification request message. In response thereto, the gNB 210 may send an UE context modification response message to the AMF 215, and thus notify that the context of the terminal has been changed and applied according to the received information.

[0155] Figure 9b The process for a terminal to obtain service policy / parameter information from a network in response to a network request of a second communication system in a wireless communication system according to an embodiment of the present disclosure is shown. Figure 9b It is an example of another process for the UE 110a to obtain service policy / parameter information (e.g., the V2X service policy parameters shown in ). According to Figure 9b the embodiment, the UE110a may use the UE configuration update process to obtain UE policy-related information.

[0156] Referring to Figure 9b , in step 923, the PCF 240 may determine to update the UE policy. Similar to step 903 in Figure 9a described above, the PCF 240 may receive and store the updated service policy / parameter information of the terminal (e.g., the V2X service policy parameters shown in ) from the UDR 230. At this time, the PCF 240 may determine that in the initial registration process of the UE 110a (e.g., Figure 9aDuring the process) whether an update of the UE policy is required, or determine that the update of the UE policy is required by the triggered network, that is, the UE policy is required after the initial registration. For example, during the initial registration process, the PCF 240 can determine whether an update of the UE policy is required based on the UE policy container (e.g., V2X policy) information received from the AMF 215 and the information associated with the access selection and PDU selection of the terminal (e.g., can be included in the Npcf_UEPolicyControl_Create request). Or, if an event such as changing the location of the UE 110a or changing the subscription information of the UE 110a occurs, for example, the slice service subscribed by the UE 110a (subscribed single network slice selection assistance information (S-NSSAI)), then the PCF 240 can determine whether an update of the UE policy is required. Additionally, as described in the part related to Figure 9a Step 911, the PCF 240 can determine to send the service policy / parameter information received from the UDR 230 (e.g., the V2X service policy parameters shown in ) to the UE 110a.

[0157] In step 925, the PCF 240 can send the service policy / parameter information (e.g., the V2X service policy parameters shown in ) to the AMF 215. At this time, if the V2X service policy parameters shown in are sent as the service policy / parameter information, the service policy / parameter information can include at least a part of the V2X service parameters shown in . According to an embodiment, the service policy / parameter information (e.g., the V2X service policy parameters shown in ) can be sent to the AMF 215 by being included in the Namf_Communication_N1N2MessageTransfer message. The Namf_Communication_N1N2MessageTransfer message can include SUPI, UE policy container, etc.

[0158] In step 927, if the UE 110a is registered in the network and is in a served state, the AMF 215 may determine to deliver the UE policy received from the PCF 240 to the UE 110a. If the UE 110a is registered in either 3GPP access or non-3GPP access, the AMF 215 may deliver the UE policy to the UE 110a via the access connected by registering the UE 110a. If the UE 110a is registered in both 3GPP access and non-3GPP access and is connectable, the AMF 215 may select a specific access according to the AMF 215 local policy and deliver the UE policy to the UE 110a. If the UE 110a is not registered in 3GPP access or non-3GPP access or is not connectable to 3GPP access or non-3GPP access, in step 935, the AMF 215 may notify the PCF 240 of the UE policy transmission failure via a specific message (e.g., Namf_Communication_N1N2TransferFailureNotification). If the AMF 215 determines to deliver the UE policy to the UE 110a via 3GPP access and the UE 110a is in the CM-IDLE state, the AMF 215 may send a paging message to the UE 110a and thus initiate a paging process via a network-triggered service request. The UE 110a that receives the paging request message may perform the paging process.

[0159] In steps 929 and 931, the AMF 215 may deliver the UE policy to the UE 110a. In this case, if the UE policy includes V2X services, the UE policy may include at least one of the V2X service policy parameters shown in . In this case, the AMF 215 may deliver a NAS message (e.g., a downlink NAS message or a management UE policy command message) for providing delivery parameters to the UE for the policy. To do so, the AMF 215 may include the NAS message in an NGAP downlink NAS transport or an NGAP UE context modification request message sent to the gNB 210. The parameter information for V2X services provided by the AMF 215 in steps 929 and 931 may be determined in a manner similar to steps 913 and 915. If the AMF 215 delivers an NGAP UE context modification request message to the gNB 210, the gNB 210 may store and apply the parameter information for V2X services received via the NGAP UE context modification request message in the context of the terminal. The gNB 210 may send a UE context modification response message to the AMF 215 as a response thereto and thus notify that the context of the terminal has been changed and applied according to the received information.

[0160] In step 933, the UE 110a that receives the UE policy information can store the obtained information and send a reply message to the AMF 215 notifying that the corresponding information has been received. In step 935, the AMF 215 can notify the PCF 240 that the service policy / parameter information (e.g., the V2X service policy parameters shown in ) has been sent to the UE 110a. In this case, the message sent in step 935 can be a Namf_N1MessageNotify message. Additionally, the PCF 240 can maintain the UE policy and notify the UDR 230 of the updated UE policy.

[0161] Figure 9c Illustrated is a process for a terminal to obtain service policy / parameter information from a network of a second communication system in a wireless communication system in response to a UE request according to an embodiment of the present disclosure. Figure 9c is an example of another process for the UE 110a to obtain service policy / parameter information (e.g., the V2X service policy parameters shown in ). According to Figure 9c the embodiment, the UE110a can obtain the UE policy by triggering a UE policy acquisition.

[0162] Referring to Figure 9c in step 937, the UE 110a can send a message requesting the UE policy to the AMF 215. In this case, the message requesting the UE policy can be a UE policy supply request message and can include a UE policy container (e.g., a V2X policy).

[0163] In step 939, the AMF 215 can send a message requesting UE policy information to the PCF 240. The message requesting UE policy information can be an Npcf_UEPolicyControl_Update request and can include the UE policy container (e.g., a V2X policy) received from the terminal.

[0164] In step 941, the PCF 240 that receives the message requesting UE policy information can determine whether a UE policy update is necessary. It can be similar to referring to Figure 9bThe described operations perform subsequent steps 941, step 943, step 945, step 947, step 949, step 951, and step 953. For example, the PCF 240 may send UE policy information to the AMF 215 in step 943, and the AMF 215 may determine to deliver the UE policy to the UE 110a and deliver it in steps 945, 947, and 949. In step 951, in response to the UE policy, the UE 110a may send a response message to the AMF 215, and in step 953, the AMF 215 may send a message to the PCF 240 indicating whether the UE policy transmission is successful.

[0165] Refer to Figure 9a 、 Figure 9b and Figure 9c The process for obtaining service parameters / policies described can be similarly applied to other terminals (e.g., UE 110b, UE 110c, UE 110d, UE 200a, and UE 200b).

[0166] Figure 10 Illustrates a process for a terminal to request and obtain radio resources for direct communication from a network entity of a second communication system in a wireless communication system according to an embodiment of the present disclosure.

[0167] Refer to Figure 10 , in step 1001, the base station 210 may obtain V2X service subscription information, policy, and parameter information from the AMF 215. For example, the base station 210 may obtain V2X service subscription information and policy and parameter information as in Figure 9a step 913 of Figure 9a step 917 of Figure 9b step 929 of

[0168] In step 1003, the UE 110a may determine to use LTE PC5 to send data. In step 1005, the UE 110a may send a sidelink (SL) resource request message for requesting LTE PC5 resources to the base station 210. The SL resource request message may include at least one of the following: PPP (and / or PPPR) requested by the data to be sent by the UE 110a, the destination address of the data to be sent by the UE 110a (e.g., the destination layer 2 ID), and the PQI and QoS flow identifier (QFI) indicating the PQI required by the data to be sent by the UE 110a.

[0169] Upon the request of UE 110a, the base station 210 determines the radio resources to be allocated to UE 110a. To determine the radio resources to be allocated to UE 110a, the base station 210 may use QoS mapping information (e.g., 'the mapping of PPP and 5QI' and / or 'the mapping of PPPR and 5QI'). For example, if PQI is received from UE 110a in step 1005, the base station 210 may use the QoS mapping information to convert the PQI received from UE 110a into a PPP (and / or PPPR) value and determine the radio resources to be allocated to UE 110a. Alternatively, if PPP (and / or PPPR) is received from UE 110a in step 1005, the base station 210 may use the QoS mapping information to convert the PPP (and / or PPPR) received from UE 110a into a PQI value and determine the radio resources to be allocated to UE 110a. Herein, it may be based on Figure 9a step 913 of Figure 9a step 917 of Figure 9b and step 929 of

[0170] to obtain the QoS mapping information from the AMF 215. Alternatively, the QoS mapping information may be pre-configured in the base station 210, and the base station 210 may use the pre-configured information.

[0171] In the embodiment described with reference to Figure 10 UE 110a determines to use LTE PC5. According to another embodiment, NR PC5 may be used instead of LTE PC5. In this case, Figure 10 each step of

[0172] In step 1003, UE 110a may determine to use NR PC5 to send data. Next, in step 1005, UE 110a may send a SL resource request message to base station 210 for requesting NR PC5 resources. The SL resource request message may include at least one of the following: PPP (and / or PPPR) requested by the data to be sent by UE 110a, the destination address of the data to be sent by UE 110a (e.g., destination layer 2 ID), and the PQI and QFI indicating the PQI required by the data to be sent by UE 110a.

[0173] According to the request of UE 110a, base station 210 determines the radio resources to be allocated to UE 110a. To determine the radio resources to be allocated to UE 110a, base station 210 may use QoS mapping information (e.g.,'mapping of PPP and 5QI' and / or'mapping of PPPR and 5QI'). For example, if PQI is received from UE 110a in step 1005, base station 210 may use the QoS mapping information to convert the PQI received from UE 110a into a PPP (and / or PPPR) value and determine the radio resources to be allocated to UE 110a. Alternatively, if PPP (and / or PPPR) is received from UE 110a in step 1005, base station 210 may use the QoS mapping information to convert the PPP (and / or PPPR) received from UE 110a into a PQI value and determine the radio resources to be allocated to UE 110a. Herein, the QoS mapping information may be obtained from AMF 215 according to Figure 9a step 913 of Figure 9a step 917 of Figure 9b step 929 of

[0174] In step 1007, base station 210 may send a SL resource response message to UE 110a. The SL resource response message may include information on the radio resources allocated to UE 110a. Herein, the radio resources may include at least one of the resources exclusively allocated to UE 110a or the resources shared with other UEs. In step 1009, UE 110a may send data. UE 110a may send data by using at least a part of the radio resources allocated by base station 210.

[0175] In reference to Figure 10In the described embodiment, the UE 110a may request resources for direct communication from the base station 210. At this time, the UE 110a may selectively request one of the LTE PC5 resources or the NR PC5 resources. Herein, the LTE PC5 resource request and the NR PC5 resource request may be distinguished according to one of various methods.

[0176] According to an embodiment, the LTE PC5 resource request and the NR PC5 resource request may be distinguished by being performed by different messages. For example, if the UE 110a requests PC5 resources from the base station 210, the UE 110a may use different SL resource request messages to distinguish the LTE PC5 resource request and the NR PC5 resource request. Accordingly, the base station 210 may determine whether the requested resource is an LTE PC5 resource or an NR PC5 resource by identifying the type of the SL resource request message.

[0177] According to an embodiment, the LTE PC5 resource request and the NR PC5 resource request may be distinguished by an indication in the message. For example, the same SL resource request message is used, but the UE 110a may include an indication indicating one of LTE PC5 or NR PC5 in the SL resource request message. Accordingly, the base station 210 may determine whether the requested resource is an LTE PC5 resource or an NR PC5 resource by identifying the value of the indication included in the SL resource request message.

[0178] According to an embodiment, the LTE PC5 resource request and the NR PC5 resource request may be distinguished using the value of the destination address (e.g., destination layer 2 ID) included in the message. For example, the value for indicating the destination address may be divided into a first range corresponding to the LTE PC5 resource and a second range corresponding to the NR PC5 resource. Specifically, when using one SL resource request message, the UE 110a may use different values to distinguish the destination layer 2 ID indicating LTE PC5 and the destination layer 2 ID indicating NR PC5. Accordingly, the base station 210 may determine whether the requested resource is an LTE PC5 resource or an NR PC5 resource by identifying the destination address value included in the SL resource request message.

[0179] According to an embodiment, the LTE PC5 resource request and the NR PC5 resource request can be distinguished based on the type of required parameters included in the message. For example, a message requesting an LTE PC5 resource may include parameters for LTE-based direct communication, while a message requesting a 5G PC5 resource may include parameters for 5G-based direct communication. Specifically, if an LTE PC5 resource is requested, the UE 110a may include in the SL resource request message only the PPP (and / or PPPR) required for data, while excluding the 5QI required for data. Similarly, additionally, if an NR PC5 resource is requested, the UE 110a may include in the SL resource request message only the 5QI required for data, while excluding the PPP (and / or PPPR) required for data. Accordingly, the base station 210 can determine whether the requested resource is an LTE PC5 resource or an NR PC5 resource by identifying the type of QoS-related parameter included in the SL resource request message.

[0180] Figure 11 A process for a terminal to request and obtain radio resources for direct communication from a network entity of a first communication system in a wireless communication system according to an embodiment of the present disclosure is shown.

[0181] Referring to Figure 11 , in step 1101, the base station 210 may obtain V2X service subscription information and policy and parameter information from the MME 125. For example, the base station 210 may obtain the V2X service subscription information and the policy and parameter information in the same manner as in Figure 8a step 809 of

[0182] In step 1103, the UE 110a may determine to use LTE PC5 to transmit data. In step 1105, the UE 110a may send an SL resource request message for requesting an LTE PC5 resource to the base station 120. The SL resource request message may include at least one of the following: the PPP (and / or PPPR) required for the data to be transmitted by the UE 110a, the destination address of the data to be transmitted by the UE 110a (e.g., the destination layer 2 ID), and the PQI required for the data to be transmitted by the UE 110a and the QFI indicating the PQI.

[0183] In response to a request from UE 110a, base station 120 determines radio resources to be allocated to UE 110a. To determine the radio resources to be allocated to UE 110a, base station 120 may use QoS mapping information (e.g., 'the mapping of PPP and 5QI' and / or 'the mapping of PPPR and 5QI'). For example, if PQI is received from UE 110a in step 1105, base station 120 may use the QoS mapping information to convert the PQI received from UE 110a into a PPP (and / or PPPR) value and determine the radio resources to be allocated to UE 110a. Alternatively, if PPP (and / or PPPR) is received from UE 110a in step 1105, base station 210 may use the QoS mapping information to convert the PPP (and / or PPPR) received from UE 110a into a PQI value and determine the radio resources to be allocated to UE 110a. Herein, the QoS mapping information may be obtained from MME 125 according to Figure 8a step 809 thereof. Alternatively, the QoS mapping information may be pre-configured in base station 120, and base station 120 may use the pre-configured information.

[0184] In step 1107, base station 120 may send an SL resource response message. The SL resource response message may include radio resource information allocated to UE 110a. Herein, the radio resources may include at least one of resources exclusively allocated to UE 110a or resources used in competition with other UEs. In step 1109, UE 110a may send data. UE 110a may send data by using at least a part of the radio resources allocated by base station 120.

[0185] In the embodiment described with reference to Figure 11 UE 110a determines to use LTE PC5. According to another embodiment, NR PC5 may be used instead of LTE PC5. In this case, Figure 10 each step of

[0186] In step 1103, UE 110a may determine to use NR PC5 to send data. Next, in step 1105, UE 110a may send an SL resource request message to base station 120 for requesting NR PC5 resources. The SL resource request message may include at least one of the following: PPP (and / or PPPR) required for the data to be sent by UE 110a, the destination address of the data to be sent by UE 110a (e.g., the destination layer 2 ID), and PQI and QFI indicating PQI required for the data to be sent by UE 110a.

[0187] Upon request from UE 110a, base station 120 determines the radio resources to be allocated to UE 110a. To determine the radio resources to be allocated to UE 110a, base station 120 may use QoS mapping information (e.g., 'the mapping of PPP and 5QI' and / or 'the mapping of PPPR and 5QI'). For example, if PQI is received from UE 110a in step 1105, base station 120 may use the QoS mapping information to convert the received PQI from UE 110a into a PPP (and / or PPPR) value and determine the radio resources to be allocated to UE 110a. Alternatively, if PPP (and / or PPPR) is received from UE 110a in step 1105, it may use the QoS mapping information stored in base station 120 to convert the received PPP (and / or PPPR) from UE 110a into a PQI value and determine the radio resources to be allocated to UE 110a. Herein, the QoS mapping information may be obtained from MME 125 according to Figure 8a step 809. Alternatively, the QoS mapping information may be pre-configured in base station 120, and base station 120 may use the pre-configured information.

[0188] In step 1107, base station 120 may send an SL resource response message. The SL resource response message may include information on the radio resources allocated to UE 110a. Herein, the radio resources may include at least one of the resources exclusively allocated to UE 110a or the resources shared with other UEs. In step 1109, UE 110a may send data. UE 110a may send data by using at least a part of the radio resources allocated from base station 210.

[0189] In the embodiment described with reference to Figure 11 UE 110a may request resources for direct communication from base station 120. At this time, UE 110a may selectively request one of the LTE PC5 resources or the NR PC5 resources. Herein, the LTE PC5 resource request and the NR PC5 resource request may be distinguished according to one of various methods.

[0190] According to an embodiment, the LTE PC5 resource request and the NR PC5 resource request may be distinguished by being performed by different messages. For example, if UE 110a requests PC5 resources from base station 120, UE 110a may use different SL resource request messages to distinguish the LTE PC5 resource request and the NR PC5 resource request. Therefore, base station 120 may determine whether the requested resource is an LTE PC5 resource or an NR PC5 resource by identifying the type of the SL resource request message.

[0191] According to an embodiment, an LTE PC5 resource request and an NR PC5 resource request can be distinguished by an indication in a message. For example, the same SL resource request message is used, but UE 110a can include an indication indicating one of LTE PC5 or NR PC5 in the SL resource request message. Accordingly, the base station 120 can determine whether the requested resource is an LTE PC5 resource or an NR PC5 resource by identifying the value of the indication included in the SL resource request message.

[0192] According to an embodiment, an LTE PC5 resource request and an NR PC5 resource request can be distinguished using the value of a destination address (e.g., a destination layer 2 ID) included in a message. For example, the value used to indicate the destination address can be divided into a first range corresponding to an LTE PC5 resource and a second range corresponding to an NR PC5 resource. Specifically, when using one SL resource request message, UE 110a can use different values to distinguish the destination layer 2 ID indicating LTE PC5 and the destination layer 2 ID indicating NR PC5. Accordingly, the base station 210 can determine whether the requested resource is an LTE PC5 resource or an NR PC5 resource by identifying the destination address value included in the SL resource request message.

[0193] According to an embodiment, an LTE PC5 resource request and an NR PC5 resource request can be distinguished based on the type of required parameters included in a message. For example, a message requesting an LTE PC5 resource can include parameters for LTE-based direct communication, while a message requesting a 5G PC5 resource can include parameters for 5G-based direct communication. Specifically, if an LTE PC5 resource is requested, UE 110a can include only the PPP (and / or PPPR) required for data in the SL resource request message and exclude the 5QI required for data. Similarly, if an NR PC5 resource is requested, UE 110a can include only the 5QI required for data in the SL resource request message and exclude the PPP (and / or PPPR) required for data. Accordingly, the base station 210 can determine whether the requested resource is an LTE PC5 resource or an NR PC5 resource by identifying the type of QoS-related parameters included in the SL resource request message.

[0194] Figure 12 A process for establishing a connection between a base station and a second communication system in a wireless communication system according to an embodiment of the present disclosure is shown. Figure 12 Signaling between the gNB 210 and the AMF 215 is shown. The gNB 210 can be referred to as the NG-RAN.

[0195] Refer to Figure 12, in step 1201, gNB 210 sends an NG setup request message to AMF 215. The NG setup request message may include V2X capability information. In step 1203, AMF 215 sends an NG setup response message to gNB 210. That is, gNB 210 and AMF 215 can exchange the information used between them and perform an N2 setup procedure to configure the connection information. The N2 setup procedure is performed regardless of the UE.

[0196] According to the N2 setup procedure, gNB 210 and AMF 215 can obtain the information necessary for their interconnection and obtain the information of the capabilities supported by each entity. According to an embodiment, if performing the NG setup procedure with AMF 215, gNB 210 can notify AMF 215 whether it supports V2X and whether there is cross-RAT PC5 control capability. Herein, the cross-RAT PC5 control capability may refer to the capability of gNB 210 to support both LTE PC5 and NR PC5 for V2X PC5 communication. Additionally, the cross-RAT PC5 control capability may refer to the capability of gNB 210 to set and provide the information of NR PC5 to a terminal in the LTE RAT or to set and provide the information of LTE PC5 to a terminal in the NR RAT. The capability information can be delivered to AMF 215 by being included in the message sent in step 1201 in the form of information such as the radio capability of gNB 210 or the V2X capability of gNB 210. AMF 215 can complete the NG setup procedure by sending a message to gNB 210 in step 1203.

[0197] Figure 13 Shows a procedure for establishing a connection between a base station and a first communication system in a wireless communication system according to an embodiment of the present disclosure. Figure 13 Shows the signaling between eNB 120 and MME 125. eNB 120 can be referred to as E-UTRAN.

[0198] Refer to Figure 13 , in step 1301, eNB 120 sends an S1 setup request message to MME 125. The S1 setup request message may include V2X capability information. In step 1303, MME 125 sends an S1 setup response message to eNB 120. eNB 120 and MME 125 can exchange the information used between them and perform an S1 setup procedure to configure the connection information. The S1 setup procedure is performed regardless of the UE.

[0199] According to the S1 setup procedure, the eNB 120 and the MME 125 can obtain the information necessary for their interconnection and the information on the functions supported by each entity. According to an embodiment, if the S1 setup procedure is performed together with the MME 125, the eNB 120 can notify the MME 125 whether it supports V2X and whether it has cross-RAT PC5 control capabilities. Herein, the cross-RAT PC5 control capabilities may refer to the ability of the eNB 120 to support both LTE PC5 and NR PC5 for V2X PC5 functions. Additionally, the cross-RAT PC5 control capabilities may refer to the ability of the eNB 120 to set and provide NR PC5 information to the terminal in the LTE RAT or to set and provide LTE PC5 information to the terminal in the NR RAT. The capability information can be delivered to the MME 125 by being included in the message sent in step 1301 in the form of information such as the radio capabilities of the eNB 120 or the V2X capabilities of the eNB 120. The MME 125 can complete the NG setup procedure by sending a message to the eNB 120 in step 1303.

[0200] UEs according to various embodiments of the present disclosure can obtain function information supported by the network. Thereafter, a process for a UE to identify functions supported by the network (e.g., cross-RAT PC5 control functions) through signaling from a base station is described by Figures 14a to 14b way.

[0201] Figure 14a FIG. 14 shows a process for a terminal to obtain system information from a network in a wireless communication system according to an embodiment of the present disclosure. FIG. 14 shows the signaling between the terminal 110a and the base station. In Figure 14a this, the base station exemplifies the eNB 120. The eNB 120 may be referred to as the E-UTRAN.

[0202] Referring to Figure 14a FIG. 14, the terminal 110a accessing the EPC network in step 1401 can receive system information from the base station (eNB) 120. The system information in step 1401 may include the functions supported by the base station 120. The functions supported by the base station 120 may include cross-RAT PC5 control capability information. The system information in step 1401 may include PC5 resource information. The PC5 resource information may include LTE PC5 resource pool or NR PC5 resource pool information.

[0203] The terminal 110a that receives the system information in step 1401 from the base station 120 can perform PC5 operations based on at least one of the functional information supported by the base station 120 and the PC5 resource pool information included in the system information. For example, if the base station 120 supports the cross-RAT PC5 control function, the terminal 110a can send an LTE PC5 or NR PC5 resource request message to the base station 120. If the NR PC5 resource pool information is included in the system information, the terminal 110a can store the NR PC5 resource pool information received from the base station 120 and use it for NR PC5 communication. Or, for example, if the base station 120 does not support the cross-RAT PC5 control function, the terminal 110a can send an LTE PC5 resource request message to the base station 120 and may not send an NR PC5 resource request message.

[0204] If the base station 120 does not support the cross-RAT PC5 control function, the base station 120 can include an indication indicating the non-support of the cross-RAT PC5 control function in the message in step 1401 (i.e., the system information (SI) message). Or, the base station 120 may not include the cross-RAT PC5 control function-related information in the message in step 1401. The terminal 110a can identify that the cross-RAT PC5 control function-related information is not included in the message in step 1401. The terminal 110a can determine that the base station 120 does not support the cross-RAT PC5 control function based on the identification.

[0205] According to another embodiment, instead of the SI message in step 1401, the message in step 811 (e.g., RRC connection reconfiguration / initial attachment response) can be used.

[0206] Figure 14b Another process for a terminal to obtain system information from a network in a wireless communication system according to an embodiment of the present disclosure is shown. FIG. 14 shows the signaling between the terminal 110a and the base station. In Figure 14b the base station is illustrated as gNB 210. The gNB 210 can be referred to as the NG-RAN.

[0207] Referring to Figure 14b in step 1451, the terminal 110a accessing the 5G network can receive system information from the base station (gNB) 210. The system information in step 1451 can include the functionality supported by the base station 210. The functionality supported by the base station 210 can include cross-RAT PC5 control capability information. The system information in step 1401 can include PC5 resource information. The PC5 resource information can include an LTE PC5 resource pool or NR PC5 resource pool information.

[0208] The terminal 110a that receives the system information of step 1451 from the base station 210 can perform PC5 operations based on at least one of the functional information supported by the base station 210 and the PC5 resource pool information included in the system information. For example, if the base station 210 supports the cross-RAT PC5 control function, the terminal 110a can send an LTE PC5 or NR PC5 resource request message to the base station 210. If the system information includes LTE PC5 resource pool information, the terminal 110a can store the LTE PC5 resource pool information received from the base station 210 and use it for LTE PC5 communication. Or, for example, if the base station 210 does not support the cross-RAT PC5 control function, the terminal 110a can send an NR PC5 resource request message to the base station 210 and may not send an LTE PC5 resource request message.

[0209] If the base station 210 does not support the cross-RAT PC5 control function, the base station 210 can include an indication indicating the non-support of the cross-RAT PC5 control function in the message of step 1451 (i.e., the SI message). Or, the base station 210 may not include cross-RAT PC5 control function-related information in the message of step 1451. The terminal 110a can identify that the cross-RAT PC5 control function-related information is not included in the message of step 1451. The terminal 110a can determine that the base station 210 does not support the cross-RAT PC5 control function based on the identification.

[0210] According to another embodiment, instead of the SI that is the message of step 1451, the message of step 915 (registration acceptance) message can be used. The message of step 915 (registration acceptance) can be included in the RRC connection reconfiguration message and sent.

[0211] The terminal according to various embodiments of the present disclosure can obtain function information supported by the network. The terminal 110a can be based on Figure 9a the process shown and register in a 5G system (e.g., 5GC).

[0212] In steps 905 and 907 of FIG. 9, the terminal 110a can send a registration request message to the AMF 215 via the base station 210. The registration request message can include the capability information of the terminal in the form of 5GS mobility management (5GMM) capability or S1 UE network capability. For example, the capability information of the terminal can be the PC5 capability for V2X (e.g., only LTE PC5, only NR PC5, both LTE PC5 and NR PC5). Additionally, for example, the capability information of the terminal can be the cross-RAT PC5 capability.

[0213] In step 909, the AMF 215 that receives the registration request message of step 907 may obtain UE subscription information from the UDM 235. The UE subscription information may include at least one or more of the "V2X service authorization" indication, the UE-PC5-AMBR per PC5 RAT, and the cross-RAT PC5 control authorization.

[0214] According to another embodiment, in step 911, the AMF 215 may obtain policy information (e.g., V2X policy information, PC5 policy information, etc.) from the PCF 240. The policy information may include at least one or more of the "V2X service authorization" indication, the UE-PC5-AMBR per PC5 RAT, and the cross-RAT PC5 control authorization.

[0215] The AMF 215 may determine the information to be included in the registration acceptance message based on at least one of the registration request message received from the terminal 110a, the UE subscription information received from the UDM 235, and the policy information received from the PCF 240. For example, if the terminal 110a supports the NR PC5 function or the cross-RAT PC5 capability, and the cross-RAT PC5 authorization information is included in the UE subscription information or the policy information, the AMF 215 may determine to provide the cross-RAT PC5 scheduling function for the terminal 110a. The registration acceptance message may include information indicating that cross-RAT PC5 scheduling is possible (e.g., the "cross-RAT PC5 control is authorized" indication). In steps 913 and 915, the AMF 215 may send the registration acceptance message to the base station 210 and the terminal 110a. The AMF 215 may send the registration acceptance message including the information indicating that cross-RAT PC5 scheduling is possible to the base station 210. The AMF 215 may send the registration acceptance message including the information indicating that cross-RAT PC5 scheduling is possible to the terminal 110a via the base station 210.

[0216] The base station 210 that receives the registration acceptance message from the AMF 215 may identify that the terminal 110a is authorized to use the cross-RAT PC5 scheduling function based on the information included in the registration acceptance message.

[0217] The terminal 110a that receives the registration acceptance message from the AMF 215 may identify that the terminal 110a is authorized to use the cross-RAT PC5 scheduling function based on the information included in the registration acceptance message.

[0218] In some embodiments, the terminal 110a authorized by the AMF 215 for cross-RAT PC5 scheduling may operate within coverage in both NR PC5 and LTE PC5. Thus, in step 1401 of FIG. 14, it may store the LTE PC5 resource pool information received from the base station 210 and use it for LTE PC5 communication.

[0219] Additionally, in some embodiments, the terminal authorized by the AMF 215 for cross-RAT PC5 scheduling may perform Figure 10 the process. In step 1003, the terminal 110a may determine the resources to be sent to LTE PC5. In step 1005, the terminal 110a may send an LTE PC5 resource request message to the base station 210 (e.g., gNB). The base station 210 may determine that the terminal 110a is a terminal authorized to make an LTE PC5 resource request based on the information received from the AMF 215 in step 1001 (e.g., information indicating that cross-RAT PC5 scheduling is possible). Thus, in step 1007, the base station 210 may allocate LTE PC5 resources to the terminal 110a. In step 1009, the terminal 110a allocated with LTE PC5 resources from the base station 210 may send data to LTE PC5.

[0220] Additionally, in some embodiments, the terminal not authorized by the AMF 215 for cross-RAT PC5 scheduling may operate within coverage in NR PC5 while operating outside the coverage in LTE PC5.

[0221] Additionally, in some embodiments, in LTE PC5 communication, the terminal not authorized by the AMF 215 for cross-RAT PC5 scheduling may not perform Figure 10 the process.

[0222] Additionally, in some embodiments, the terminal authorized by the AMF 215 for cross-RAT PC5 scheduling may perform Figure 10 the process. In step 1003, the terminal 110a may determine the resources to be sent to LTE PC5. In step 1005, the terminal 110a may send an LTE PC5 resource request message to the base station 210. Based on the information received from the AMF 215 in step 1001 (e.g., information indicating that cross-RAT PC5 scheduling is possible), the base station 210 may determine that the terminal 110a is a terminal not authorized for LTE PC5 resource requests. Thus, in step 1007, the base station 210 may not allocate LTE PC5 resources to the terminal 110a. In step 1009, the terminal 110a not allocated with LTE PC5 resources from the base station 210 may send data to LTE PC5 in an out-of-coverage mode.

[0223] A terminal according to various embodiments of the present disclosure may obtain function information supported by a network. The terminal 110a may register in the EPC system by executing the Figure 8a process shown.

[0224] In steps 801 and 803 of FIG. 8, the terminal 110a may send an initial attachment request message to the MME 125 via a base station 120 (e.g., eNB). The initial attachment request message may include UE capability information in the form of UE network capabilities. For example, the UE capability information may include PC5 capabilities for V2X (e.g., only LTE PC5, only NR PC5, both LTE PC5 and NR PC5), cross-RAT PC5 capabilities, etc.

[0225] In step 805, the MME 125 that receives the initial attachment request message of step 803 may obtain UE subscription information from the HSS 135. The UE subscription information may include at least one or more of an indication of "V2X service authorization", UE-PC5-AMBR per PC5 RAT, and cross-RAT PC5 control authorization.

[0226] The MME 125 may determine the information to be included in the initial context setup request / initial attachment response message based on at least one of the initial attachment request message received from the terminal 110a and the UE subscription information received from the HSS 135. For example, if the terminal 110a supports the NR PC5 function or cross-RAT PC5 capabilities, and the UE subscription information includes cross-RAT PC5 authorization information, the MME 125 may determine to provide the cross-RAT PC5 scheduling function for the terminal 110a. The MME 125 may include information indicating that cross-RAT PC5 scheduling is possible (e.g., an indication of "cross-RAT PC5 control authorization") in the initial context setup request / initial attachment response message. In steps 809 to 811, the MME 125 may send an initial context setup request / initial attachment response message to the base station 120 and the terminal 110a. In step 809, the MME 125 may send an initial context setup request / initial attachment response message to the base station 120. In step 809, the MME 125 may send an initial context setup request / initial attachment response message to the terminal 110a via the base station 120.

[0227] The base station 120 that receives the initial context setup request message from the MME 125 may identify that the terminal 110a is authorized to use the cross-RAT PC5 scheduling function based on the information included in the initial context setup request message.

[0228] The terminal 110a that receives the initial attachment response message from the MME 125 can identify that the terminal 110a is authorized to use the cross-RAT PC5 scheduling function based on the information included in the initial attachment response message.

[0229] In addition, in some embodiments, a terminal authorized by the MME for cross-RAT PC5 scheduling can operate within the coverage in both NR PC5 and LTE PC5. Thus, in step 1401 of FIG. 14, the NR PC5 resource pool information received from the base station 120 can be stored and used for NR PC5 communication.

[0230] In addition, in some embodiments, a terminal authorized by the MME for cross-RAT PC5 scheduling can perform Figure 11 the process. In step 1103, the terminal 110a can determine the resources to be sent to NR PC5. In step 1105, the terminal 110a can send an NR PC5 resource request message to the base station 120. Based on the information received from the MME 125 in step 1101 (e.g., information indicating that cross-RAT PC5 scheduling is possible), the base station 120 can determine that the terminal 110a is a terminal authorized to make an NR PC5 resource request. Thus, in step 1107, the base station 120 can allocate NR PC5 resources to the terminal 110a. In step 1109, the terminal 110a that has been allocated the NR PC5 resources from the base station 120 can send data to NR PC5.

[0231] In addition, in some embodiments, a terminal not authorized by the MME for cross-RAT PC5 scheduling can operate within the coverage in LTE PC5, while operating outside the coverage in NR PC5.

[0232] In addition, in some embodiments, in NR PC5 communication, a terminal not authorized by the MME for cross-RAT PC5 scheduling may not perform Figure 11 the process.

[0233] In addition, in some embodiments, a terminal not authorized by the MME 125 for cross-RAT PC5 scheduling can perform Figure 11Procedure. In step 1103, the terminal 110a may determine to send resources to NR PC5. In step 1105, the terminal 110a may send an NR PC5 resource request message to the base station 120. Based on the information received from the MME 125 in step 1101 (e.g., information indicating that cross-RAT PC5 scheduling is possible), the base station 120 may determine that the terminal 110a is a terminal not authorized to make an NR PC5 resource request. Therefore, in step 1107, the base station 120 may not allocate NR PC5 resources to the terminal 110a. In step 1109, the terminal 110a that has not been allocated NR PC5 resources from the base station 120 may send data to NR PC5 in out-of-coverage mode.

[0234] Figure 3 The interworking structure of a 5G system and an EPC system according to various embodiments of the present disclosure has been shown. The AMF 215 and the MME 125 may be connected through the N26 interface.

[0235] The terminal 110a according to various embodiments of the present disclosure may be registered in a 5G system (e.g., 5GC) and connected to the AMF 215. The AMF 215 may store the UE capability information (e.g., including at least one of PC5 capabilities for V2X (LTE PC5 only, NR PC5 only, both LTE PC5 and NR PC5), cross-RAT PC5 capabilities) received from the terminal in Figure 9a step 907. The AMF 215 may store the UE capability information as UE context. The AMF 215 may store the UE subscription information or policy information received from the UDM 235 or the PCF 240 in Figure 9a steps 909 to 911. The AMF 215 may store the UE subscription information or policy information as UE context. The UE subscription information or policy information may include at least one or more of the following information: PC5 authorization information (whether the UE is authorized to perform V2X communication as a vehicle UE, a pedestrian UE, or both through the PC5 reference point, including for LTE PC5 and for NR PC5), "V2X service authorization" indication, UE-PC5-AMBR per PC5 RAT, cross-RAT PC5 control authorization, PLMN list (the PLMN list for which the UE is authorized to perform V2X communication through the PC5 reference point). For each PLMN in the list, it includes the (one or more) RATs and PC5 QoS parameters for which the UE is authorized to perform V2X communication through the PC5 reference point.

[0236] According to various embodiments of the present disclosure, the terminal 110a registered and connected to the AMF 215 in the 5G system can move to the EPC system (e.g., handover, idle mode mobility, connected mode mobility, etc.). Therefore, the AMF 215 can send the UE context stored in the AMF 215 to the MME 125 via the N26 interface. The UE context may include UE capability information, UE subscription information, policy information, etc. The MME 125 can store and use the UE context received from the AMF 215.

[0237] For example, the UE context may include information indicating that the terminal 110a can use the LTE PC5 function and the NR PC5 function and that the terminal 110a is an authorized terminal for cross-RAT PC5 control. Based on the UE context, the MME 125 can determine to provide the cross-RAT PC5 scheduling function for the UE 110a.

[0238] The AMF 215 can determine the UE context information to be sent to the MME 125. For example, the AMF 215 can identify whether the PLMN ID of the MME 125 is included in the PLMN list of the UE context. If the PLMN list includes the PLMN ID of the MME 125, the AMF 215 can include the PLMN list in the UE context information sent to the MME 125. If the PLMN list does not include the PLMN ID of the MME 125, the AMF 215 may not include the PLMN list in the UE context information sent to the MME 125.

[0239] To send the UE context to the MME 125, the AMF 215 can convert the UE context in 5G format into the UE context in EPS format. For example, the UE context converted into EPS format can be referred to as the mapped EPS UE context for V2X or the mapped EPS UE context. The AMF 215 can send the UE context converted into EPS format to the MME 125 via the N26 interface. The UE context converted into EPS format can be included in messages such as relocation request, relocation complete notification, and context response and sent to the MME 125.

[0240] The MME 125 can include information indicating that cross-RAT PC5 scheduling is possible (e.g., "cross-RAT PC5 control authorization" indication) in a message (e.g., initial context setup request, handover request, etc.) sent to the base station 120 to which the UE 110a is connected. The base station 120 receiving the message from the MME 125 can identify that the terminal 110a is authorized to use the cross-RAT PC5 scheduling function based on the information included in the message.

[0241] The MME 125 may include, in a message sent to the terminal 110a (e.g., TAU acceptance, etc.), information indicating that cross-RAT PC5 scheduling is possible (e.g., a "cross-RAT PC5 control authorization" indication). The terminal 110a that receives the message from the MME 125 may identify, based on the information included in the message, that the terminal 110a is authorized to use the cross-RAT PC5 scheduling function.

[0242] The terminal 110a according to various embodiments of the present disclosure may be registered in the EPC system and connected to the MME 125. The MME 125 may store the UE capability information (e.g., PC5 capabilities for V2X (LTE PC5 only, NR PC5 only, both LTE PC5 and NR PC5), cross-RAT PC5 capabilities) received from the terminal in Figure 8a step 803. The MME may store the UE capability information as UE context. The MME 125 may store the UE subscription information received from the HSS 135 in Figure 8a step 807. The MME 125 may store the UE subscription information as UE context. The UE subscription information may include at least one or more of the following information: PC5 authorization information (whether the UE is authorized to perform V2X communication as a vehicle UE, a pedestrian UE, or both through the PC5 reference point, including for LTE PC5 and for NR PC5), a "V2X service authorization" indication, UE-PC5-AMBR per PC5 RAT (including UE-PC5-AMBR for LTE PC5 and UE-PC5-AMBR for NR PC5), cross-RAT PC5 control authorization, a PLMN list (a list of PLMNs for which the UE is authorized to perform V2X communication through the PC5 reference point). For each PLMN in the list, it includes the (one or more) RATs and PC5 QoS parameters for which the UE is authorized to perform V2X communication through the PC5 reference point.

[0243] According to various embodiments of the present disclosure, the terminal 110a registered in the EPC system and connected to the MME 125 may move to the 5G system (e.g., handover, idle mode mobility, connected mode mobility, etc.). Accordingly, the MME 125 may send the UE context stored in the MME 125 to the AMF 215 via the N26 interface. The UE context may include UE capability information, UE subscription information, policy information, etc.

[0244] The MME 125 may determine the UE context information to be sent to the AMF 215. For example, the MME 125 may identify whether the PLMN ID of the AMF 215 is included in the PLMN list of the UE context. If the PLMN list includes the PLMN ID of the AMF 215, the MME 125 may include the PLMN list in the UE context information sent to the AMF 215. If the PLMN list does not include the PLMN ID of the AMF 215, the MME 125 may not include the PLMN list in the UE context information sent to the AMF 215.

[0245] The MME 125 may send the UE context in EPS format to the AMF 215 via the N26 interface. The UE context in EPS format may be included in messages such as a forward relocation request, a forward relocation complete notification acknowledgment, and a context response and sent to the AMF 215.

[0246] The AMF 215 may store and use the UE context received from the MME 125. For example, the AMF 215 may convert the UE context in EPS format received from the MME 125 into a UE context in 5G format. The UE context may include information indicating that the terminal 110a may use the LTE PC5 function and the NR PC5 function and that the terminal 110a is authorized for cross-RAT PC5 control. Based on the UE context, the AMF 215 may determine to provide the cross-RAT PC5 scheduling function to the UE 110a.

[0247] The AMF 215 may include information indicating that cross-RAT PC5 scheduling is possible (e.g., a "cross-RAT PC5 control authorization" indication) in a message (e.g., an initial context setup request, a handover request, etc.) sent to the base station 210 connected to the terminal 110a. The base station 210 that receives the message from the AMF 215 may identify, based on the information included in the message, that the terminal 110a is authorized to use the cross-RAT PC5 scheduling function.

[0248] The AMF 215 may include information indicating that cross-RAT PC5 scheduling is possible (e.g., a "cross-RAT PC5 control authorization" indication) in a message (e.g., a registration acceptance, etc.) sent to the terminal 110a. The terminal 110a that receives the message from the AMF 215 may identify, based on the information included in the message, that the terminal 110a is authorized to use the cross-RAT PC5 scheduling function.

[0249] Various embodiments of the present disclosure relate to the cross-RAT PC5 control capabilities of a terminal. The UE capability information of the terminal may include information (e.g., an information element (IE)) for indicating whether cross-RAT PC5 control capabilities are supported. The cross-RAT PC5 control capabilities may indicate the ability of the eNB 120 to configure information for NR PC5 in the LTE RAT and provide it to the terminal or configure information for LTE PC5 in the NR RAT and provide it to the terminal. The policy information delivered by a policy-related entity (e.g., the PCF 240) to an authorization management entity (e.g., the AMF 215) may include at least one or more of the information such as "V2X service authorization" indication, UE-PC5-AMBR per PC5 RAT, and cross-RAT PC5 control authorization.

[0250] In various embodiments of the present disclosure, a message (e.g., a registration acceptance message) between a terminal, a base station (e.g., the eNB 120 or the gNB 120), and a core network entity (e.g., the AMF 215) may include information (e.g., a "cross-RAT PC5 control authorization" indication) indicating that cross-RAT PC5 scheduling is possible. Depending on whether the terminal is authorized by the AMF for cross-RAT PC5 scheduling, the terminal may perform LTE PC5 communication in an in-coverage mode or an out-of-coverage mode. Additionally, depending on whether the terminal is authorized by the MME for cross-RAT PC5 scheduling, the terminal may perform NR PC5 communication in an in-coverage mode or an out-of-coverage mode.

[0251] In some embodiments, the base station may determine whether the terminal is authorized for cross-RAT PC5 scheduling based on the information obtained from the AMF. The base station may determine whether to allocate resources for LTE PC5 communication based on the determination. If the terminal is not authorized by the AMF for cross-RAT PC5 scheduling, the base station may not allocate resources for LTE PC5 communication to the terminal. The terminal may perform LTE PC5 communication in an out-of-coverage mode. If the terminal is authorized by the AMF for cross-RAT PC5 scheduling, the base station may allocate resources for LTE PC5 communication to the terminal. The terminal may perform LTE PC5 communication in an in-coverage mode.

[0252] Additionally, in some embodiments, the base station may determine whether a terminal is authorized to perform cross-RAT PC5 scheduling based on the information obtained from the MME. The base station may determine whether to allocate resources for NR PC5 communication to the terminal based on the determination. If the terminal is not authorized by the MME to perform cross-RAT PC5 scheduling, the base station may not allocate resources for NR PC5 communication to the terminal. The terminal may perform NR PC5 communication in an out-of-coverage mode. If the terminal is authorized by the MME to perform cross-RAT PC5 scheduling, the base station may allocate resources for LTE-NR communication to the terminal. The terminal may perform NR PC5 communication in an in-coverage mode.

[0253] The method according to the embodiments described in the claims or the specification of the present disclosure may be implemented by software, hardware, or a combination of hardware and software.

[0254] As for software, a computer-readable storage medium storing one or more programs (software modules) may be provided. The one or more programs stored in the computer-readable storage medium may be configured to be executed by one or more processors of the electronic device. The one or more programs may include instructions for controlling the electronic device to execute the method according to the embodiments described in the claims or the specification of the present disclosure.

[0255] Such a program (software module, software) may be stored in a random access memory, a non-volatile memory, including flash memory, read-only memory (ROM), electrically erasable programmable ROM (EEPROM), magnetic disk storage device, compact disc (CD)-ROM, digital versatile disc (DVD), or other optical storage device, and magnetic cassette. Alternatively, it may be stored in a memory that combines a part or all of those recording media. Additionally, multiple memories may be included.

[0256] Additionally, the program may be stored in an attachable storage device that can be accessed via a communication network such as the Internet, an intranet, a local area network (LAN), a wide area network (WLAN), or a storage area network (SAN), or a communication network obtained by combining these networks. Such a storage device may be accessed through an external port by the device that executes the embodiments of the present disclosure. Additionally, a separate storage device on the communication network may access the device that executes the embodiments of the present disclosure.

[0257] In a specific embodiment of the present disclosure, the elements included in the present disclosure are expressed in singular or plural forms. However, for the convenience of illustration, the singular or plural expression is appropriately selected according to the proposed situation. The present disclosure is not limited to a single element or multiple elements. Elements expressed in plural forms may be configured as a single element, and elements expressed in singular forms may be configured as multiple elements.

[0258] At the same time, although specific embodiments have been described in the description of the present disclosure, it should be noted that various changes can be made therein without departing from the scope of the present disclosure. Therefore, the scope of the present disclosure is not limited and defined by the described embodiments, but is defined not only by the scope of the following claims, but also by the scope of their equivalents.

Claims

1. A method performed by a Mobility Management Entity (MME), the method comprising: Receiving an Attach Request message or a Tracking Area Update (TAU) Request message including UE capability information from a User Equipment (UE); Receiving a message including subscription information from a Home Subscriber Server (HSS), wherein the subscription information includes Quality of Service (QoS) parameters, UE-PC5-Aggregate Maximum Bit Rate (AMBR) for Long-Term Evolution (LTE) PC5, and UE-PC5-AMBR for New Radio (NR) PC5; and Sending, via an Initial Context Setup Request message or a Handover Request message, the QoS parameters, UE-PC5-AMBR for LTE PC5, and UE-PC5-AMBR for NR PC5 included in the received subscription information to a base station; wherein the UE capability information indicates the NR PC5 capability of the UE; and wherein the QoS parameters indicate the 5G Quality of Service Indicator (5QI) for Vehicle-to-Everything (V2X).

2. The method according to claim 1, Among them, wherein the subscription information further includes an indication of Vehicle-to-Everything (V2X) service authorization per Packet Data Convergence Protocol (PDCP) Radio Access Technology (RAT); wherein the indication of the V2X service authorized per PDCP RAT is included in the Initial Context Setup Request message or the Handover Request message.

3. The method according to claim 2, the method further comprising: Receiving V2X-related information from an Access and Mobility Management Function (AMF); and wherein the V2X-related information includes information indicating the V2X service authorized per PDCP RAT, UE-PC5AMBR per PDCP RAT, and PDCP Quality of Service (QoS) parameters.

4. A Mobility Management Entity (MME), the MME comprising: At least one transceiver; and At least one processor, wherein the at least one processor is configured to perform the method according to any one of claims 1 to 3.

Images