KR20200131645A - Method and apparatus for providing direct communication service in wireless communication system - Google Patents

Abstract

The present disclosure relates to a communication technique for fusing a 5^th generation (5G) communication system with an Internet of things (IoT) technology to support a higher data transmission rate than that of a 4^th generation (4G) system and a system thereof. The present disclosure can be applied to an intelligent service (for example, smart home, smart building, smart city, smart car or connected car, healthcare, digital education, retail business, security and safety related services, etc.) based on a 5G communication technology and an IoT-related technology. According to the present disclosure, disclosed are a method and apparatus for providing a direct communication service. A control signal processing method in a wireless communication system comprises the steps of: receiving a first control signal; processing the received first control signal; and transmitting a second control signal generated based on the processing.

Description

Method and apparatus for providing direct communication service in wireless communication system {METHOD AND APPARATUS FOR PROVIDING DIRECT COMMUNICATION SERVICE IN WIRELESS COMMUNICATION SYSTEM}

The present disclosure relates to a method and apparatus for providing a direct communication service in a wireless communication system.

Efforts are being made to develop an improved 5G communication system or a pre-5G communication system in order to meet the increasing demand for wireless data traffic after the commercialization of 4G communication systems. For this reason, a 5G communication system or a pre-5G communication system is called a Beyond 4G Network communication system or an LTE system and a Post LTE system. The 5G communication system defined by 3GPP is called the New Radio (NR) system.

In order to achieve a high data rate, the 5G communication system is being considered for implementation in the ultra-high frequency (mmWave) band (eg, such as the 60 Giga (60 GHz) band). In order to mitigate the path loss of radio waves in the ultra-high frequency band and increase the transmission distance of radio waves, in 5G communication systems, beamforming, massive MIMO, and Full Dimensional MIMO (FD-MIMO) ), array antenna, analog beam-forming, and large scale antenna techniques were discussed and applied to NR systems.

In addition, in order to improve the network of the system, in 5G communication system, advanced small cell, advanced small cell, cloud radio access network (cloud RAN), ultra-dense network , Device to Device communication (D2D), wireless backhaul, moving network, cooperative communication, CoMP (Coordinated Multi-Points), and interference cancellation And other technologies are being developed.

In addition, in the 5G system, advanced coding modulation (ACM) methods such as Hybrid FSK and QAM Modulation (FQAM) and SWSC (Sliding Window Superposition Coding), advanced access technologies such as Filter Bank Multi Carrier (FBMC), NOMA (non-orthogonal multiple access), and sparse code multiple access (SCMA) have been developed.

On the other hand, the Internet is evolving from a human-centered network in which humans generate and consume information, to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. Internet of Everything (IoE) technology, which combines IoT technology with big data processing technology through connection with cloud servers, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, a sensor network for connection between objects, machine to machine , M2M), and MTC (Machine Type Communication) technologies are being studied. In the IoT environment, intelligent IT (Internet Technology) services that create new value in human life by collecting and analyzing data generated from connected objects can be provided. IoT is the field of smart home, smart building, smart city, smart car or connected car, smart grid, healthcare, smart home appliance, advanced medical service, etc. through the convergence and combination of existing IT (Information Technology) technology and various industries. Can be applied to.

Accordingly, various attempts have been made to apply a 5G communication system to an IoT network. For example, 5G communication such as a sensor network, machine to machine (M2M), and machine type communication (MTC) is being implemented by techniques such as beamforming, MIMO, and array antenna. As the big data processing technology described above, a cloud radio access network (cloud RAN) is applied as an example of the convergence of 5G technology and IoT technology.

V2X (Vehicle to Everything) is a general term that refers to all types of communication methods applicable to road vehicles, and in combination with the development of wireless communication technology, various additional services in addition to the initial safety use cases are becoming possible.

As a V2X service providing technology, WAVE (Wireless Access in Vehicular Environments) standards based on IEEE 802.11p and IEEE P1609 have been standardized. However, WAVE, which is a type of Dedicated Short Range Communication (DSRC) technology, has a limitation in that the distance of communication between the vehicle and the vehicle is limited.

To overcome this limitation, a cellular-based V2X technology standard is in progress in 3GPP. In Release 14/Release 15, the LTE system-based EPS (Evolved Packet System) V2X standard was completed, and in Release 16, the NR system-based 5GS (5th Generation System) V2X standard is in progress.

An object of the present disclosure is to provide a method and apparatus for providing an improved direct communication service in a wireless communication system.

The present invention for solving the above problem is a control signal processing method in a wireless communication system, the method comprising: receiving a first control signal transmitted from a base station; Processing the received first control signal; And transmitting a second control signal generated based on the processing to the base station.

According to an embodiment of the present disclosure, an apparatus and method capable of effectively providing a direct communication service in a wireless communication system can be provided.

1 illustrates a configuration of a vehicle communication system according to an embodiment of the present disclosure.
2A illustrates a control plane protocol stack of a terminal according to an embodiment of the present disclosure.
2B is a diagram illustrating a user plane protocol stack of a terminal according to an embodiment of the present disclosure.
3 shows a configuration of a direct communication link connection according to an embodiment of the present disclosure.
4A illustrates a procedure for establishing a direct communication link connection according to an embodiment of the present disclosure.
4B illustrates a data transmission procedure using a direct communication link according to an embodiment of the present disclosure.
4C illustrates a direct communication link update procedure according to an embodiment of the present disclosure.
5 illustrates a procedure for a terminal to obtain application data related information from a network according to an embodiment of the present disclosure.
6A is a block diagram illustrating a configuration of a network entity according to an embodiment of the present disclosure.
6B is a block diagram illustrating a configuration of a terminal according to an embodiment of the present disclosure.

Hereinafter, the operating principle of the present disclosure will be described in detail with reference to the accompanying drawings. In the following description of the present disclosure, when it is determined that a detailed description of a related known function or configuration may unnecessarily obscure the subject matter of the present disclosure, a detailed description thereof will be omitted. In addition, terms to be described later are terms defined in consideration of functions in the present disclosure and may vary according to the intention or custom of users or operators. Therefore, the definition should be made based on the contents throughout this specification.

For the same reason, some components in the accompanying drawings are exaggerated, omitted, or schematically illustrated. In addition, the size of each component does not fully reflect the actual size. The same reference numerals are assigned to the same or corresponding components in each drawing.

Advantages and features of the present disclosure, and a method of achieving them will be apparent with reference to the embodiments described below in detail together with the accompanying drawings. However, the present disclosure is not limited to the embodiments disclosed below, but may be implemented in a variety of different forms, and only these embodiments make the present disclosure complete, and those skilled in the art to which the present disclosure pertains. It is provided to fully inform the scope of the invention to the person, and the present disclosure is only defined by the scope of the claims. The same reference numerals refer to the same components throughout the specification.

At this time, it will be appreciated that each block of the flowchart diagrams and combinations of the flowchart diagrams may be executed by computer program instructions. Since these computer program instructions can be mounted on the processor of a general purpose computer, special purpose computer or other programmable data processing equipment, the instructions executed by the processor of the computer or other programmable data processing equipment are described in the flowchart block(s). It creates a means to perform functions. These computer program instructions can also be stored in computer-usable or computer-readable memory that can be directed to a computer or other programmable data processing equipment to implement a function in a particular way, so that the computer-usable or computer-readable memory It is also possible to produce an article of manufacture containing instruction means for performing the functions described in the flowchart block(s). Computer program instructions can also be mounted on a computer or other programmable data processing equipment, so that a series of operating steps are performed on a computer or other programmable data processing equipment to create a computer-executable process to create a computer or other programmable data processing equipment. It is also possible for instructions to perform processing equipment to provide steps for executing the functions described in the flowchart block(s).

In addition, each block may represent a module, segment, or part of code that contains one or more executable instructions for executing the specified logical function(s). In addition, it should be noted that in some alternative execution examples, functions mentioned in blocks may occur out of order. For example, two blocks shown in succession may in fact be executed substantially simultaneously, or the blocks may sometimes be executed in reverse order depending on the corresponding function.

In this case, the term'~ unit' used in the present embodiment refers to software or hardware components such as FPGA or ASIC, and'~ unit' performs certain roles. However,'~ part' is not limited to software or hardware. The'~ unit' may be configured to be in an addressable storage medium, or may be configured to reproduce one or more processors. Thus, as an example,'~ unit' refers to components such as software components, object-oriented software components, class components and task components, processes, functions, properties, and procedures. , Subroutines, segments of program code, drivers, firmware, microcode, circuitry, data, database, data structures, tables, arrays, and variables. The components and functions provided in the'~ units' may be combined into a smaller number of elements and'~ units', or may be further divided into additional elements and'~ units'. In addition, components and'~ units' may be implemented to play one or more CPUs in a device or a security multimedia card. Also, in an embodiment, the'~ unit' may include one or more processors.

A term for identifying an access node used in the following description, a term for network entities, a term for messages, a term for an interface between network objects, a term for various identification information And the like are illustrated for convenience of description. Accordingly, the present disclosure is not limited to the terms described later, and other terms referring to objects having an equivalent technical meaning may be used.

For convenience of description below, the present disclosure uses terms and names defined in standards for 5G, New Radio (NR), and Long Term Evolution (LTE) systems. However, the present disclosure is not limited by terms and names, and may be equally applied to systems conforming to other standards.

In describing the embodiments of the present disclosure in detail, the communication standard defined by the 3GPP will be the main target, but the main subject of the present disclosure is not significantly departing from the scope of the present disclosure to other communication systems having a similar technical background. It can be applied with slight modifications in the range of, and this will be possible at the judgment of a person skilled in the technical field of the present disclosure.

In describing the embodiments of the present disclosure in detail, the vehicle communication service will be the main target, but the main gist of the present disclosure is, within a range not significantly departing from the scope of the present disclosure, even to other services provided in the 5G network. It can be applied as a modification, and this will be possible at the judgment of a person skilled in the technical field of the present disclosure.

The 5G system is considering supporting various services compared to the existing 4G system. For example, the most representative services are mobile ultra-wide band communication service (eMBB: enhanced mobile broad band), ultra-reliable and low latency communication service (URLLC: ultra-reliable and low latency communication), and large-scale device-to-device communication service (mMTC: massive machine type communication), evolved multimedia broadcast/multicast service (eMBMS), and the like. In addition, a system providing a URLLC service may be referred to as a URLLC system, and a system providing an eMBB service may be referred to as an eMBB system. In addition, the terms service and system may be used interchangeably.

Among them, URLLC service is a service newly considered in 5G system, unlike existing 4G system, and ultra-high reliability (for example, packet error rate about 10-5) and low latency (for example, compared to other services) About 0.5msec). In order to satisfy such strict requirements, the URLLC service may need to apply a transmission time interval (TTI) shorter than that of the eMBB service, and various operation methods utilizing this may be considered.

On the other hand, the Internet is evolving from a human-centered network in which humans generate and consume information, to an Internet of Things (IoT) network that exchanges and processes information between distributed components such as objects. IoE (Internet of Everything) technology, which combines IoT technology with big data processing technology through connection with cloud servers, is also emerging. In order to implement IoT, technology elements such as sensing technology, wired/wireless communication and network infrastructure, service interface technology, and security technology are required, and recently, a sensor network for connection between objects, machine to machine , M2M), and MTC (Machine Type Communication) technologies are being studied.

1 illustrates a configuration of a vehicle communication system according to an embodiment of the present disclosure.

Referring to FIG. 1, a terminal (user equipment, user terminal, terminal, or vehicle UE) may be used interchangeably. 110) communicates directly with another terminal 120 (for example, , Device-to-Device, D2D, ProSe, PC5, Sidelink communication, 140) or network communication 150, 160 through the mobile communication system 130 may be used. In the case of direct communication, message transmission and reception between the terminal 110 and the other terminal 120 may be performed through the PC5 link. In the case of network communication, a message sent from the transmitting vehicle terminal to the receiving vehicle terminal may be transmitted to the network through a Uu link and then transmitted to the receiving vehicle terminal through the Uu link. The mobile communication system 130 may be an EPC system defined by 3GPP, a 5GC system, or a communication system other than 3GPP. The direct communication 140 may be provided using a Long Term Evolution (LTE) Radio Access Technology (RAT) or a New Radio (NR) RAT or a non-3gpp RAT (eg, WiFi).

2A is a diagram illustrating a control plane protocol stack of a terminal according to an embodiment of the present disclosure, and FIG. 2B is a diagram illustrating a user plane protocol stack of a terminal according to an embodiment of the present disclosure. The terminal 110 may be a transmitting terminal or a receiving terminal, and the terminal 120 may be a receiving terminal or a transmitting terminal, but for convenience of description, the terminal 110 and the terminal 120 are respectively referred to.

Referring to Figure 2a, the control plane protocol stack of the terminal (110, 120) is a PC5 signaling protocol layer (PC5 Signaling Protocol layer, 210, 215), RRC layer (RRC layer, 220, 225), PDCP layer (PDCP layer, 230, 235), RLC layer (RLC layer, 240, 245), MAC layer (MAC layer, 250, 255), PHY layer (PHY layer, 260, 265) may be configured. The RRC layers 220 and 225, the PDCP layers 230 and 235, the RLC layers 240 and 245, and the MAC layers 250 and 255 may be collectively referred to as an AS layer (Access Stratum layer, 200, 205). In the following description of the present invention, the AS layer (200, 205) refers to the RRC layer (220, 225), the PDCP layer (230, 235), the RLC layer (240, 245), the MAC layer (250, 255) It may include at least one or more.

The PC5 signaling protocol layer (210, 215) is a link connection establishment (link establishment) and a link for direct communication 140 between the terminal 110 and the terminal 120 through the procedure shown in Figs. 4a, 4b to 4c A link maintenance function can be provided.

Referring to Figure 2a, the PC5 signaling (PC5-S) message of the terminal (110, 120) through the PC5 signaling protocol layer (210, 215), AS layer (200, 205), PHY layer (260, 265) It can be transmitted to the terminal.

Referring to FIG. 2B, the user plane protocol stack of the terminals 110 and 120 is an application layer (Application layer, 270, 275), an SE layer (Service Enabling layer, 280, 285), SDAP layer (SDAP layer, 290, 295). ), PDCP layer (PDCP layer, 230, 235), RLC layer (RLC layer, 240, 245), MAC layer (MAC layer, 250, 255), PHY layer (PHY layer, 260, 265) may be configured. . SDAP layers (290, 295), PDCP layers (230, 235), RLC layers (240, 245), MAC layers (250, 255) may be collectively referred to as an AS layer (Access Stratum layer, 200, 205). In the following description of the present invention, the AS layer (200, 205) refers to SDAP layer (290, 295), PDCP layer (230, 235), RLC layer (240, 245), MAC layer (250, 255) It may include at least one or more.

The SE layers 280 and 285 are intermediate layers for performing operations of the application layers 270 and 275 and may provide specialized functions for each application or service. One SE layer can support multiple application layers. In addition, a specialized SE layer may be defined for each application layer. For example, in order to provide a V2X service, the application layers 270 and 275 may be a V2X application layer. In addition, for the V2X application layer operation, the SE layers 280 and 285 may be defined as a V2X layer (V2X layer). In order to provide the following V2X service, the application layers 270 and 275 may be used interchangeably with the V2X application layer, and the SE layers 280 and 285 may be used interchangeably with the V2X layer.

The SE layers 280 and 285 may provide a data transmission function on a link established for direct communication 140 between the terminal 110 and the terminal 120. The SE layers 280 and 285 may include functions such as an IP protocol for message transmission, a non-IP protocol, and a transport protocol (for example, TCP or UDP).

The SDAP layers 290 and 295 may be used when transmitting data through direct communication 140 between the terminal 110 and the terminal 120. The direct communication 140 between the terminal 110 and the terminal 120 may be a PC5 broadcast communication mode, a PC5 groupcast communication mode, and a PC5 unicast communication mode. For example, when a direct communication 140 link connection between the terminal 110 and the terminal 120 is established and then data is transmitted through the established link (eg, PC5 unicast communication or PC5 groupcast communication), SDAP layer (290, 295) can be used for message transmission. In addition, for example, even when data is transmitted without establishing a direct communication 140 link connection between the terminal 110 and the terminal 120 (eg, PC5 broadcast communication or PC5 groupcast communication), the SDAP layer 290 , 295) can be used for message transmission.

The PC5 signaling protocol layers 210 and 215 according to an embodiment of the present disclosure may include functions provided by the SE layers 280 and 285 for link connection establishment and/or link connection management. Or, the PC5 signaling protocol layer (210, 215) is SE layer (280, 285) and / or RRC layer (220, 225) and / or PDCP layer (230, 235) and / or SDAP layer (290, 295) and You can interact.

3 illustrates a terminal operation for direct communication between a terminal and a terminal according to an embodiment of the present disclosure.

Referring to FIG. 3, the terminal 110 and the terminal 120 may store and run the same application 310, 315 or 350, 355 or 360, 365. Applications can be classified by application ID (eg, OSAppID, etc.). For example, application #1 310 of terminal 110 and application #1 315 of terminal 120 may be referred to by the same application ID. The applications 310 and 315 may provide one or more services. That is, for example, the applications 310 and 315 may include service type #1 (312, 317) and service type #2 (314, 319). Each service type can be classified by a service type ID (eg, PSID, ITS-AID, etc.).

Referring to FIG. 3, one or more applications are installed in a terminal according to an embodiment of the present invention, and one or more applications may be simultaneously operated. Application layer user IDs associated with each application (eg, terminal ID, terminal subscriber ID, GPSI, user e-mail address, etc.) can be used in various ways as follows.

For example, one application layer user ID may be used in one application. In this case, the application layer user ID may be assigned as a unique value for each user and application. Referring to FIG. 3, if Application#1(310), Application#2(350), Application#3(360) are installed in the terminal 110, each application Application#1(310), Application# 2(350) and Application#3(360) may be classified by an application layer user ID of each application. In this case, the SE layer 280 may classify each application (Application#1 310, Application#2 350, Application#3 360) by an application layer user ID. The difference between the application ID and the application layer user ID is that the application #1 310 of the terminal 110 and the application #1 315 of the terminal 120 may be referred to as the same application ID. Application #1 310 and application #1 315 of the terminal 120 may be referred to as different application layer user IDs, respectively.

Alternatively, one application layer user ID may be used in one or more applications. That is, one or more applications may share one application layer user ID. Referring to FIG. 3, Application#1 (310) and Application#2 (350) of the terminal 110 use one application layer user ID, and Application #3 (360) uses another application layer user ID. I can. In this case, the SE layer 280 may divide Application#1 (310) and Application#2 (350) into the same application layer user ID, and Application#3 (360) into one application layer user ID. have.

Alternatively, one application layer user ID can be used in all applications. That is, all applications can share one application layer user ID. Referring to FIG. 3, all applications 310, 350, and 360 installed in the terminal 110 may use one application layer user ID. That is, each application may not be additionally classified by using the application layer user ID. In this case, the SE layer 280 knows that one application layer user ID is applied to all applications of the terminal 110 and can be used.

In the following description of the present invention, the operation of the applications 310 to 315 to 350 to 355 to 360 to 360) and/or the service types 312, 314, 317, 319 is the application layer 270 and 275 shown in FIG. 2B. It can be understood as the operation of. One or more application and/or service types may be driven in the application layers 270 and 275.

The terminal 110 and the terminal 120 may create a direct communication 330 link using the procedure shown in FIG. 4A. Direct communication 330 link creation may be performed for PC5 unicast communication or PC5 groupcast communication. The terminal 110 and the terminal 120 may update the direct communication 330 link created using the procedure shown in FIG. 4C.

The terminal 110 and the terminal 120 may transmit and receive data using direct communication using the procedure shown in FIG. 4B. The data transmission/reception procedure shown in FIG. 4B may be PC5 unicast communication, PC5 groupcast communication, or PC5 broadcast communication.

[Example 1]

Hereinafter, a procedure of transmitting and receiving data after creating a direct communication 330 link will be described with reference to FIGS. 4A, 4B, and 4C.

According to an embodiment of the present invention, the terminal 110 and the terminal 120 may create a direct communication 330 link, and may perform signaling and data transmission for one or more applications in the direct communication 330 link.

4A illustrates a procedure for creating a direct communication link connection (ProSe link establishment) according to an embodiment of the present disclosure.

For the description of the present invention, the transmitting terminal 110 is a terminal initiating a direct communication link connection, and the remaining neighboring terminals 115, 120, and 125 are located at an adjacent distance to the transmitting terminal 110 so that the transmitting terminal 110 It is assumed that the terminal is capable of receiving the direct communication request message 425 transmitted. In addition, it is assumed that one or more of the peripheral terminals 115, 120, and 125, for example, the terminal 120, are a terminal 440 that directly communicates with the transmitting terminal 110.

Referring to FIG. 4A, the application layer 270 of the terminal 110 to perform the application operation is the'application ID' of the application 310 and/or 350 and/or 360 requesting direct communication in step 403, the application A'communication mode' (for example, PC5 broadcast, PC5 groupcast, PC5 unicast, etc.) indicating a communication method of (310 and/or 350 and/or 360), application 310 and/or 350 And/or 360), at least one or more of a'communication protocol' (for example, IP, non-IP, Ethernet (hereinafter, referred to as Ethernet), TCP, UDP, RDS, etc.) to be used may be provided to the SE layer 280. . In describing an embodiment of the present invention, the application layer 270 will assume that the application requesting direct communication in step 403 is the application #1 310 and the embodiment will be described. According to the'communication protocol' to be used in the application 310, the application layer 270 may additionally provide the following information to the SE layer 280 in step 403.

When an IP protocol is included in the'communication protocol', the application layer 270 may determine the'IP address' of the terminal 110 to be used for the application 310 and provide it to the SE layer 280. Alternatively, if the application layer 270 does not provide the information, the SE layer 280 may determine the'IP address' of the terminal 110 to be used for the application 310 in step 406.

When a non-IP protocol is included in the'communication protocol', the application layer 270 determines'Reliable Data Service (RDS) configuration information' to be used for the application 310 and provides it to the SE layer 280. I can. Alternatively, if the application layer 270 does not provide the information, the SE layer 280 may determine'RDS configuration information' to be used for the application 310 in step 406. In describing the embodiments of the present invention below,'RDS configuration information' may mean the RDS protocol defined by 3GPP, but it does not exactly follow the RDS protocol, but it is possible to exchange ports for an application used between two entities. It can mean including protocols that exist. RDS configuration information may include a source port or a destination port. This means a port that can identify an App using D2D communication used by each terminal. Therefore, the application layer 270 allocates a port to be used to identify a packet transmitted to the application in'Reliable Data Service (RDS) configuration information' to be used for the application 310 and provides it to the SE layer 280. I can. Alternatively, if the application layer 270 does not provide the information, in step 406, the SE layer 280 selects a port to be used to identify a packet transmitted to the application in'RDS configuration information' to be used for the application 310. You can decide.

When an Ethernet protocol is included in the'communication protocol', the application layer 270 may determine'Ethernet flow information' to be used for the application 310 and provide it to the SE layer 280. Alternatively, if the application layer 270 does not provide the information, the SE layer 280 may determine'Ethernet flow information' to be used for the application 310 in step 406. Hereinafter, in describing the embodiments of the present invention, the'Ethernet flow information' may include at least one of an Ethernet type (ethType), a flow description, a flow direction, and a vlan tag.

When a non-IP protocol or an Ethernet protocol is included in the'communication protocol', the application layer 270 is the'Layer-2 address' of the terminal 110 to be used for the application 310 (e.g., MAC address Alternatively, a ProSe Layer-2 address, etc.) may be determined and provided to the SE layer 280. Alternatively, if the application layer 270 does not provide the information, the SE layer 280 may determine a'Layer-2 address' to be used for the application 310 in step 406.

When TCP or UDP protocol is included in the'communication protocol', the application layer 270 determines the'transport layer port number' to be used for the application 310 and provides it to the SE layer 280. I can. In addition, the application layer 270 may determine a'port driving timer' indicating a time when the'transport layer port number' is driven and provide it to the SE layer 280. Alternatively, if the application layer 270 does not provide the information, the SE layer 280 may determine a'transport layer port number' and a'port driving timer' to be used for the application 310 in step 406. The application layer 270 and/or the SE layer 280 may not process data received through a corresponding port number after the'port driving timer' expires. The following shows an example of information that the application layer 270 can provide to the SE layer 280 in step 403.

- 'Application ID' of the application 310,

- 'Communication mode' indicating the communication method of the application 310,

- 'Communication protocol' to be used in the application 310,

- 'IP address' of the terminal 110

- 'Transport layer port number' and'port driving timer' to be used in the application 310

- 'Layer-2 address' of terminal 110

- 'RDS setting information' to be used in the application 310

- 'Ethernet flow information' to be used in the application 310

If the application layer 270 has two or more applications requesting direct communication in step 403, the above-described information may be added for each application.

The SE layer 280 of the terminal 110 requests a direct communication in step 406 based on the information received from the application layer 270 in step 403 and/or the information determined by the SE layer 280 in step 406. ) You can create a message. The direct communication request message is a'application ID' of the application 310 received from the application layer 270 in step 403 and/or determined by the SE layer 280 in step 406, a'communication protocol' to be used in the application 310, 'IP address' of the terminal 110,'transport layer port number' to be used for the application 310,'port driving timer','layer-2 address' of the terminal 110,'RDS setting' to be used for the application 310 At least one of'information' and'Ethernet flow information' to be used for the application 310 may be included.

The SE layer 280 of the terminal 110 may store the information included in the direct communication request message and use it for subsequent direct communication.

The SE layer 280 may directly transmit a communication request message to the terminal 120 through the AS layer 200 and the PHY layer 260 in step 409. Upon receiving the direct communication request message, the SE layer 285 of the terminal 120 may store information included in the direct communication request message and transmit the received direct communication request message to the application layer 275. The application layer 275 may decide to accept the received direct communication request based on information included in the received direct communication request message, etc., and decide to reply to the direct communication request message.

The application layer 275 of the terminal 120, which wishes to accept the direct communication request, includes the application (310 of the 110 terminal (corresponding to 315 of the 120 terminal)) included in the received direct communication request message and/or to be used for the application. A'communication protocol' to be used in the application 315 may be determined based on the'communication protocol' information. The application layer 275 of the terminal 120 is a'application ID' of the application 315 requesting direct communication in step 412, and a'communication mode' indicating a communication method of the application 315 (for example, , PC5 broadcast, PC5 groupcast, PC5 unicast, etc.), at least one of the'communication protocol' to be used in the application 315 (eg, IP, non-IP, Ethernet (hereinafter referred to as Ethernet), TCP, UDP, etc.) The above can be provided to the SE layer 285.

According to the'communication protocol' to be used in the application, the application layer 275 may additionally provide the following information to the SE layer 285 in step 412.

When the IP protocol is included in the'communication protocol', the application layer 275 may determine the'IP address' of the terminal 120 to be used for the application and provide it to the SE layer 285. Alternatively, if the application layer 275 does not provide the information, the SE layer 285 may determine the'IP address' of the terminal 120 to be used for the application in step 415.

When a non-IP protocol is included in the'communication protocol', the application layer 275 may determine the'RDS configuration information' to be used for the application and provide it to the SE layer 285. UE-3 (120) checks the'RDS configuration information' included in the Direct Communication Request message sent by UE-1 (110) through step 409. This RDS configuration information may include source port information configured and sent by UE-1. This includes a port for identifying an application that transmits/receives data through the corresponding D2D communication in UE-1. Accordingly, the SE layer may set a port to be used by an application of UE-1 to identify a packet through D2D communication as a destination port in'Reliable Data Service (RDS) configuration information' to be used in the application. The application layer receiving this may allocate a port to identify its own application for transmitting and receiving data between the UE-1 and the application layer. UE-3 can distinguish the application used for D2D communication with UE-1 by port information, and the port that can identify its application is the source port, and the port received from the UE-1 is the destination port. By setting it to, it can be included and configured in the RDS setting information. The application layer of UE-3 can deliver the RDS configuration information set by itself to the SE layer. Therefore, the SE layer stores the port sent by UE-1 as the destination port and the port allocated by the application layer as the source port according to the RDS configuration information received from the application layer, and can be used for D2D unicast communication. have.

Alternatively, if the application layer 275 does not provide the information, the SE layer 285 may determine'RDS configuration information' to be used for the application in step 412. This RDS configuration information includes a port that can identify an application that transmits/receives data through the corresponding D2D communication at the UE-1 terminal configured and sent by UE-1. Accordingly, the SE layer may set a port to be used by an application of UE-1 to identify a packet through D2D communication as a destination port in'Reliable Data Service (RDS) configuration information' to be used in the application. In addition, the SE layer can allocate a port that can identify its own application for transmitting and receiving data between the UE-1 and the application layer. Therefore, the SE layer of UE-3 can distinguish the application used for D2D communication with UE-1 by port information, and the port that can identify its application is a source port and received from UE-1. By setting the port as the destination port, you can include and configure the RDS setting information. In other words, the SE layer stores the port sent by UE-1 as the destination port and the port allocated by the application layer as the source port according to the RDS configuration information set as above, and is used for D2D unicast communication. can do.

When an Ethernet protocol is included in the'communication protocol', the application layer 275 may determine'Ethernet flow information' to be used for the application and provide it to the SE layer 285. Alternatively, if the application layer 275 does not provide the information, the SE layer 285 may determine'Ethernet flow information' to be used for the application in step 415.

When the'communication protocol' includes a non-IP protocol or an Ethernet protocol, the application layer 275 is the'Layer-2 address' of the terminal 120 to be used for the application (e.g., MAC address or ProSe Layer -2 address, etc.) can be determined and provided to the SE layer 285. Alternatively, if the application layer 275 does not provide the information, in step 415, the SE layer 285 may determine a'Layer-2 address' to be used for the application.

When a TCP or UDP protocol is included in the'communication protocol', the application layer 275 may determine the'transport layer port number' to be used for the application and provide it to the SE layer 285. In addition, the application layer 275 may determine a'port driving timer' indicating a time when the'transport layer port number' is driven and provide it to the SE layer 285. Alternatively, if the application layer 275 does not provide the information, in step 415, the SE layer 285 may determine a'transport layer port number' and a'port driving timer' to be used for the application. The application layer 275 and/or the SE layer 285 may not process data received through a corresponding port number after the'port driving timer' expires. The following shows an example of information that the application layer 275 can provide to the SE layer 285 in step 412.

- 'Application ID' of the application 315,

- 'Communication mode' indicating the communication method of the application 315,

- 'Communication protocol' to be used in the application 315,

- 'IP address' of the terminal 120

- 'Transport layer port number' and'port drive timer' to be used in the application 315

- 'Layer-2 address' of terminal 120

- 'RDS setting information' to be used in the application 315

- 'Ethernet flow information' to be used in the application 315

The SE layer 285 of the terminal 120 is based on the information received from the application layer 275 in step 412 and/or the information determined by the SE layer 285 in step 415, based on the direct communication response in step 415. ) You can create a message. The direct communication response message is the'application ID' of the application 315 received from the application layer 275 in step 412 and/or determined by the SE layer 285 in step 415,'communication protocol' to be used in the application 315, 'IP address' of terminal 120,'transport layer port number' to be used for application 315,'port driving timer','layer-2 address' of terminal 110,'RDS setting' to be used for application 315 Information” and “Ethernet flow information” to be used for the application 315 may be included.

The SE layer 285 of the terminal 120 may store the information included in the direct communication response message and use it for subsequent direct communication.

The SE layer 285 may directly transmit a communication response message to the terminal 110 via the AS layer 205 and the PHY layer 265 in step 418.

The SE layer 280 of the terminal 110 receiving the direct communication response message may store the information included in the received direct communication response message and use it for subsequent direct communication.

The SE layer 280 of the terminal 110 may inform the application layer 270 that a direct communication link connection has been established. In this case, the SE layer 280 of the terminal 110 may transmit the received direct communication response message to the application layer 270.

When the non-IP protocol is included in the'communication protocol', the UE-1 110 checks the'RDS configuration information' included in the Direct Communication Response message sent by the UE-3 120 through step 418. This RDS configuration information includes a port that can identify an application that transmits/receives data through the corresponding D2D communication in UE-3 in the form of a source port. Therefore, the SE layer transmits data from UE-1 to UE-3 in the source port that the application of UE-3 will use to identify packets through D2D communication in'Reliable Data Service (RDS) configuration information' to be used in the application. It can be set as the destination port to be used when sending. The SE layer can deliver this to the application layer. Upon receiving this, the application layer sets the port that can identify its application for transmitting and receiving data between the UE-3 and the application layer as the source port and the port received from the UE-3 as the destination port, and includes it in the RDS configuration information. , Configurable. The application layer of UE-1 can deliver the RDS configuration information set by itself to the SE layer. Therefore, according to the RDS configuration information received from the application layer, the SE layer stores a port for UE-3 as a destination port and a port for itself as RDS configuration information set as a source port, and can be used for D2D unicast communication.

Alternatively, if the application layer 275 does not provide the information, the SE layer 285 may determine'RDS configuration information' to be used for the application in step 412. The SE layer of UE-1 is set by UE-3 and sets the'Source Port to identify an application transmitting and receiving data through the D2D communication in the UE-3 terminal' sent through step 418 as a destination port. In addition, the'Source Port that can identify an application that transmits/receives data through D2D communication' allocated by itself before step 409 is set as a source port. Therefore, the SE layer uses the'Reliable Data Service (RDS) configuration information' to be used in the application. The port that the UE-1 application will use to identify packets through D2D communication is the source port, and the UE-3 application is A port to be used to identify a packet through D2D communication can be set as a destination port. In other words, the SE layer stores the port sent by UE-3 as the destination port and the port to be used as the source port according to the RDS configuration information set as described above, and can be used for D2D unicast communication. have.

4B illustrates a data transmission procedure using a direct communication link according to an embodiment of the present disclosure.

Referring to FIG. 4B, the terminal 110 and the terminal 120 may complete the direct communication link connection setup through the procedure described above in FIG. 4A. The terminals 110 and 120 may store information related to the terminals 110 and 120 and applications 310 and 315 supported by the direct communication link during the process of establishing a direct communication link connection.

The application layer 270 of the terminal 110 determines to transmit the application data on the direct communication link in step 424, and the'application ID' of the application 310, the'application data' of the application 310, and the application 310 ) At least one of the'communication protocols' to be used in the SE layer 280 may be provided.

In step 427, the SE layer 280 stores information included in the direct communication request message and/or the information included in the direct communication response message stored in the procedure of FIG. 4a, and/or the information received from the application layer 270 in step 424. Based on the determination of a communication protocol required for application data transmission, the following operations can be performed.

When the applications 310 and 315 supported by the direct communication link support the IP protocol, the SE layer 280 may generate an IP header of the application data and determine a source IP address and a destination IP address of the IP header. The source IP address may be the'IP address' of the terminal 110. The destination IP address may be the'IP address' of the terminal 120.

When the applications 310 and 315 supported by the direct communication link support the UDP or TCP protocol, the SE layer 280 may generate a transport layer header of the application data and determine a port number of the transport layer header. The port number may be a'transport layer port number' to be used for the application 315.

When the applications 310 and 315 supported by the direct communication link support the non-IP protocol or the Ethernet protocol, the SE layer 280 generates a layer-2 header of the application data, and the source terminal address of the layer-2 header and The destination terminal address can be determined. The source terminal address may be a'layer-2 address' of the terminal 110. The destination terminal address may be a'layer-2 address' of the terminal 120.

When the applications 310 and 315 supported by the direct communication link support the non-IP protocol or RDS, the application layer 270 provides'Reliable Data Service (RDS) configuration information' to be used in the application through D2D communication. A source port and a destination port to be used to identify a transmitted packet may be provided to the SE layer 280 by including in a data header. Alternatively, when the application layer 270 does not provide the information, in order to identify a packet transmitted through D2D communication, according to the'RDS setting information' set by the SE layer 280 according to the method according to FIG. 4A Source Port and Destination Port to be used can be included in the data header. For example, when UE 1 and UE 3 perform D2D communication, UE 1 may set and transmit a port used for D2D communication in its application as a source port. In addition, the port used for D2D communication in the application used by UE 3 that receives the data it sends can be set as the destination port.

In step 430, the SE layer 280 stores the'application data' received in step 424 and the'application data related information' determined in step 427 (e.g., layer-2 header, IP header, transport layer header, etc.) to the AS layer. It may be transmitted to the terminal 120 through 200 and the PHY layer 260.

The SE layer 285 of the terminal 120 that received the'application data' and'application data related information' in step 431 is the information included in the direct communication request message stored during the procedure of FIG. 4A and/or the direct communication response message. Based on the information included in and/or the'application data related information' received from the terminal 110 in step 430, an application of the application layer 275 to deliver the'application data' may be determined in the following manner.

When the port number of the transport layer header of the'application data related information' and the'transport layer port number' to be used for the application 315 match, the SE layer 275 may transmit data to the corresponding application 315.

When the RDS information of the'application data related information' and the RDS information to be used for the application 315 match, the SE layer 275 may transmit data to the corresponding application 315. That is, the SE layer can see the configured RDS configuration information and compare the ports included in the header of the data. Therefore, if the destination port of the header of the received data is viewed and matches the source port included in its own RDS configuration information, an application using the corresponding destination port can be determined. In addition, the SE layer may further compare the source port of the received data header with the destination port included in the RDS configuration information set to itself to determine which application to transmit data to. After determining the application as described above, the SE layer may transmit data to the application.

4C illustrates a direct communication link update procedure according to an embodiment of the present disclosure.

Referring to FIG. 4C, the terminal 110 and the terminal 120 may update'application data related information' exchanged through the procedure described above in FIG. 4A.

[Example 2]

Hereinafter, a procedure for transmitting and receiving data without a direct communication 330 link creation procedure will be described with reference to FIGS. 4B and 5.

5 illustrates a procedure for a terminal to obtain'application data related information' from a network according to an embodiment of the present disclosure.

Referring to FIG. 5, the terminals 110 and 120 may register with the network through steps 1 to 12. The registration acceptance message of step 12a may include'application data related information'. Upon receiving the registration permission message of step 12a, the terminals 110 and 120 may store the'application data related information' included in the registration permission message and use it for subsequent direct communication.

Alternatively, the terminals 110 and 120 may store the'application data related information' included in the step 13a message while receiving the step 13a message after the registration procedure of steps 1 to 12, and use it for subsequent direct communication.

Alternatively, the terminals 110 and 120 may request'application data related information' from the AMF 503 in step 14a after the registration procedure of steps 1 to 12. The AMF 503, which has received a request for'application data related information' from the terminals 110 and 120, may include'application data related information' in the 14d message transmitted to the terminals 110 and 120. The terminals 110 and 120 may store the'application data related information' included in the step 14d message and use it for subsequent direct communication.

Terminals 110 and 120 that have obtained'application data related information' through the procedure shown in FIG. 5 may directly communicate through the procedure shown in FIG. 4B without a direct communication link creation procedure.

Referring to FIG. 4B, the terminal 110 and the terminal 120 may acquire and store'application data related information' through the procedure described above in FIG. 5.

The application layer 270 of the terminal 110 determines to transmit the application data on the direct communication link in step 424, and the'application ID' of the application 310, the'application data' of the application 310, and the application 310 ) At least one of the'communication protocols' to be used in the SE layer 280 may be provided.

In step 427, the SE layer 280 determines a communication protocol required for application data transmission based on the'application data related information' stored in the procedure of FIG. 5 and/or the information received from the application layer 270 in step 424. , You can perform the following operations.

When the applications 310 and 315 supported by the direct communication link support the IP protocol, the SE layer 280 may generate an IP header of the application data and determine a source IP address and a destination IP address of the IP header. The source IP address may be the'IP address' of the terminal 110. The destination IP address may be the'IP address' of the terminal 120.

When the applications 310 and 315 supported by the direct communication link support the UDP or TCP protocol, the SE layer 280 may generate a transport layer header of the application data and determine a port number of the transport layer header. The port number may be a'transport layer port number' to be used for the application 315.

When the applications 310 and 315 supported by the direct communication link support the non-IP protocol or the Ethernet protocol, the SE layer 280 generates a layer-2 header of the application data, and the source terminal address of the layer-2 header and The destination terminal address can be determined. The source terminal address may be a'layer-2 address' of the terminal 110. The destination terminal address may be a'layer-2 address' of the terminal 120.

When the applications 310 and 315 supported by the direct communication link support the non-IP protocol or RDS, the application layer 270 provides'Reliable Data Service (RDS) configuration information' to be used in the application through D2D communication. A source port and a destination port to be used to identify a transmitted packet may be provided to the SE layer 280 by including in a data header. Alternatively, when the application layer 270 does not provide the information, in order to identify a packet transmitted through D2D communication, according to the'RDS setting information' set by the SE layer 280 according to the method according to FIG. 4A Source Port and Destination Port to be used can be included in the data header. For example, when UE 1 and UE 3 perform D2D communication, UE 1 may set and transmit a port used for D2D communication in its application as a source port. In addition, the port used for D2D communication in the application used by UE 3 that receives the data it sends can be set as the destination port.

In step 430, the SE layer 280 stores the'application data' received in step 424 and the'application data related information' determined in step 427 (e.g., layer-2 header, IP header, transport layer header, etc.) to the AS layer. It may be transmitted to the terminal 120 through 200 and the PHY layer 260.

The SE layer 285 of the terminal 120 that received the'application data' and the'application data related information' in step 431, the'application data related information' stored in the procedure of FIG. 5 and/or the terminal ( Based on the'application data related information' received from 110), an application of the application layer 275 to which the'application data' is to be delivered may be determined in the following manner.

When the port number of the transport layer header of the'application data related information' and the'transport layer port number' to be used for the application 315 match, the SE layer 275 may transmit data to the corresponding application 315.

When the RDS information of the'application data related information' and the RDS information to be used for the application 315 match, the SE layer 275 may transmit data to the corresponding application 315. That is, the SE layer can see the configured RDS configuration information and compare the ports included in the header of the data. Therefore, if the destination port of the header of the received data is viewed and matches the source port included in its own RDS configuration information, an application using the corresponding destination port can be determined. In addition, the SE layer may further compare the source port of the received data header with the destination port included in the RDS configuration information set to itself to determine which application to transmit data to. After determining the application as described above, the SE layer may transmit data to the application.

6A is a block diagram illustrating a configuration of a network entity according to an embodiment of the present disclosure.

A network entity according to an embodiment of the present disclosure may include a mobile communication system 130.

Referring to FIG. 6A, the network entity may include a transmission/reception unit 600, a control unit 610, and a storage unit 620. The transmission/reception unit 600, the control unit 610, and the storage unit 620 of the network entity may operate according to the above-described communication method of the network entity. However, the elements of the network entity are not limited to the above-described example. For example, the network entity may include more or fewer components than the above-described components. In addition, the transmission/reception unit 600, the control unit 610, and the storage unit 620 may be implemented in the form of a single chip. In addition, the control unit 610 may include at least one processor.

The transmission/reception unit 600 collectively refers to the reception unit 606 of the network entity and the transmission unit 603 of the network entity, and may transmit and receive signals. The transmitted/received signal may include control information and data. To this end, the transceiving unit 600 may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, and an RF receiver that amplifies a received signal with low noise and down-converts a frequency. However, this is only an embodiment of the transmission/reception unit 600, and components of the transmission/reception unit 600 are not limited to the RF transmitter and the RF receiver.

In addition, the transmission/reception unit 600 may receive a signal through a wireless channel, output it to the control unit 610, and transmit a signal output from the control unit 610 through a wireless channel.

The storage unit 620 may store programs and data necessary for the operation of the network entity. In addition, the storage unit 620 may store control information or data included in a signal obtained from a network entity. The control unit 620 may be configured with a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, and a DVD, or a combination of storage media.

The controller 610 may control a series of processes so that the network entity can operate according to the above-described embodiment of the present disclosure. For example, the control unit 610 may receive a control signal and a data signal through the transceiving unit 600 and process the received control signal and data signal. In addition, the control unit 610 The signal may be transmitted through the transceiver 600.

6B is a block diagram illustrating a configuration of a terminal according to an embodiment of the present disclosure.

Specifically, FIG. 6B may be a block diagram illustrating the internal structure of the terminals 110, 115, 120, and 125 according to an embodiment of the present disclosure. The terminal may include a transmission/reception unit 650, a control unit 660 and a storage unit 670.

According to the above-described communication method of the terminal, the transmission/reception unit 650, the control unit 660, and the storage unit 670 of the terminal may operate. However, the components of the terminal are not limited to the above-described example. For example, the terminal may include more or fewer components than the above-described components. In addition, the transmission/reception unit 650, the control unit 660, and the storage unit 670 may be implemented in the form of a single chip. In addition, the control unit 660 may include at least one or more processors.

The transmission/reception unit 650 is collectively referred to as the reception unit 656 of the terminal and the transmission unit 653 of the terminal, and may transmit and receive signals to and from the base station. Signals transmitted and received with the base station may include control information and data. To this end, the transceiver 650 may include an RF transmitter that up-converts and amplifies a frequency of a transmitted signal, and an RF receiver that amplifies a received signal with low noise and down-converts a frequency. However, this is only an embodiment of the transmission/reception unit 650, and components of the transmission/reception unit 650 are not limited to the RF transmitter and the RF receiver.

In addition, the transmission/reception unit 650 may receive a signal through a wireless channel, output it to the control unit 660, and transmit a signal output from the control unit 660 through a wireless channel.

The storage unit 670 may store programs and data necessary for operation of the terminal. In addition, the storage unit 670 may store control information or data included in a signal obtained from the terminal. The storage unit 670 may be composed of a storage medium such as a ROM, a RAM, a hard disk, a CD-ROM, a DVD, or a combination of storage media.

The controller 660 may control a series of processes so that the terminal can operate according to the above-described embodiment of the present disclosure. For example, the control unit 660 may receive a control signal and a data signal through the transceiving unit 650 and process the received control signal and data signal. The signal may be transmitted through the transceiver 650.

The embodiments disclosed in the present specification and drawings are merely provided specific examples for easy explanation and understanding of the present invention, and are not intended to limit the scope of the present invention. In addition, one or more of the above-described embodiments may be combined with each other and performed, and parts of the embodiments may be combined with each other and performed. Therefore, the scope of the present invention should be construed that all changes or modified forms derived based on the present disclosure in addition to the embodiments disclosed herein are included in the scope of the present invention.

Claims (1)

In the control signal processing method in a wireless communication system,
Receiving a first control signal;
Processing the received first control signal; And
And transmitting a second control signal generated based on the processing.

Images