CN113728675A

CN113728675A - Apparatus and method for processing service policy in wireless communication system

Info

Publication number: CN113728675A
Application number: CN202080027413.2A
Authority: CN
Inventors: 李淏娟; 金成勋
Original assignee: Samsung Electronics Co Ltd
Current assignee: Samsung Electronics Co Ltd
Priority date: 2019-04-02
Filing date: 2020-04-02
Publication date: 2021-11-30
Also published as: KR20200116852A

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 process parameter information and policies for providing services in a wireless communication system, and an operation method of a base station may include: obtaining mapping information regarding quality of service associated with direct communication between a first system and a second system; and performing a handover between the quality of service of the first system and the quality of service of the second system using the information on the mapping.

Description

Apparatus and method for processing service policy in wireless communication system

Technical Field

The present disclosure relates generally to wireless communication systems, and more particularly, to an apparatus and method for processing policy and parameter information for providing services in a wireless communication system.

Background

In order to meet the increasing demand for wireless data services after fourth generation (4G) communication systems have been commercialized, an advanced fifth generation (5G) communication system or pre-5G communication system has been developed in an effort. For this reason, the 5G communication system or pre-5G communication system is referred to as a super 4G network communication system or a Long Term Evolution (LTE) system.

To achieve high data rates, 5G communication systems consider their implementation in the very high frequency (mmWave) band (e.g., 60GHz band). To mitigate path loss of propagation and to extend propagation distance in the very high frequency band, 5G communication systems are discussing beamforming, massive Multiple Input Multiple Output (MIMO), full-dimensional (FD) -MIMO, array antennas, analog beamforming, and massive antenna techniques.

In addition, for network enhancement of the system, the 5G communication system is developing technologies such as evolved small cell, advanced small cell, cloud Radio Access Network (RAN), ultra-dense network, device-to-device (D2D) communication, wireless backhaul, mobile network, cooperative communication, coordinated multipoint (CoMP), and reception interference cancellation. In addition, 5G systems are also under development for hybrid frequency shift keying and quadrature amplitude modulation (FQAM) and Sliding Window Superposition Coding (SWSC) as Advanced Coding Modulation (ACM) schemes, and filter bank multi-carrier (FBMC), non-orthogonal multiple access (NOMA), and Sparse Code Multiple Access (SCMA) as advanced access techniques.

In contrast to existing 4G systems, 5G systems are considering support of various services. For example, the most representative services are enhanced mobile broadband (eMBB), ultra-reliable and low latency communication (URLLC), large-scale machine type communication (mtc), evolved multimedia broadcast/multicast service (eMBMS), and the like. A system providing URLLC service may be referred to as a URLLC system, and a system providing eMBB service may be referred to as an eMBB system. The terms service and system are used interchangeably herein.

Meanwhile, the internet is evolving from a human-centric connection 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 that combines IoT technology with big data processing technology by connecting with 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 recently been studied. The IoT environment may provide an intelligent Internet Technology (IT) service that creates new value in human life by collecting and analyzing data generated from connected objects. Through the fusion and composition of existing IT with various industries, IoT may be applied to fields such as smart homes, smart buildings, smart cities, smart cars or networked cars, smart grids, healthcare, smart appliances, and advanced medical services.

Accordingly, various attempts are being made to apply the 5G communication system to the IoT network. For example, technologies such as sensor network, M2M, and MTC are implemented by schemes such as beamforming, MIMO, and array antennas, which are 5G communication technologies. Applying the cloud Radio Access Network (RAN) as an example of the convergence of big data processing technology as described above can be said to be 5G technology and IoT technology.

Vehicle-to-all (V2X) is a general term referring to all kinds of communication schemes applicable to road vehicles, and can provide various additional services in conjunction with wireless communication technology development in addition to initial security use cases. The in-vehicle environment Wireless Access (WAVE) standard based on Institute of Electrical and Electronics Engineers (IEEE)802.11P and IEEE P1609 is standardized as a V2X service provisioning technology. However, WAVE, which is a Dedicated Short Range Communication (DSRC) technology, has a limitation in that a message transmission distance between vehicles is limited.

To overcome this limitation, the third generation partnership project (3GPP) is working on the cellular-based V2X technical standard. Release 14/release 15 has completed the LTE-based Evolved Packet System (EPS) V2X standard, and release 16 is working on New Radio (NR) -based fifth generation system (5GS) V2X standardization.

Disclosure of Invention

Technical problem

Based on the above discussion, the present disclosure provides an apparatus and method for efficiently processing policy and parameter information for providing a service in a wireless communication system.

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

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

Solution to the problem

According to various embodiments of the present disclosure, a method of operation 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 switching between the quality of service of the first system and the quality of service of the second system using the mapping information.

According to various embodiments of the present disclosure, a method of operating 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 switching between the quality of service of the first system and the quality of service of the second system using the mapping information.

According to various embodiments of the present disclosure, a base station apparatus 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 control to obtain mapping information of quality of service related to direct communication between a first system and a second system, and to switch between the quality of service of the first system and the quality of service of the second system using the mapping information.

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 control to obtain mapping information of quality of service related to direct communication between a first system and a second system, and to switch between the quality of service of the first system and the quality of service of the second system using the mapping information.

Advantageous effects of the invention

Apparatuses and methods according to various embodiments of the present disclosure can efficiently perform direct communication between different systems by using information of quality of service mapping information related to direct communication between a first system and a second system.

Effects that can be obtained from the present disclosure are not limited to the above-mentioned effects, and other effects not mentioned can be clearly understood by those skilled in the art of the present disclosure through the following description.

Drawings

Fig. 1 shows a structure of a first communication system according to an embodiment of the present disclosure.

Fig. 2 shows a structure of a second communication system according to an embodiment of the present disclosure.

Fig. 3 illustrates an interworking structure between communication systems according to an embodiment of the present disclosure.

Fig. 4 illustrates a configuration of a network entity in a wireless communication system according to an embodiment of the present disclosure.

Fig. 5 illustrates a configuration of a terminal in a wireless communication system according to an embodiment of the present disclosure.

Fig. 6 illustrates a flowchart for using mapping information of quality of service in a wireless communication system according to an embodiment of the present disclosure.

Fig. 7 illustrates a flowchart for providing mapping information of quality of service in a wireless communication system according to an embodiment of the present disclosure.

Fig. 8a illustrates 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 disclosure.

Fig. 8b illustrates 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.

Fig. 9a illustrates 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 procedure in a wireless communication system according to an embodiment of the present disclosure.

Fig. 9b illustrates a process for a terminal to obtain service policy/parameter information from a network upon a network request from a second communication system in a wireless communication system according to an embodiment of the present disclosure.

Fig. 9c illustrates a process for a terminal to obtain service policy/parameter information from a network of a second communication system upon a request of the terminal in a wireless communication system according to an embodiment of the present disclosure.

Fig. 10 shows a procedure 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.

Fig. 11 shows a procedure 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.

Fig. 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.

Fig. 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.

Fig. 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.

Fig. 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

The terminology used in the present disclosure is used to describe particular embodiments and is not intended to limit the scope of other embodiments. The singular forms may include the plural unless it is explicitly stated differently. All terms used herein, including technical and scientific terms, may have the same meaning as commonly understood by one of ordinary skill in the art to which this disclosure belongs. A term defined in a general dictionary among terms used in the present disclosure may be interpreted to have the same or similar meaning as the context of the related art, and it should not be interpreted ideally or excessively as a formal meaning unless explicitly defined in the present disclosure. In some cases, even terms defined in the present disclosure should not be construed to exclude embodiments of the present disclosure.

In various embodiments of the present disclosure to be described below, a hardware method is described as an example. However, since various embodiments of the present disclosure include techniques that use both hardware and software, various embodiments of the present disclosure do not preclude software-based approaches.

Hereinafter, the present disclosure relates to an apparatus and method for processing policy and parameter information for providing a service in a wireless communication system. In particular, the present disclosure describes techniques for switching between parameters for direct communication between User Equipments (UEs), e.g., PC5 communication, proximity services (ProSe), sidelink communication, vehicle-to-all (V2X) communication, in a wireless communication system.

Terms used in the following description for identifying an access node, terms representing network entities, terms representing messages, terms representing interfaces between network entities, and terms representing various kinds of identification information are for explanation. Accordingly, the present disclosure is not limited to the terms to be described, and other terms may be used to represent a subject having a technically identical meaning.

To simplify the following description, the present disclosure describes various embodiments using terms and names defined in specifications of an Evolved Packet System (EPS) system and a fifth generation (5G) system as illustrations for explanation. Various embodiments of the present disclosure may be readily modified and applied to other communication systems.

In describing embodiments of the present disclosure in detail, it should be mainly directed to communication standards defined by the third generation partnership project (3GPP), but the main subject matter of the present disclosure may be applied to other communication systems having similar technical backgrounds without slight modification within a scope not significantly departing from the scope of the present disclosure, which will be determined by those skilled in the art of the present disclosure.

In describing the embodiments of the present disclosure in detail, it will be mainly directed to vehicle communication services, but the main subject matter of the present disclosure may be applied to other services provided in an EPS network or a 5G network without being slightly modified within a scope that would be determined by those skilled in the art of the present disclosure, without significantly departing from the scope of the present disclosure.

Fig. 1 shows a structure of a first communication system according to an embodiment of the present disclosure. According to an embodiment, the first communication system shown in fig. 1 may be a mobile communication system based on the Long Term Evolution (LTE) standard.

Referring to fig. 1, the first communication system includes an evolved node b (enb)120, a Mobility Management Entity (MME)125, a serving/packet data gateway (S/P-GW)130, a Home Subscription Server (HSS)135, a V2X Control Function (CF)140, and a V2X Application Server (AS) 145. S/P-GW 130 may be divided into a serving gateway (S-GW) and a packet data gateway (P-GW). The eNB120 may 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 technical equivalents.

User Equipment (UE)110a, 110b, 110c or 110d accesses an external network through eNB120 and S/P-GW 130. It may be necessary to generate a Packet Data Network (PDN) connection for a

UE

110a, 110b, 110c, or 110d to send and receive data through the S/P-GW 130, and one PDN connection may include one or more EPS bearers. The

UE

110a, 110b, 110c, or 110d may be referred to as a "terminal," a "mobile station," a "subscriber station," a "remote terminal," a "wireless terminal," or "user equipment," or other terms with technical equivalents. For the purposes of the following description, the present disclosure describes an embodiment using UE 110a among UEs 110a, 110b, 110c, or 110d, and the other UEs 110b, 110, and 110d may operate similarly.

An Application Function (AF) is a device that exchanges information related to an application with a user at an application level. The V2X AS 145 is a means for providing application level V2X services. The V2X AS 145 may include AF functionality.

The eNB120 is a RAN node and corresponds to a Radio Network Controller (RNC) of a UTRAN system and a Base Station Controller (BSC) of a global system for mobile communications (GSM) enhanced data rates for GSM evolution (EDGE) RAN (geran) system. The eNB120 is connected with the UE 110a through a radio channel and performs a role similar to that of the existing RNC/BSC.

In LTE, each user traffic including a real-time service such as voice over internet protocol (VoIP) provides a service through a shared channel. Therefore, means for collecting and scheduling context information of the UE 110a is required, and the eNB120 may function as a scheduler.

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

The HSS 135 is a device that stores and manages subscription information of UEs including the UE 110 a. The subscription information may be referred to as "UE subscription information" or "terminal subscription information". In addition, the HSS 135 may store subscription information for providing the V2X service. < table 1> is an example of V2X service-related subscription information managed by the HSS 135.

[ Table 1]

The V2X CF 140 is a device that manages service policies and parameter information to provide V2X services. < table 2> and < table 3> show examples of V2X service policy and parameter information managed by the V2X CF 140. The UE 110a may establish a PDN connection with the V2X CF 140 via the eNB120 and the S/P-GW 130 through the procedure shown in fig. 8a, i.e., after completing registration in the network, and obtain V2X service policy and parameter information from the V2X CF 140. Still, V2X service policy and parameter information shown in < table 2> or < table 3> may be preconfigured in UE 110a, and UE 110a may use the preconfigured information. < table 2> is an example of V2X service policies and parameters for direct communication (e.g., ProSe).

[ Table 2]

In describing embodiments of the present disclosure, QoS-related parameters defined in a 5G system may be referred to as a "5G quality of service indicator (5 QI)" or a "PC 55 QI (PQI)", and '5 QI' and 'PQI' may be used interchangeably. < table 3> is an example of V2X service policies and parameters for network communications (e.g., Uu communications).

[ Table 3]

To provide LTE PC5 communication, a quality of service (QoS) model based on ProSe Per Packet Priority (PPPP)/ProSe Per Packet Reliability (PPPR) may be used. QoS parameters for LTE PC5 communication may include PPPP and PPPR. The PPPP may include a value indicating a priority level. For example, PPPP can be expressed as a value ranging from '1' to '8'. If the PPPP is '1', it may be determined that the PPPP has a higher priority than the PPPP of '2'. The PPPR may include a value indicating a reliability level. For example, PPPR may be expressed as a value ranging from '1' to '8'. If the PPPR is "1", it can be determined that higher reliability is required than the PPPR of '2'.

To provide New Radio (NR) PC5 communications, a PQI-based QoS model may be used. The QoS parameter, PQI, for NR PC5 communications may include at least one of a priority level, a packet delay budget, a packet error rate, an averaging window, and a maximum data burst size. In addition, to provide NR PC5 communication, a communication range value may be used together with PQI. The following < table 4> shows an example of PQI. < table 4> is an example of a 5QI value defined in the 3GPP standard.

[ Table 4]

According to an embodiment of the present disclosure, information (hereinafter, 'mapping 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 may be defined. For example, the mapping information may be defined as "QoS-related policies/parameters" of < table 2 >. Specifically, the mapping information may be defined as "mapping of PPPP and 5 QI", "mapping of PPPR and 5 QI" as shown in < table 2 >. The mapping information may be determined according to at least one of the following various schemes.

According to an embodiment, to determine a PPPP mapping that may be used interchangeably with the priority level of a PQI, a PPPP value or value interval may be defined that maps with a priority level value or value interval among PQIs. For example, priority level values '7' and '15' may be mapped to PPPP value '1'. As another example, priority level values '0' to '20' may be mapped to PPPP values '1'.

According to an embodiment, to determine a PPPP map that may be used interchangeably with the packet delay budget of the PQI, a packet delay budget mapped with the PPPP may be defined. A packet delay budget value or value interval may be defined that is either a PQI mapped with the packet delay budget value or a value interval mapped with PPPP. For example, a packet delay budget value mapped with a PPPP value of '1' is defined as '110 ms', and a packet delay budget value '110 ms' derived from PPPP may map a packet delay budget value, which is a PQI, to '110 b ms'. As another example, a packet delay budget value '110 ms' derived from PPPP may be mapped to an interval from '0 ms' to '110 ms' as a packet delay budget value of PQI.

According to an embodiment, to determine a PPPR mapping that may be used interchangeably with the packet error rate of a PQI, a PPPR value or value interval may be defined that maps with the packet error rate or value interval as a PQI. For example, packet error rate values of '10-6' and '10-5' may be mapped to PPPR value of '1'. As another example, packet error rate values from '10-6' to '10-5' may be mapped to PPPR value '1'.

According to an embodiment, PPPP and/or PPPR values mapped with the PQI value may be defined to determine PPPP or PPPR that may be used interchangeably with the PQI value (e.g., a 5QI value corresponding to < table 4 >). For example, a PQI value of '1' may be mapped to a PPPP value of '1' and/or a PPPR value of '5'.

Mapping information between an LTE QoS model (e.g., PPPP/PPPR) and an NR QoS model (e.g., PQI) may be defined as in the various examples described above, and the LTE QoS model and the NR QoS model may be transmitted to at least one of a terminal and a base station through the processes of fig. 8a through 9 c.

Fig. 2 shows a structure of a second communication system according to an embodiment of the present disclosure. According to an embodiment, the second communication system shown in fig. 2 may be a 5G-based mobile communication system.

Referring to fig. 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 technical equivalents.

The

UEs

110a, 110b, 200a, and 200b access external networks through the gNB 210 and the UPF 225. In order for a UE to transmit and receive data through the UPF 225, a PDU session needs to be generated, and one PDU session may include one or more QoS flows. The

UE

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 having equivalent technical meanings. For the purposes of the following description, the present disclosure describes embodiments using UE 110a of UEs 110a, 110b, 200a, and 200b, and the

other UEs

110b, 200a, and 200b may operate similarly.

The gNB 210 is a RAN node and corresponds to an 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 traffic including a real-time service such as VoIP through the internet protocol is served through a shared channel, a means for collecting and scheduling context information of the UE 110a, which is managed by the gNB 210, is required.

The AMF 215 is a device that manages various control functions, and one AMF 215 may be connected to a plurality of base stations. The UPF 225 is a device that provides data bearers and creates or removes PDU sessions under the control of the SMF 220. UDM 235 is a device that stores and manages subscription information for UE 110 a. In addition, UDM 235 may store subscription information for providing V2X services. < table 1> shows an example of V2X service-related subscription information managed by UDM 235.

PCF 240 is a device that controls policies related to the QoS of the user, and Policy and Charging Control (PCC) rules corresponding to the policies are sent and applied to SMF 220 and UPF 225. In addition, PCF 240 may manage service policies and parameter information for providing V2X services. < table 2> and < table 3> show examples of V2X service policy and parameter information managed by PCF 240. V2X service policy and parameter information may be stored in the UDR 230. PCF 240 may obtain V2X service policy and parameter information from UDR 230. UE 110a may obtain V2X service policy and parameter information from PCF 240 via the process shown in fig. 5. Alternatively, the V2X service policy and parameter information shown in < table 2> and < table 3> may be preconfigured in the terminal, and the terminal may use the preconfigured information. The AF 250 is a device that exchanges application-related information with a user at an application level. The V2X AS 145 is a means for providing application level V2X services. The V2X AS 145 may include AF 250 functionality.

Fig. 3 illustrates an interworking structure between communication systems according to an embodiment of the present disclosure. According to an embodiment, the structure shown in fig. 3 may be an interworking structure of an LTE-based mobile communication system and a 5G-based mobile communication system (e.g., NR).

Referring to FIG. 3, for interworking between a first communication system and a second communication system, an SGW 300, UPF + PG-U305, SMF + PGW-C510, V-PCF 315, HSS + UDM 320, and V-V2X CF 325 may be deployed with the first communication system and the second communication system.

Fig. 4 illustrates a configuration of a network entity in a communication system according to an embodiment of the present disclosure. The configuration shown in fig. 4 may be understood as one configuration of eNB120, MME 125, S/P-GW 130, HSS 135, V2X CF 140, gNB 210, AMF 215, SMF 220, UPF 225, UDM 235, UDR 230, PCF 240, NEF 245, and AF 250. 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.

Referring to fig. 4, the network entity includes a communication unit 410, a storage unit 420, and a control unit 430.

The communication unit 410 provides an interface for communicating with other devices in the network. That is, the communication unit 410 converts a bitstream transmitted from the network entity to the other device into a physical signal, and converts a physical signal received from the other device into a bitstream. That is, the communication unit 410 may transmit and receive signals. Thus, the communication unit 410 may 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 a network.

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

If the network entity of fig. 4 is a base station (e.g., eNB120 or gNB 210), the network entity may also include a wireless communication unit. The wireless communication unit performs a function for transmitting and receiving signals through a radio channel. For example, the wireless communication unit performs a conversion function between a baseband signal and a bit string according to a physical layer standard of the system. For example, in data transmission, a wireless communication unit generates complex symbols by encoding and modulating a transmission bit stream. In addition, in data reception, the wireless communication unit recovers the received bit stream by demodulating and decoding the baseband signal.

In addition, the wireless communication unit up-converts a baseband signal into a Radio Frequency (RF) band signal, transmits it via an antenna, and down-converts the RF band signal received via the antenna into a baseband signal. To this end, the wireless communication unit may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a digital-to-analog converter (DAC), an analog-to-digital converter (ADC), and the like. In addition, the wireless communication unit may include a plurality of transmission/reception paths. Further, the wireless communication unit may comprise at least one antenna array having a plurality of antenna elements.

In terms of hardware, the wireless communication unit may include a digital unit and an analog unit, and the analog unit may include a plurality of sub-units according to an operating power and an operating frequency. The digital unit may be implemented with at least one processor, such as a Digital Signal Processor (DSP).

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

The control unit 430 controls the general operation of the network entities. For example, the control unit 430 transmits and receives signals through the communication unit 410. In addition, 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.

Fig. 5 illustrates a configuration of a terminal in a communication system according to an embodiment of the present disclosure. The configuration shown in fig. 5 may be understood as a configuration of the

UE

110a, 110b, 110c, 11d, 200a, or 200 b. 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.

Referring to fig. 5, the terminal includes a communication unit 510, a storage unit 520, and a control unit 530.

The communication unit 510 may perform a function 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 a physical layer standard of the system. For example, in data transmission, the communication unit 510 generates a complex symbol by encoding and modulating a transmission bit string. In addition, in data reception, communication section 510 restores a received bit string by demodulating and decoding a baseband signal. In addition, the communication unit 510 up-converts the baseband signal into an RF band signal, transmits it via an antenna, and down-converts the RF band signal received via the antenna into the baseband signal. For example, the communication unit 510 may include a transmission filter, a reception filter, an amplifier, a mixer, an oscillator, a DAC, an ADC, and the like.

In addition, the communication unit 510 may include a plurality of transmission and reception paths. Further, the communication unit 510 may comprise at least one antenna array having a plurality of antenna elements. In terms of hardware, the communication unit 510 may include digital circuitry and analog circuitry (e.g., RF integrated circuit (RFIC)). Herein, the digital circuit and the analog circuit may be implemented as a single package. In addition, the communication unit 510 may include a plurality of RF chains. Further, the communication unit 510 may perform beamforming.

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". In addition, in the following description, transmission and reception through a radio channel are used as meaning of the above-described processing including the communication unit 510.

The storage unit 520 stores basic programs for operating the terminal, application programs, 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 of the control unit 530.

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. In addition, 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 comprise at least one processor or microprocessor, or may be part of a processor. In addition, a 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.

Fig. 6 illustrates a flowchart for mapping information for using QoS in a wireless communication system according to an embodiment of the present disclosure. Fig. 6 illustrates an operation method of an apparatus using QoS mapping information. For example, an apparatus may be a base station (e.g., eNB120 or gNB 210) or a UE (e.g.,

UE

110a, 110b, 110c, 110d, 200a, or 200 b).

Referring to fig. 6, in step 601, the apparatus obtains QoS mapping information between different systems. The QoS mapping information may include at least one of: information indicating that switching between parameters indicating QoS required for communication in the first system and the second system is allowed, information indicating a correspondence relationship 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 are notified. For example, one of the first system and the second system may be a system based on the LTE standard as shown in fig. 1, and the other may be a system based on the NR standard as shown in fig. 2. The QoS mapping information may be obtained through a unique procedure for providing mapping information or a procedure for other purposes, for example, a procedure for registering in a network, a procedure for accessing a network, or a procedure for updating a Tracking Area (TA).

In step 603, the device performs an operation related to direct communication using the mapping information. For example, the apparatus may use the mapping information to switch the QoS parameters of the first system to the QoS parameters of the second system. The QoS parameters after the handover may be used for various operations related to direct communication. For example, the QoS parameters after handoff may be used for resource allocation, resource requests, service availability determinations, and the like.

As in the embodiment described with reference to fig. 6, the apparatus may obtain QoS mapping information between the first system and the second system. In this regard, the device may transmit capability information notifying that a direct communication related operation based on the QoS mapping information can be performed to the network. That is, since providing the mapping information to the device even if the mapping information is not available causes unnecessary signaling overhead, the device can still inform the network of the necessity of the mapping information by transmitting capability information reporting that the mapping information is available.

As in the embodiment described with reference to fig. 6, the apparatus may switch the QoS parameters of the first system to the QoS parameters of the second system.

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

According to another embodiment, if the apparatus is a UE, the apparatus may switch the QoS parameters of the first system generated by the application to the QoS parameters of the second system. As an example, to perform directional communication in systems other than the system corresponding to the QoS parameter provided by the application, the apparatus may switch the QoS parameter generated by the application. As another example, if a system for providing a service of each application is defined but the QoS parameters provided by the application do not correspond to the defined system, the apparatus may switch the QoS parameters generated by the application.

Fig. 7 is a flowchart of mapping information for providing QoS in a wireless communication system according to an embodiment of the present disclosure. Fig. 7 illustrates an operation method of an apparatus for providing QoS mapping information. For example, the apparatus 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., eNB120 or gNB 210).

Referring to fig. 7, in step 701, an apparatus generates a message including QoS mapping information between different systems. The QoS mapping information may include at least one of: the information notifying that switching between parameters indicating QoS required for communication in the first system and the second system is allowed, the information indicating correspondence between the parameters indicating QoS required for communication in the first system and the second system, and the information indicating a switching rule between the 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 fig. 1, and the other may be a system based on the NR standard as shown in fig. 2. The message including the QoS mapping information may be generated by a request of other devices or may be generated by a determination of a device.

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

According to various embodiments, a method of operation of a base station in a wireless communication system may comprise: obtaining information of a QoS mapping related to direct communication between a first system and a second system; and switching between the QoS of the first system and the QoS of the second system using the mapping information.

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

In some embodiments, the method further comprises: receiving a first message requesting resources for direct communication from a terminal; and transmitting a second message informing a result of the resource allocation, and the second message may be generated based on the QoS parameter and the mapping information related to the direct communication included in the first message.

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

In some embodiments, the capability information may include information indicating the presence or absence of cross-Radio Access Technology (RAT) PC5 control capabilities.

In some embodiments, a method of operation 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 switching between the QoS of the first system and the QoS of the second system using the mapping information.

In some embodiments, the method further comprises: transmitting a first message requesting resources for direct communication to a base station; and receiving a second message informing of a result of the resource allocation, and the first message may include a QoS parameter of the first system or the second system.

In some embodiments, the first message may indicate whether the resource requested based on at least one of a message type, an indication, a destination address value, and a QoS parameter included in the first message is a first system resource or a second system resource.

According to various embodiments, a base station apparatus 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 control to obtain mapping information of QoS related to direct communication between a first system and a second system, and perform switching between the QoS of the first system and the QoS of the second system using the mapping information.

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

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

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

In some embodiments, the capability information may include information indicating the presence or absence of control capabilities across the RAT PC 5.

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 of a QoS map related to direct communication between a first system and a second system, and perform switching between QoS of the first system and QoS of the second system by using the mapping information.

In some embodiments, the at least one processor controls to transmit a first message requesting resources for direct communication to the base station, and receives a second message notifying an allocation result of the resources, and the first message may include a QoS parameter of the first system or the second system.

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.

Fig. 8a illustrates 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 disclosure. The process shown in fig. 8a is a process in which UE 110a registers with the network, and the registration process may be referred to as network attachment. A default EPS bearer is created during network attach, so an always-on IP connection is possible.

According to fig. 8a, in step 801, a UE 110a may transmit an initial attach request message to an eNB 120. The UE 110a may send an attach request message to the eNB120 using a Radio Resource Control (RRC) connection setup complete message.

In step 803, eNB120 may send an initial attach request message to MME 125 for access. The eNB120 may transmit the attach request message using an initial UE message as an S1-MME control message. The initial attach request message may include UE capability information supported by UE 110 a. The UE capability information may include at least one of a V2X capability indication, LTE PC5 capability, and NR PC5 capability. The initial attach request message may be included in an S1 application protocol (S1AP) initial UE message and delivered to the MME 125. The eNB120 may deliver an initial UE message to the MME 125 that includes V2X support capability information (e.g., V2X support, cross RAT PC5 control capability information) for the eNB 120. According to another embodiment, a Tracking Area Update (TAU) message may be used in place of the initial attach request message.

In step 805, MME 125 may send a message (e.g., a UE subscription request message) to HSS 135 requesting subscription information for UE 110 a. In step 807, HSS 135 may respond to MME 125 with a response message (e.g., a UE subscription response message) that includes UE subscription information. The subscription information of the UE 110a may include at least one of the items shown in < table 1 >. According to an embodiment of the present disclosure, the HSS 135 may store V2X service policy and parameter information for direct communication (e.g., ProSe) as shown in < table 2 >. Subscription information responsive 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 < table 2 >.

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

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 grant indication (e.g., a of table 1) and a UE-PC 5-Aggregated Maximum Bit Rate (AMBR) for LTE PC5 (e.g., b of table 1).

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

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

Fig. 8b illustrates 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. Fig. 8b shows a procedure for a terminal to obtain V2X service policy and parameter information. According to the procedure shown in fig. 8b, after the registration at the network is completed through the procedure shown in fig. 8a, the UE 110a may establish a PDN connection with the V2X CF 140 through the eNB120 and the S/P-GW 130 and obtain V2X service policy and parameter information from the V2X CF 140.

Referring to fig. 8b, the HSS 135 may receive V2X-related subscription information and service policy/parameter information from the V2X CF 140 in step 817. 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 received 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 < table 2> and < table 3 >.

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

Fig. 9a to 9c illustrate a procedure for a terminal to obtain service policy/parameter information (e.g., V2X service policy parameters shown in < table 1 >) from a network according to an embodiment of the present disclosure.

Fig. 9a illustrates 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 procedure in a wireless communication system according to an embodiment of the present disclosure. Fig. 9a shows the signaling between UE 110a, gNB 210, AMF 215, PCF 240, UDM 235 and UDR 230. The gNB 210 may be referred to herein as An 'access network (An)' or 'RAN'.

Referring to fig. 9a, UDM 235 may send subscription information for UE 110a to PCF 240 in step 901. For example, if subscription information of UE 110a stored in UDM 235 is updated, UDM 235 may provide the updated subscription information. In step 903, UDR 230 may send policy related information (e.g., V2X service parameters) to PCF 240. For example, if policy related information stored in the UDR 230 is updated, the UDR 230 may provide the updated policy related information. In fig. 9a, steps 901 and 903 are shown to be 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 a different time. That is, steps 901 and 903 may be performed independently of the registration procedure of UE 110 a.

In step 905, 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, which receives the registration request message from the UE 110a via the gNB 210, can request UE subscription information of the UE 110a from the UDM 235 by signaling with the UDM 235, and obtain the subscription information from the UDM 235. In step 911, AMF 215 may request policy information associated with UE 110a from PCF 240 and obtain the policy information by signaling with PCF 240.

In step 905, UE 110a may include UE capability information and/or UE policy container (e.g., V2X policy) information supported by UE 110a in the registration request message and thus send the capability information and/or UE policy container information to 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 UE 110a supports the V2X service, information indicating that the UE 110a supports the V2X service may be provided to the AMF 215 by being included in UE capability information (e.g., a V2X capability indication). In addition, 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.

The registration request message transmitted in step 907 may be delivered to the AMF 215 by being included in a Next Generation Application Protocol (NGAP) initial UE message transmitted by the gNB 210 to the AMF 215. The gNB 210 may include the gNB 210 support capability information, e.g., V2X support and cross-RAT PC5 control, in the initial UE message.

In step 909, AMF 215 may request subscription information for UE 105a from UDM 235, and UDM 235 may send a message to UDR 230 requesting the subscription information. The message for requesting subscription information of the UE 110a may include identification information indicating the UE 110a (e.g., a subscriber permanent identifier (SUPI), a 5G Globally Unique Temporary Identifier (GUTI), an International Mobile Subscriber Identity (IMSI), etc. of the UE 110 a). UDR 230 may reply to UDM 235 with a DM query response message that includes subscription information for UE 110 a. UDM 235 receiving the UE subscription information may reply to AMF 215 with a UE subscription response message. The UE subscription response message may include at least one of UE subscription information of the V2X service shown in < table 1 >: (e.g., V2X service authorization information for UE 110a, V2X capability for UE 110a, PC5 LTE capability for UE 110a, PC5 NR capability for UE 110a, cross-RAT PC5 control authorization information for UE 110a, etc.).

According to an embodiment, if the AMF 215 determines that the UE 110a supports the V2X service based on the UE capability information received from the UE 110a, the AMF 215 may select the PCF 240 supporting the V2X service. In step 911, the AMF 215 may request policy information associated with the UE 110a from the selected PCF 240. The message sent in step 911 may include UE policy container (e.g., V2X policy) information received by the AMF 215 from the UE 110 a.

PCF 240 may use one of various methods to obtain the V2X service parameters to be applied to UE 110a from UDR 230. For example, in step 903, if V2X service parameter updates are needed, UDR 230 may provide V2X service parameters to PCF 240. As another example, PCF 240 may request and obtain V2X service parameters from UDR 230 in step 911. According to an embodiment, the V2X service parameters provided by UDR 230 to PCF 240 may include V2X service policies and parameter information as shown in < table 2> and < table 3 >.

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

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

According to an embodiment, PCF 240 may include policy/parameter information related to LTE PC5 among V2X service policies and parameters for direct communication (e.g., ProSe) of < table 2> into one policy container. In addition, the PCF 240 may include policy/parameter information related to the NR PC5 among V2X service policies and parameters for direct communication (e.g., ProSe) < table 2> into one policy container. In addition, PCF 240 may include V2X service policy and parameter information for network communications (e.g., Uu communications) of < table 3> into a policy container. PCF 240 may specify a policy part ID indicating V2X service policy and parameter information to the V2X policy and include it in a policy container. The PCF 240 may inform that the corresponding policy information is a policy for V2X through the policy part ID, and that V2X service policy and parameter information are included.

In

steps

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

According to an embodiment, if the UE capabilities include a V2X capability indication and NR PC5 capabilities, and the gbb capabilities include V2X support, the registration accept message sent in step 913 may include at least one of: V2X service authorization indication (e.g., < a of table 1 >), UE-PC5-AMBR for NR PC5 (e.g., < c of table 1 >), PLMN list for UE 110a to communicate using PC5 (e.g., < d of table 1 >), cross-RAT PC5 control authorization (e.g., < e of table 1 >), and policy container including policy/parameter information related to NR PC5 among V2X service policies and parameters for direct communication (e.g., ProSe) < table 2 >.

According to an embodiment, if the UE capabilities include a V2X capability indication, LTE PC5 capabilities, and NR PC5 capabilities, and the gbb capabilities include V2X support and cross-RAT PC5 control, the registration acceptance sent in step 913 may include at least one of: a V2X service authorization indication (e.g., < a of table 1 >), UE-PC5-AMBR for LTE PC5 (e.g., < b of table 1 >), UE-PC5-AMBR for NR PC5 (e.g., < c of table 1 >), PLMN list for UE 110a to communicate using PC5 (e.g., < d of table 1 >), cross RAT PC5 control authorization (e.g., < e of table 1 >), policy container including policy/parameter information related to LTE PC5 among V2X service policies and parameters for direct communication (e.g., ProSe) of < table 2>, and policy container including policy/parameter information related to NR PC5 among V2X service policies and parameters for direct communication (e.g., ProSe) of < table 2 >.

Alternatively, in step 917 and step 919, the AMF 215 may deliver the parameter information for the V2X service received from the PCF 240 to the UE 110a through a separate procedure. The parameter information for providing the V2X service included in the registration accept message transmitted in

steps

913 and 915 or the UE policy delivery message transmitted in steps 917 and 919 may include at least one of the service policies/parameter information described in the present disclosure. At this time, in step 917 and step 919, parameter information for the V2X service included in an NGAP downlink non-access stratum (NAS) transport message and an NAS message for the AMF 215 to provide policy information to the terminal may be determined in a similar manner to step 913 and step 915. In step 917, AMF 215 may deliver an NGAP UE context modification request message to gNB 210. The NGAP UE context modification request message is a message for changing context information of the terminal configured in the gNB 210, and the gNB 210 stores and applies parameter information for the V2X service received through the NGAP UE context modification request message in the context of the terminal. In response thereto, the gNB 210 may transmit a UE context modification response message to the AMF 215, and thus notify the terminal that the context is changed and applied according to the received information.

Fig. 9b illustrates a process for a terminal to obtain service policy/parameter information from a network at a network request of a second communication system in a wireless communication system according to an embodiment of the present disclosure. Fig. 9b is an example of another process for UE 110a to obtain service policy/parameter information (e.g., V2X service policy parameters shown in < table 1 >). According to the embodiment of fig. 9b, UE 110a may use a UE configuration update procedure to obtain UE policy related information.

Referring to fig. 9b, in step 923 PCF 240 may determine to update the UE policy. As in step 903 of fig. 9a described above, PCF 240 may receive and store updated service policy/parameter information for the terminal from UDR 230 (e.g., V2X service policy parameters shown in < table 1 >). At this time, PCF 240 may determine whether an update of UE policies is required during an initial registration procedure (e.g., the procedure of fig. 9 a) of UE 110a, or whether an update of UE policies is required by the triggered network, i.e., UE policies are required after the initial registration. For example, during the initial registration procedure, PCF 240 may determine whether a UE policy update is needed based on UE policy container (e.g., V2X policy) information received from AMF 215 and information associated with access selection and PDU selection for the terminal (e.g., may be included in an Npcf _ UEPolicyControl _ Create request). Alternatively, if an event occurs, such as changing the location of UE 110a or changing subscription information of UE 110a, e.g., a slicing service (subscribed single network slice selection assistance information (S-NSSAI)) to which UE 110a subscribes, PCF 240 may determine whether a change to the UE policy is required. In addition, PCF 240 may determine to send the service policy/parameter information received from UDR 230 (e.g., V2X service policy parameters shown in < table 1 >) to UE 110a, as described in the section related to step 911 of fig. 9 a.

In step 925, PCF 240 may send service policy/parameter information (e.g., V2X service policy parameters shown in < table 1 >) to AMF 215. At this time, if the V2X service policy parameters shown in < table 1> are transmitted as service policy/parameter information, the service policy/parameter information may include at least a part of the V2X service parameters shown in < table 1 >. According to an embodiment, the service policy/parameter information (e.g., the V2X service policy parameter shown in < table 1 >) may be sent to the AMF 215 by being included in a Namf _ Communication _ N1N2MessageTransfer message. The Namf _ Communication _ N1N2MessageTransfer message may include SUPI, a UE policy container, and the like.

In step 927, if UE 110a is registered in the network and is in a served state, AMF 215 may determine to deliver the UE policy received from PCF 240 to UE 110 a. If UE 110a is registered in either of the 3GPP access and the non-3 GPP access, AMF 215 may deliver the UE policy to UE 110a via the access connected through the registered UE 110 a. If UE 110a is registered in both 3GPP and non-3 GPP accesses and is connectable, AMF 215 may select a particular access according to AMF 215 local policies and deliver the UE policies to UE 110 a. If the UE 110a is not registered in or connectable to the 3GPP access or the non-3 GPP access, the AMF 215 may notify the PCF 240 of the failure of the UE policy transmission through a specific message (e.g., Namf _ Communication _ N1N2transfer failure notification) in step 935. If the AMF 215 determines to deliver the UE policy to the UE 110a through the 3GPP access, if 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 procedure through a network triggered service request. The UE 110a receiving the paging request message may perform a paging procedure.

In

steps

929 and 931, the AMF 215 may deliver the UE policy to the UE 110 a. In this case, if the UE policy includes V2X service, the UE policy may include at least one of the V2X service policy parameters shown in < table 1 >. 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 the policy of the delivery parameters to the UE. To do so, the AMF 215 may include the NAS message in an NGAP downlink NAS transmission or an NGAP UE context modification request message sent to the gNB 210. The parameter information for the V2X service provided by the AMF 215 in

steps

929 and 931 can be determined in a similar manner to

steps

913 and 915. If AMF 215 delivers an NGAP UE context modification request message to gNB 210, gNB 210 may store and apply parameter information for V2X service received through the NGAP UE context modification request message in the context of the terminal. The gNB 210 may transmit a UE context modification response message to the AMF 215 in response thereto, and thus inform the terminal that the context is changed and applied according to the received information.

In step 933, the UE 110a receiving the information of the UE policy may store the obtained information and transmit a reply message notifying that the corresponding information is received, to the AMF 215. In step 935, the AMF 215 may notify the PCF 240 that service policy/parameter information (e.g., V2X service policy parameters shown in < table 1 >) is sent to the UE 110 a. In this case, the message transmitted in step 935 may be a Namf _ N1MessageNotify message. In addition, PCF 240 may maintain the UE policies and notify UDR 230 of the updated UE policies.

Fig. 9c illustrates a process for a terminal to obtain service policy/parameter information from a network of a second communication system upon a UE request in a wireless communication system according to an embodiment of the present disclosure. Fig. 9c is an example of yet another procedure for UE 110a to obtain service policy/parameter information (e.g., V2X service policy parameters shown in < table 1 >). According to the embodiment of fig. 9c, the UE 110a may obtain the UE policy by triggering UE policy acquisition.

Referring to fig. 9c, the UE 110a may transmit a message requesting UE policy to the AMF 215 in step 937. In this case, the message requesting the UE policy may be a UE policy provisioning request message and may include a UE policy container (e.g., V2X policy).

In step 939, the AMF 215 may send a message to the PCF 240 requesting UE policy information. The message requesting UE policy information may be an Npcf _ UEPolicyControl _ Update request and may include a UE policy container (e.g., V2X policy) received from the terminal.

In step 941, PCF 240, having received the message requesting UE policy information, may determine whether a UE policy update is necessary.

Subsequent steps

941, 943, 945, 947, 949, 951 and 953 may be performed similar to the operations described with reference to fig. 9 b. For example, PCF 240 may send UE policy information to AMF 215 in step 943, and AMF 215 may determine to deliver UE policy to UE 110a and deliver it in

steps

945, 947, and 949. In step 951, in response to the UE policy, UE 110a may send a response message to AMF 215, and in step 953 AMF 215 may send a message to PCF 240 indicating whether the UE policy transmission was successful.

The procedures for obtaining service parameters/policies described with reference to fig. 9a, 9b, and 9c may be equally applied to other terminals (e.g., UE 110b, UE 110c, UE 110d, UE 200a, and UE 200 b).

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

In step 1003, the UE 110a may determine to transmit data using the LTE PC 5. In step 1005, UE 110a may transmit a Sidelink (SL) resource request message to base station 210 requesting LTE PC5 resources. The SL resource request message may include at least one of: the PPPP (and/or PPPR) requested by the data to be transmitted by UE 110a, the destination address (e.g., destination layer 2 ID) of the data to be transmitted by UE 110a, and the PQI required for the data to be transmitted by UE 110a and the QoS Flow Identifier (QFI) indicating the PQI.

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

In step 1007, the base station 210 may transmit a SL resource response message including radio resource information allocated to the UE 110 a. Herein, the radio resource may include at least one of a resource exclusively allocated to the UE 110a or a resource competing for use with other UEs. In step 1009, UE 110a may transmit data. The UE 110a may transmit data by using at least a portion of the radio resources allocated by the base station 210.

In the embodiment described with reference to fig. 10, UE 110a determines to use LTE PC 5. According to another embodiment, NR PC5 may be used instead of LTE PC 5. In this case, each step of fig. 10 includes the following operations.

In step 1003, the UE 110a may determine to transmit data using the NR PC 5. Next, in step 1005, UE 110a may transmit a SL resource request message for requesting NR PC5 resources to base station 210. The SL resource request message may include at least one of: the PPPP (and/or PPPR) requested by the data to be transmitted by UE 110a, the destination address (e.g., destination layer 2 ID) of the data to be transmitted by UE 110a, and the PQI required for the data to be transmitted by UE 110a and the QFI indicating the PQI.

In step 1007, the base station 210 may transmit an SL resource response message to the UE 110 a. The SL resource response message may include information of radio resources allocated to UE 110 a. Herein, the radio resource may include at least one of a resource exclusively allocated to the UE 110a or a resource competing for use with other UEs. In step 1009, UE 110a may transmit data. The UE 110a may transmit data by using at least a portion of the radio resources allocated by the base station 210.

In the embodiment described with reference to fig. 10, 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 resource or the NR PC5 resource. Herein, the LTE PC5 resource request and the NR PC5 resource request may be distinguished according to one of various methods.

According to an embodiment, LTE PC5 resource requests and NR PC5 resource requests may be distinguished by being performed by different messages. For example, if UE 110a requests PC5 resources from base station 210, UE 110a may use different SL resource request messages to distinguish between LTE PC5 resource requests and NR PC5 resource requests. 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 the SL resource request message.

According to an embodiment, LTE PC5 resource requests and NR PC5 resource requests may be distinguished by an indication in the message. For example, the same SL resource request message is used, but UE 110a may include an indication in the SL resource request message indicating one of LTE PC5 or NR PC 5. 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.

According to an embodiment, LTE PC5 and NR PC5 resource requests may be distinguished using the value of the destination address (e.g., destination layer 2 ID) included in the message. For example, a value indicating a 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 between the destination layer 2 ID indicating LTE PC5 and the destination layer 2 ID indicating NR PC 5. 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.

According to an embodiment, LTE PC5 and NR PC5 resource requests may be distinguished based on the type of required parameters included in the message. For example, the message requesting LTE PC5 resources may include parameters for LTE-based direct communication, and the message requesting 5G PC5 resources may include parameters for 5G-based direct communication. Specifically, if LTE PC5 resources are requested, UE 110a may include the PPPP (and/or PPPR) needed for data only in the SL resource request message, while excluding the 5QI needed for data. Similarly, in addition, if NR PC5 resources are requested, UE 110a may include 5QI needed for data only, while excluding PPPP (and/or PPPR) needed for data, in the SL resource request message. 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 the QoS-related parameter included in the SL resource request message.

Referring to fig. 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 V2X service subscription information and policy and parameter information as in step 809 of fig. 8 a.

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

Upon request by UE 110a, base station 120 determines radio resources to allocate to UE 110 a. To determine the radio resources to be allocated to UE 110a, base station 120 may use QoS mapping information (e.g., 'mapping of PPPP and 5 QI' and/or 'mapping of PPPR and 5 QI'). For example, if a PQI is received from the UE 110a in step 1105, the base station 120 may convert the PQI received from the UE 110a into a PPPP (and/or PPPR) value using the QoS mapping information and determine radio resources to be allocated to the UE 110 a. Alternatively, if PPPP (and/or PPPR) is received from the UE 110a in step 1105, the base station 210 may convert the PPPP (and/or PPPR) received from the UE 110a into a PQI value using the QoS mapping information and determine radio resources to be allocated to the UE 110 a. Herein, the QoS mapping information may be obtained from the MME 125 according to step 809 of fig. 8 a. Alternatively, the QoS mapping information may be preconfigured in the base station 120, and the base station 120 may use the preconfigured information.

In step 1107, the base station 120 may transmit a SL resource response message. The SL resource response message may include radio resource information allocated to UE 110 a. Herein, the radio resource may include at least one of a resource exclusively allocated to the UE 110a or a resource competing for use with other UEs. In step 1109, UE 110a may transmit data. UE 110a may transmit data by using at least a portion of the radio resources allocated by base station 120.

In the embodiment described with reference to fig. 11, UE 110a determines to use LTE PC 5. According to another embodiment, NR PC5 may be used instead of LTE PC 5. In this case, each step of fig. 10 includes the following operations.

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

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

In step 1107, the base station 120 may transmit a SL resource response message. The SL resource response message may include information of radio resources allocated to UE 110 a. Herein, the radio resource may include at least one of a resource exclusively allocated to the UE 110a or a resource competing for use with other UEs. In step 1109, UE 110a may transmit data. The UE 110a may transmit data by using at least a portion of the radio resources allocated from the base station 210.

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

According to an embodiment, LTE PC5 resource requests and NR PC5 resource requests 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 between LTE PC5 resource requests and NR PC5 resource requests. Accordingly, the base station 120 can 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.

According to an embodiment, LTE PC5 resource requests and NR PC5 resource requests may be distinguished by an indication in the message. For example, the same SL resource request message is used, but UE 110a may include an indication in the SL resource request message indicating one of LTE PC5 or NR PC 5. Accordingly, the base station 120 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.

According to an embodiment, LTE PC5 and NR PC5 resource requests may be distinguished based on the type of required parameters included in the message. For example, the message requesting LTE PC5 resources may include parameters for LTE-based direct communication, and the message requesting 5G PC5 resources may include parameters for 5G-based direct communication. Specifically, if LTE PC5 resources are requested, UE 110a may include only PPPP (and/or PPPR) needed for data in the SL resource request message, while excluding 5QI needed for data. Similarly, if NR PC5 resources are requested, UE 110a may include only the 5QI needed for data in the SL resource request message, while excluding the PPPP (and/or PPPR) needed 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 the QoS-related parameter included in the SL resource request message.

Fig. 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. Fig. 12 shows signaling between the gNB 210 and the AMF 215. The gNB 210 may be referred to as an NG-RAN.

Referring to fig. 12, in step 1201, the gNB 210 transmits an NG setting request message to the AMF 215. The NG setting request message may include V2X capability information. In step 1203, AMF 215 sends an NG setup response message to gNB 210. That is, the gNB 210 and the AMF 215 may exchange information used between the two and perform an N2 setup procedure to configure connection information. The N2 setup procedure may be performed regardless of the UE.

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

Fig. 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. Fig. 13 shows signaling between eNB120 and MME 125. The eNB120 may be referred to as an E-UTRAN.

Referring to fig. 13, in step 1301, eNB120 transmits an S1 setup request message to MME 125. The S1 setup request message may include V2X capability information. In step 1303, the MME 125 transmits an S1 setup response message to the eNB 120. The eNB120 and the MME 125 may exchange information used between the two and perform S1 setup procedures to configure the connection information. The S1 setup procedure may be performed regardless of the UE.

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

A UE according to various embodiments of the present disclosure may obtain function information supported by a network. Hereinafter, a procedure for the UE to identify functions supported by the network (e.g., cross-RAT PC5 control functions) through signaling from the base station is described through fig. 14a to 14 b.

Fig. 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. Fig. 14 shows signaling between the terminal 110a and the base station. In fig. 14a, the base station exemplifies an eNB 120. The eNB120 may be referred to as an E-UTRAN.

Referring to fig. 14a, a terminal 110a accessing the EPC network may receive system information from a base station (eNB)120 in step 1401. The system information in step 1401 may include functionality supported by base station 120. The functionality supported by the base station 120 may include controlling capability information across the RAT PC 5. 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.

The terminal 110a, which has received the system information of step 1401 from the base station 120, may perform a PC5 operation based on at least one of functionality information supported by the base station 120 and 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 may 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 may 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 may transmit an LTE PC5 resource request message and may not transmit an NR PC5 resource request message to the base station 120.

If the base station 120 does not support the cross-RAT PC5 control function, the base station 120 may include an indication in the message of step 1401 (i.e. the System Information (SI) message) indicating that the cross-RAT PC5 control function is not supported. Alternatively, the base station 120 may not include the cross-RAT PC5 control function related information in the message of step 1401. The terminal 110a may recognize that the cross-RAT PC5 control function related information is not included in the message of step 1401. The terminal 110a may determine, based on the identification, that the base station 120 does not support the cross-RAT PC5 control function.

According to another embodiment, the message of step 811 (e.g., RRC connection reconfiguration/initial attach response) may be used instead of the SI message of step 1401.

Fig. 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. Fig. 14 shows signaling between the terminal 110a and the base station. In fig. 14b, the base station exemplifies a gNB 210. The gNB 210 may be referred to as an NG-RAN.

Referring to fig. 14b, the terminal 110a accessing the 5G network may receive system information from the base station (gNB)210 in step 1451. The system information in step 1451 may include functionality supported by the base station 210. The functionality supported by the base station 210 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.

The terminal 110a, which has received the system information of step 1451 from the base station 210, may perform a PC5 operation based on at least one of functionality information supported by the base station 210 and 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 may 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 may 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 may transmit an NR PC5 resource request message and may not transmit an LTE PC5 resource request message to the base station 210.

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

According to another embodiment, the message (registration accept) message of step 915 may be used instead of the SI as the message of step 1451. The message (registration accept) of step 915 may be included in the RRC connection reconfiguration message and transmitted.

A terminal according to various embodiments of the present disclosure may obtain function information supported by a network. The terminal 110a may register in a 5G system (e.g., 5GC) based on the procedure shown in fig. 9 a.

In

steps

905 and 907 of fig. 9, the terminal 110a may transmit a registration request message to the AMF 215 via the base station 210. The registration request message may include 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 may be PC5 capability for V2X (e.g., LTE PC5 only, NR PC5 only, both LTE PC5 and NR PC 5). In addition, the capability information of the terminal may be the cross-RAT PC5 capability, for example.

In step 909, the AMF 215 having received 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 a "V2X service grant" indication, UE-PC5-AMBR per PC5 RAT, and cross RAT PC5 control grant.

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 a "V2X service authorization" indication, UE-PC5-AMBR per PC5 RAT, and cross RAT PC5 control authorization.

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 supports 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 110 a. The registration accept message may include information indicating that cross-RAT PC5 scheduling is possible (e.g., a "cross-RAT PC5 control is authorized" indication). In

steps

913 and 915, the AMF 215 may transmit a registration accept message to the base station 210 and the terminal 110 a. The AMF 215 may send a registration accept message to the base station 210 that includes information indicating that scheduling across the RAT PC5 is possible. The AMF 215 may send a registration accept message including information indicating that scheduling across the RAT PC5 is possible to the terminal 110a via the base station 210.

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

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

In some embodiments, a terminal 110a authorized by the AMF 215 for cross-RAT PC5 scheduling may operate in coverage in NR PC5 and LTE PC 5. Accordingly, 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.

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

Additionally, in some embodiments, terminals that are not authorized for cross-RAT PC5 scheduling from the AMF 215 may operate in coverage in NR PC5 and out of coverage in LTE PC 5.

Additionally, in some embodiments, terminals that are not authorized to schedule across RAT PCs 5 from the AMF 215 may not perform the process of fig. 10 in LTE PC5 communications.

Additionally, in some embodiments, a terminal authorized for cross-RAT PC5 scheduling from the AMF 215 may perform the process of fig. 10. In step 1003, the terminal 110a may determine to transmit resources to the LTE PC 5. In step 1005, the terminal 110a may transmit 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 scheduling across RAT PCs 5 is possible), the base station 210 may determine that terminal 110a is a terminal that is not authorized to make LTE PC5 resource requests. Therefore, in step 1007, the base station 210 may not allocate the LTE PC5 resource to the terminal 110 a. In step 1009, the terminal 110a, which is not allocated LTE PC5 resources from the base station 210, may transmit data to the LTE PC5 in the out-of-coverage mode.

A terminal according to various embodiments of the present disclosure may acquire function information supported by a network. The terminal 110a may register in the EPC system by performing the procedure shown in fig. 8 a.

In steps 801 and 803 of fig. 8, the terminal 110a may transmit an initial attach request message to the MME 125 via the base station 120 (e.g., eNB). The initial attach 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., LTE PC5 only, NR PC5 only, both LTE PC5 and NR PC5), cross-RAT PC5 capabilities, and so on.

In step 805, the MME 125 having received the initial attach 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 a "V2X service authorization" indication, UE-PC5-AMBR per PC5 RAT, and cross RAT PC5 control authorization.

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

The base station 120 that received 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.

The terminal 110a that received the initial attach response 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 attach response message.

Additionally, in some embodiments, terminals authorized by the MME for cross-RAT PC5 scheduling may operate in coverage in NR PC5 and LTE PC 5. Accordingly, in step 1401 of fig. 14, the NR PC5 resource pool information received from the base station 120 may be stored and used for NR PC5 communication.

Additionally, in some embodiments, a terminal authorized by the MME for cross-RAT PC5 scheduling may perform the process of fig. 11. In step 1103, the terminal 110a may determine to send resources to the NR PC 5. In step 1105, the terminal 110a may transmit an NR PC5 resource request message to the base station 120. Based on the information received from MME 125 in step 1101 (e.g., information indicating that scheduling across RAT PCs 5 is possible), base station 120 may determine that terminal 110a is a terminal authorized to make NR PC5 resource requests. Accordingly, in step 1107, the base station 120 may allocate NR PC5 resources to the terminal 110 a. In step 1109, the terminal 110a, which is allocated NR PC5 resources from the base station 120, may transmit data to the NR PC 5.

Additionally, in some embodiments, terminals that are not authorized by the MME for cross-RAT PC5 scheduling may operate in-coverage in LTE PC5 and out-of-coverage in NR PC 5.

Additionally, in some embodiments, terminals not authorized by the MME for cross-RAT PC5 scheduling may not perform the process of fig. 11 in NR PC5 communications.

Additionally, in some embodiments, terminals that are not authorized by the MME 125 for cross-RAT PC5 scheduling may perform the process of fig. 11. In step 1103, the terminal 110a may determine to send resources to the NR PC 5. In step 1105, the terminal 110a may transmit 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 scheduling across RAT PCs 5 is possible), the base station 120 may determine that terminal 110a is a terminal that is not authorized to make NR PC5 resource requests. Therefore, in step 1107, the base station 120 may not allocate NR PC5 resources to the terminal 110 a. In step 1109, the terminal 110a, which is not allocated NR PC5 resources from the base station 120, may transmit data to the NR PC5 in an out-of-coverage mode.

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

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 capability for V2X (LTE PC5 only, NR PC5 only, both LTE PC5 and NR PC5), cross-RAT PC5 capability) received from the terminal in step 907 of fig. 9 a. The AMF 215 may store the UE capability information as a UE context. The AMF 215 may store the UE subscription information or policy information received from the UDM 235 or PCF 240 in steps 909 to 911 of fig. 9 a. The AMF 215 may store UE subscription information or policy information as a UE context. The UE subscription information or policy information may include at least one or more of the following: PC5 authorization information (whether the UE is authorized to perform V2X communications over a PC5 reference point as a vehicular UE, a pedestrian UE, or both, 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 (PLMN list where the UE is authorized to perform V2X communications over a PC5 reference point). For each PLMN in the list, RAT(s) and PC5 QoS parameters that the UE is authorized to perform V2X communications over the PC5 reference point are included.

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

For example, 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 a terminal authorized for cross-RAT PC5 control. Based on the UE context, the MME 125 may determine to provide the cross-RAT PC5 scheduling functionality for the UE 110 a.

The AMF 215 may determine UE context information to send to the MME 125. For example, the AMF 215 may 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 may 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.

To send the UE context to the MME 125, the AMF 215 may convert the UE context in the 5G format to the UE context in the EPS format. For example, the UE context converted into the EPS format may be referred to as a mapped EPS UE context or a mapped EPS UE context for V2X. The AMF 215 may send the UE context converted into EPS format to the MME 125 over the N26 interface. The UE context converted into the EPS format may be included in a message such as a relocation request, relocation complete notification, and context response and transmitted to the MME 125.

The MME 125 may include information indicating that cross-RAT PC5 scheduling is possible (e.g., a "cross-RAT PC5 control grant" indication) in a message (e.g., an initial context setup request, a 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 may identify that the terminal 110a is authorized to use the cross-RAT PC5 scheduling function based on the information included in the message.

The MME 125 may include information indicating that cross-RAT PC5 scheduling is possible (e.g., a "cross-RAT PC5 control grant" indication) in a message sent to the terminal 110a (e.g., TAU accept, etc.). The terminal 110a receiving the 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 message.

A 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 capability for V2X (LTE PC5 only, NR PC5 only, both LTE PC5 and NR PC5), cross-RAT PC5 capability) received from the terminal in step 803 of fig. 8 a. The MME may store the UE capability information as a UE context. The MME 125 may store the UE subscription information received from the HSS 135 in step 807 of fig. 8 a. The MME 125 may store the UE subscription information as a UE context. The UE subscription information may include at least one or more of the following: PC5 authorization information (whether the UE is authorized to perform V2X communication as a vehicle UE, a pedestrian UE, or both over a PC5 reference point, including for LTE PC5 and for NR PC5), "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, PLMN list (list of PLMNs the UE is authorized to perform V2X communication over a PC5 reference point). For each PLMN in the list, RAT(s) and PC5 QoS parameters that the UE is authorized to perform V2X communications over the PC5 reference point are included.

According to various embodiments of the present disclosure, a terminal 110a registered in the EPC system and connected to the MME 125 may move to a 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 over the N26 interface. The UE context may include UE capability information, UE subscription information, policy information, and the like.

The MME 125 may determine UE context information to send 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.

The MME 125 may send the EPS formatted UE context to the AMF 215 over an N26 interface. The UE context in EPS format may be included in messages such as a forward relocation request, a forward relocation completion notification acknowledgement, and a context response and sent to the AMF 215.

The AMF 215 may store and use the UE context received from the MME 125. For example, the AMF 215 may convert the EPS format UE context received from the MME 125 into a 5G format UE context. The UE context may include information indicating that the terminal 110a may use LTE PC5 functionality and NR PC5 functionality 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 functionality to the UE 110 a.

The AMF 215 may include information indicating that cross-RAT PC5 scheduling is possible (e.g., a "cross-RAT PC5 control grant" 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 110 a. The base station 210 receiving the 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 message.

The AMF 215 may include information indicating that cross-RAT PC5 scheduling is possible (e.g., a "cross-RAT PC5 control grant" indication) in a message sent to the terminal 110a (e.g., registration accept, etc.). The terminal 110a receiving the 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 message.

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

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

In some embodiments, the base station may determine whether the terminal is authorized for cross-RAT PC5 scheduling based on information obtained from the AMF. The base station may determine whether to allocate resources for LTE PC5 communication to the terminal based on the determination. The base station may not allocate resources to the terminal for LTE PC5 communications if the terminal is not authorized by the AMF for cross-RAT PC5 scheduling. 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 to the terminal for LTE PC5 communications. The terminal may perform LTE PC5 communication in an in-coverage mode.

Additionally, in some embodiments, the base station may determine whether the terminal is authorized for cross-RAT PC5 scheduling based on 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 for cross-RAT PC5 scheduling, the base station may not allocate resources to the terminal for NR PC5 communications. The terminal may perform NR PC5 communication in an out-of-coverage mode. The base station may allocate resources to the terminal for LTE NR communication if the terminal is authorized by the MME for cross-RAT PC5 scheduling. The terminal can perform NR PC5 communication in the in-coverage mode.

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

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

Such programs (software modules, software) may be stored in random access memory, non-volatile memory including flash memory, Read Only Memory (ROM), electrically erasable programmable ROM (eeprom), magnetic disk storage, Compact Disk (CD) -ROM, Digital Versatile Disks (DVD) or other optical storage, and magnetic cassettes. Alternatively, it may be stored in a memory that combines a part or all of those recording media. Additionally, multiple memories may be included.

In addition, the program may be stored in an attachable storage device that is accessible 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 storage devices may access devices that perform embodiments of the present disclosure through an external port. In addition, a separate storage device on the communication network may access the device performing the embodiments of the present disclosure.

In certain embodiments of the present disclosure, elements included in the present disclosure are expressed in singular or plural forms. However, the singular or plural expressions are appropriately selected depending on the proposed situation for convenience of explanation, the present disclosure is not limited to a single element or a plurality of elements, elements expressed in the plural form may be configured as a single element, and elements expressed in the singular form may be configured as a plurality of elements.

Meanwhile, although specific embodiments have been described in the description of the present disclosure, it should be noted that various changes may be made therein without departing from the scope of the present disclosure. Accordingly, the scope of the present disclosure is not limited and restricted by the described embodiments, but is defined not only by the scope of the following claims, but also by the scope of equivalents thereof.

Claims

1. A method performed by a User Equipment (UE), the method comprising:

transmitting a message including UE capability information to a Mobility Management Entity (MME),

wherein the UE capability information indicates whether the UE supports a New Radio (NR) PC 5.

2. The method of claim 1, wherein the message comprises an attach request message or a Tracking Area Update (TAU) request message.

3. A method performed by a Mobility Management Entity (MME), the method comprising:

receiving a message including User Equipment (UE) capability information from a UE,

4. The method of claim 3, the method further comprising:

receiving a message including subscription information from a Home Subscription Server (HSS),

wherein the subscription information includes a UE-PC 5-Aggregate Maximum Bit Rate (AMBR) for Long Term Evolution (LTE) PC5 and a UE-PC5-AMBR for NR PC 5.

5. The method of claim 4, wherein the subscription information comprises quality of service (QoS) parameters for the NR PC 5.

6. The method of claim 5, wherein the QoS parameters are delivered to a base station through an initial context setup request message or a handover request message.

7. The method of claim 5, wherein an indication indicating vehicle-to-all (V2X) service authorization per PC5 Radio Access Technology (RAT) and UE-PC5-AMBR per PC5 RAT is sent to a base station based on the subscription information.

8. A method performed by a Home Subscription Server (HSS), the method comprising:

sending a message including subscription information to a Mobility Management Entity (MME),

wherein the subscription information includes a UE-PC 5-Aggregate Maximum Bit Rate (AMBR) for a Long Term Evolution (LTE) PC5 and a UE-PC5-AMBR for a New Radio (NR) PC 5.

9. The method of claim 8, wherein the subscription information comprises quality of service (QoS) parameters for the NR PC 5.

10. A method performed by a Mobility Management Entity (MME), the method comprising:

receiving vehicle-to-all (V2X) related information from an access and mobility management function (AMF); and

transmitting a handover request message to an enodeb (enb) based on the received V2X-related information,

wherein the V2X related information includes information indicating authorized V2X services per PC5 Radio Access Technology (RAT), UE-PC 5-Aggregated Maximum Bit Rate (AMBR) per PC5 RAT, and PC5 quality of service (QoS) parameters.

11. A method performed by a Mobility Management Entity (MME), the method comprising:

sending vehicle-to-all (V2X) related information to an access and mobility management function (AMF),

wherein the V2X-related information is used to deliver a handover request message to a gNodeB (gNB) associated with the AMF, an

The V2X-related information includes information indicating authorized V2X services per PC5 Radio Access Technology (RAT), UE-PC 5-Aggregated Maximum Bit Rate (AMBR) per PC5 RAT, and PC5 quality of service (QoS) parameters.

12. A method performed by an access and mobility management function (AMF), the method comprising:

receiving vehicle-to-all (V2X) related information from a Mobility Management Entity (MME); and

transmits a handover request message to the gNodeB (gNB) based on the received V2X-related information,

13. A method performed by an access and mobility management function (AMF), the method comprising:

sending vehicle-to-all (V2X) related information to a Mobility Management Entity (MME),

wherein the V2X-related information is used to deliver a handover request message to an eNodeB (eNB) associated with the MME, an

14. A User Equipment (UE), the UE comprising:

at least one transceiver; and

at least one processor for executing a program code for the at least one processor,

wherein the at least one processor is configured to perform the method of claim 1 or 2.

15. A communication node, the communication node comprising:

at least one transceiver; and

wherein the at least one processor is configured to perform the method of claims 3-13.