Patent Description:
Therefore, the <NUM> or pre-<NUM> communication system is also called a "Beyond <NUM> Network' or a 'Post LTE System'.

In line with this, a method for provisioning service parameters related to service-specific information to user equipment(UE) has been researched. <NPL>, is a technical specification and defines the Stage <NUM> procedures and Network Function Services for the <NUM> system architecture. <NPL>, discloses details relating to a UE which uses the UE route selection policy, URSP, rules to route IMS traffic via the appropriate <NUM> network slice.

Vehicle-to-everything (V2X) is a general term that refers to all types of communication schemes applicable to road vehicles. With the advancement of wireless communication technology, V2X enables various additional services, in addition to initial safety use cases.

Wireless access in vehicular environments (WAVE) standards based on IEEE <NUM>. 11p and IEEE P1609 have been established to provide V2X services. However, WAVE, a type of dedicated short range communication (DSRC) technology, has a limitation on the coverage of messages between vehicles.

To overcome this limitation, the 3GPP is currently in the process of specifying standards for cellular-based V2X technology. LTE-based evolved packet system (EPS) V2X standards have been completed in Release <NUM>/Release <NUM>, and NR-based <NUM>th generation system (5GS) V2X standards are under discussion in Release <NUM>.

The technical subjects pursued in the disclosure may not be limited to the above mentioned technical subjects, and other technical subjects which are not mentioned may be clearly understood through the following descriptions by those skilled in the art of the disclosure.

An aspect of the disclosure is to provide a method for provisioning V2X service-related parameters to a user equipment (UE) in a V2X system.

In accordance with an aspect of the disclosure, a method performed by a device for performing a network exposure function (NEF) in a communication system is provided as defined by the appended set of claims.

In accordance with another aspect of the disclosure, a method performed by a device for performing a unified data repository (UDR) function in a communication system is provided as defined by the appended set of claims.

In accordance with another aspect of the disclosure, a method performed by a device for performing a policy control function (PCF) in a communication system is provided as defined by the appended set of claims.

According to the disclosure, there is an advantage in that a vehicle UE can use a vehicular communication service provided in a V2X system. Here, the vehicle UE may be a built-in device of a vehicle or a terminal attached to a vehicle, such as a smartphone or a black box.

A UE according to an embodiment can be connected to a 5GS so as to use a 5GS V2X service through an LTE or NR radio technology, and a V2X service provider can perform V2X service parameter provisioning to the UE.

Effects obtainable from the disclosure may not be limited to the above mentioned effects, and other effects which are not mentioned may be clearly understood through the following descriptions by those skilled in the art of the disclosure.

Hereinafter, the operating principle of the disclosure will be described in detail with reference to the accompanying drawings. In describing the disclosure below, a detailed description of related known configurations or functions incorporated herein will be omitted when it is determined that the detailed description thereof may unnecessarily obscure the subject matter of the disclosure. The terms as described below are those defined in consideration of the functions in the disclosure, and thus the meanings thereof may be different according to users, intentions of operators, or customs. Therefore, the definitions of the terms should be made on the basis of the contents throughout the specification.

As used herein, terms for identifying access nodes, terms referring to network entities, terms referring to messages, terms referring to interfaces between network entities, terms referring to various identification information, and the like are illustratively provided for the convenience of description. Therefore, the disclosure is not limited by the terminology provided below, and other terms indicating subjects having equivalent technical meanings may be used.

In describing the disclosure below, terms and names defined in the standards for <NUM> systems will be used for the convenience of description. However, the disclosure is not limited by those terms and names, and may also be similarly applied to systems according to other standards.

In the following detailed description of embodiments, the disclosure is directed to the communication standards defined by 3GPP, but the subject matter of the disclosure can be applied to any other communication system having the similar technical background through slight modifications and changes, which may be made according to determinations of those skilled in the art, without departing from the scope of the disclosure.

In the following detailed description of embodiments, the disclosure is directed to a vehicular communication service, but the subject matter of the disclosure can be applied to any other service provided in a <NUM> network through slight modifications and changes, which may be made according to determinations of those skilled in the art, without departing from the scope of the disclosure.

<FIG> illustrates a configuration view of an example of a V2X system architecture and connections between network entities and vehicle UEs according to an embodiment. An evolved packet system (EPS)-based V2X system may include an evolved packet core (EPC) core network <NUM> and long term evolution (LTE) base stations <NUM>, <NUM>. A 5th generation system (5GS)-based V2X system may include a 5th generation core (5GC) core network <NUM> and new radio (NR) base stations <NUM>, <NUM>. In the following description, the terms "base station" and "radio access network (RAN)" may be used interchangeably. Further, the terms "LTE base station", "<NUM> base station", and "eNB" may be used interchangeably. Further, the terms "NR base station", "<NUM> base station", and "gNB" may be used interchangeably, Further, the terms "application server (AS)" and "application function (AF)" may be used interchangeably.

The base station <NUM> connected concurrently to the EPC core network <NUM> and the 5GC core network <NUM> can provide both the LTE base station function and the NR base station function. The base station <NUM> may be referred to as "<NUM> base station" or "gNB". The EPS V2X function in the disclosure means a function of allowing a UE to access an EPS, which is the <NUM> core network, so as to use a V2X service. Since a <NUM> UE uses LTE as the wireless access technology, it can be said that a UE supporting the EPS V2X function accesses an EPS and uses the LTE V2X function. LTE V2X means a V2X technology which is provided as a device-to-device communication technology in LTE, and may be referred to as "LTE PC5". The 5GS V2X function in the disclosure means a function of allowing a UE to access an 5GS, which is the <NUM> core network, so as to use a V2X service. Since a <NUM> UE can use LTE (or LTE advanced) and new radio (NR) as the wireless access technology, it can be said that a UE supporting the 5GS V2X function accesses a 5GS and uses the LTE V2X and NR V2X functions. NR V2X means a V2X technology which is provided as a device-to-device communication technology in NR, and may be referred to as "NR PC5 interface".

A vehicle UE according to an embodiment may provide the EPS V2X function, the 5GS V2X function, or both the EPS V2X function and the 5GS V2X function. The vehicle UE providing the EPS V2X function can provide an LTE-based direct communication interface (e.g., LTE PC5 interface, D2D interface, or the like). Further, the vehicle UE providing the EPS V2X function can access an EPS core so as to be provided with a V2X service from a V2X application server (AS) through the EPS core. The vehicle UE providing the 5GS V2X function can provide an <NUM>-based direct communication interface (e.g., NR PC5 interface, D2D interface, or the like). Further, the vehicle UE providing the 5GS V2X function can access a 5GS core so as to be provided with a V2X service from a V2X AS through the 5GS core.

Referring to <FIG>, a vehicle UE <NUM> having the EPS V2X function may be connected to the EPC core network <NUM> via the LTE base station <NUM> by using the EPS V2X function. Alternatively, a vehicle UE <NUM> having the 5GS V2X function may be connected to the 5GC core network <NUM> via the NR base station <NUM> by using the 5GS V2X function. Alternatively, a vehicle UE <NUM> having the EPS V2X function and the 5GS V2X function may be connected to the EPC core network <NUM> via the LTE base station <NUM> by using the EPS V2X function. Alternatively, the vehicle UE <NUM> having the EPS V2X function and the 5GS V2X function may be connected to the 5GC core network <NUM> via the NR base station <NUM> by using the 5GS V2X function.

Referring to <FIG>, the 5GC core network <NUM> may include network entities. The network entities may include AMF, SMF, UPF, UDM, PCF, NEF, AF, and the like defined by 3GPP.

A <NUM> network system according to an embodiment can provide various services on the <NUM> network. That is, service providers (SPs) for services can provide the services through the <NUM> network.

In order to provide the services through the <NUM> network system, the service providers may have to provision service-related pre-configuration information to UEs. To this end, the <NUM> system may provide a method by which the service providers can perform service-related pre-configuration information provisioning to UEs.

An example of a UE provisioning service provided in the <NUM> system is shown in Table <NUM> below.

Referring to Table <NUM> showing examples of NF services provided by the NEF, the <NUM> system may allow a service provider to transmit configuration information to a UE. The service provider may be represented by "application server (AS)" or "application function (AF)".

A V2X AS according to an embodiment may deliver V2X service-related service parameter configuration information to a UE by using the Nnef_UEProvisioning service according to a procedure illustrated in <FIG>. In the detailed description of embodiments, the service name of a service for provisioning service-related pre-configuration information to a UE by the <NUM> system is referred to as "Nnef_UEProvisioning", but this is merely an example, and the service may be referred to as any other service name such as Nnef_ServiceProvisioning or Nnef_ServiceParameterProvisioning.

The Nnef_UEProvisioningservice in Table <NUM> may provide services as shown in Table <NUM> below.

The "Create" operation of the Nnef_UEProvisioning service may require input and output values as shown in Table <NUM> below.

The provisioning information in Table <NUM> may include values given in Tables <NUM>, <NUM>, <NUM>, and <NUM>.

The "Update" operation of the Nnef_UEProvisioning service may require input and output values as shown in Table <NUM>.

The "Delete" operation of the Nnef_UEProvisioning service may require input and output values as shown in Table <NUM>.

<FIG> illustrates a UE provisioning procedure according to an embodiment.

Referring to <FIG>, the V2X AS <NUM> according to an embodiment may generate a UE provisioning request message for service parameter provisioning to a UE which has subscribed to a V2X service (step <NUM>). An example of the UE provisioning request message generated by the V2X AS is shown in Table <NUM> below.

The UE provisioning request message may include "Service Description" which indicates the service provided by the V2X AS <NUM>. The V2X AS according to an embodiment provides a vehicular communication service (V2X), and thus the "Service Description" may be represented by a value indicating V2X (e.g., AF-Service-Identifier indicating V2X, S-NSSAI indicating V2X, or the like).

The UE provisioning request message may include "Target UE Identifier(s)" which indicates the UE that is the target for delivery of service parameters provided by the V2X AS <NUM>. The V2X AS according to an embodiment may include a GPSI or External Group Identifier as the "Target UE identifier". The GPSI may indicate one UE. The External Group Identifier may indicate a group of one or more UEs.

The UE provisioning request message may include "AF transaction identifier" for identifying the UE provisioning request message generated by the V2X AS.

The UE provisioning request message may include configuration information (corresponding to "Service parameters" in Table <NUM>) which is necessary for the UE <NUM> to use the V2X service provided by the V2X AS <NUM>. Further, the UE provisioning request message may include the version information (corresponding to "PII (Provisioning Information identifier)" in Table <NUM>) of the "Service parameters".

The V2X service configuration information (corresponding to the "Service parameters" in Table <NUM>) may include V2X service-related configuration information for a vehicle UE having the 5GS V2X function. Further, the V2X service configuration information (corresponding to the "Service parameters" in Table <NUM>) may include V2X service-related configuration information for a vehicle UE having the EPS V2X function.

For PC5 communication (device-to-device communication) of a vehicle UE having the 5GS V2X function, the V2X service-related configuration information for a vehicle UE having the 5GS V2X function may include information as shown in Table <NUM> below.

Further, for Uu communication (communication through a network) of a vehicle UE having the 5GS V2X function, the V2X service-related configuration information for a vehicle UE having the 5GS V2X function may include information as shown in Table <NUM> below.

For PC5 communication (device-to-device communication) of a vehicle UE having the EPS V2X function, the V2X service-related configuration information for a vehicle UE having the EPS V2X function may include information as shown in Table <NUM> below.

Further, for Uu communication (communication through a network) of a vehicle UE having the EPS V2X function, the V2X service-related configuration information for a vehicle UE having the EPS V2X function may include information as shown in Table <NUM> below.

After having generated the UE provisioning request message in step <NUM>, the V2X AS <NUM> according to an embodiment may transmit the request message to the NEF <NUM> by using the Nnef_UEProvisioningservice (step <NUM>).

When the V2X AS initially generates UE provisioning information for a new vehicle, the message in step <NUM> may be a "Nnef_UEProvisioning_Create" message. Alternatively, when the V2X AS updates previously generated UE provisioning information, the message in step <NUM> may be a "Nnef_UEProvisioning_Update" message.

The UE provisioning request message may include the "Transaction ID" identifying the AF request made by V2X AS, the service ID (e.g., network slice ID (e.g., S-NSSAI, etc.) defined for a V2X service) of the service provided by the V2X AS, the UE ID, the group ID of the group to which the UE belongs, and the like as described in Table <NUM>.

Further, the request message may include the V2X service configuration information as described in Tables <NUM>, <NUM>, <NUM>, and <NUM>.

On receiving the UE provisioning request message in step <NUM>, the NEF <NUM> may store the request message, received from the V2X AS <NUM>, in the UDR <NUM> when the request message in step <NUM> is a "Nnef_UEProvisioning_Create" or "Nnef_UEProvisioning_Update" message (step <NUM>). An example of the information which the NEF <NUM> stores in the UDR <NUM> is shown in Table <NUM> below.

After having received the UE provisioning request message in step <NUM>, the NEF <NUM> may delete information, the "Data Key" of which matches the "AF Transaction Id" included in the request message, from the information stored in the UDR <NUM> when the request message in step <NUM> is a "Nnef_UEProvisioning_Delete".

After having stored the V2X AS request message in the UDR <NUM> in step <NUM>, the NEF <NUM> may transmit, to the V2XAS <NUM>, a UE provisioning response message which notifies the V2X AS <NUM> that the UE provisioning request message has been processed (step <NUM>).

After having stored the V2X request information in step <NUM>, the UDR <NUM> may check the service ID (Service Description) included in the V2X AS request information to determine that the request message is a V2X service provisioning request for a V2X service, and may select the PCF responsible for management of V2X service policy information (step <NUM>). The service ID, the UE ID, etc. may be considered in the PCF selection.

The UDR <NUM> may transmit a "Nudr_DM_Notify" message to the PCF selected in step <NUM> (step <NUM>). The "Nudr_DM_Notify" message may include the UE ID (e.g., SUPI) and the like.

On receiving the "Nudr_DM_Notify" message in step <NUM>, the PCF <NUM> may check the message to determine whether UE provisioning is needed (step <NUM>). When the UE provisioning is needed, the PCF <NUM> may select the serving AMF to which the UE indicated by the UE ID in the message is currently connected (step <NUM>). A specific method for selecting the AMF may follow the procedure illustrated in <FIG> or <FIG>.

The PCF <NUM> may transmit a "Namf_Communication_N1N2Message Transfer" message to the AMF selected in step <NUM> (step <NUM>). The "Namf_Communication_N1N2Message Transfer" message may include the V2X service configuration information generated by the V2X AS in step <NUM> and transmitted to the NEF <NUM> in step <NUM>.

On receiving the "Namf_Communication _N1N2Message Transfer" message, the AMF <NUM> may transmit the corresponding message to the UE <NUM> (step <NUM>).

On receiving the UE provisioning information message in step <NUM>, the UE <NUM> may store therein the V2X service configuration information included in the message, and may use the corresponding configuration information for the V2X service.

If the provisioning information is not successfully transmitted to the UE due to the unreachability of the UE in step <NUM>, the AMF <NUM> may notify the PCF <NUM> that the UE policy container delivery is unsuccessful. On receiving the message indicating that the UE provisioning information delivery is unsuccessful, the PCF <NUM> may subscribe to a UE reachability event according to the procedure illustrated in <FIG> (step <NUM> to step <NUM> of <FIG>). As illustrated in <FIG>, if the UE becomes reachable (step 1c of <FIG>), the AMF <NUM>, <NUM> may notify the PCF <NUM>, <NUM> that the UE becomes reachable (step 2b of <FIG>). On receiving the message in step 2b of <FIG> from the AMF <NUM>, <NUM>, the PCF <NUM>, <NUM> may reattempt to deliver the UE provisioning information by transmitting the message in step <NUM> of <FIG> to the AMF <NUM>, <NUM> (step <NUM> to step <NUM> of <FIG>).

Further, when desiring to delete previously generated UE provisioning information, the V2X AS <NUM> according to an embodiment may transmit a "Nnef_UEProvisioning_Delete" message as the message in step <NUM> of <FIG>. On receiving the "Nnef_UEProvisioning_Delete" message, the NEF <NUM> may delete the existing stored UE provisioning information in step <NUM>.

<FIG> illustrates an AMF selection procedure according to an embodiment.

Step <NUM> of <FIG> may correspond to step <NUM> of <FIG>. On receiving the "Nudr_DM_Notify" message from the UDR <NUM> in step <NUM> of <FIG>, the PCF <NUM> may transmit a UE location information request message to the UDM <NUM> in order to discover the serving AMF of the UE (step <NUM>). The UE location information request message may include the UE ID (e.g., SUPI or the like). Further, the UE location information request message may include the NF type to be discovered by the PCF <NUM>. According to an embodiment, the NF type may be AMF.

On receiving the UE location information request message, the UDM <NUM> may discover serving AMF information of the UE corresponding to the UE ID included in the request message. The UDM <NUM> may transmit a UE location information response message back to the PCF <NUM> in response to the UE location information request message received in step <NUM> (step <NUM>). The UE location information response message may include the serving AMF information of the UE.

On receiving the UE location information response message, the PCF <NUM> may transmit a "Namf_Communication_N1N2MessageTransfer" message to the serving AMF included in the response message (step <NUM>). Step <NUM> of <FIG> may correspond to step <NUM> of <FIG>.

In order to access a <NUM> network and use a V2X service, a vehicle UE according to an embodiment may perform a UE registration procedure as shown in <FIG>. The serving AMF of the UE may be determined in the process of performing the UE registration procedure, and the serving AMF <NUM> may perform policy association establishment with the PCF <NUM> (step <NUM> of <FIG> or step <NUM> of <FIG>).

Step <NUM> of <FIG> may correspond to step <NUM> of <FIG>. On receiving a "Nudr_DM_Notify" message from the UDR <NUM> in step <NUM> of <FIG>, the PCF <NUM> may transmit a "Namf_Communication_N1N2MessageTransfer" message to the AMF <NUM> with which policy association establishment has been completed in the previous UE registration procedure (step <NUM>). Step <NUM> of <FIG> may correspond to step <NUM> of <FIG>.

A <NUM> system according to an embodiment may provide a UE reachability event. An example of the UE reachability event provided by the <NUM> system according to an embodiment is shown in Table <NUM> below.

Referring to Table <NUM> showing an example of the event, when the UE transitions to a "CM-CONNECTED" state, the <NUM> system may notify a network entity (e.g., PCF, AF, or the like) having subscribed to the UE reachability event that the UE becomes reachable for data transmission.

<FIG> illustrates a procedure in which an application server (V2X AS) subscribes to a UE reachability event of a UE according to an embodiment.

The V2X AS <NUM> according to an embodiment may determine whether to subscribe to a UE reachability event of a UE in order to determine when to transmit data to the UE (step <NUM>).

The V2X AS <NUM> may transmit a "Nnef_EventExposure_Subscribe" request message to the NEF <NUM> (step <NUM>). In order to indicate that the V2X AS <NUM> desires to subscribe to a UE reachability event of a specific UE, the "Nnef_EventExposure_Subscribe" request message may include the event ID indicating the UE reachability and the UE ID of the corresponding UE.

On receiving the "Nnef_EventExposure_Subscribe" request message, the NEF <NUM> may verify whether the V2X AS <NUM> is eligible to subscribe to the UE reachability event. Further, in order to process the event subscription request according to the corresponding message, the NEF <NUM> may transmit a "Nudm_EventExposure_Subscribe" request message to the UDM <NUM> (step <NUM>).

On receiving the "Nudm_EventExposure_Subscribe" request message, the UDM <NUM> may verify whether the V2X AS <NUM> or the NEF <NUM> is eligible to subscribe to the UE reachability event. If it is determined that the V2X AS <NUM> or the NEF <NUM> is eligible to subscribe to the UE reachability event, the UDM <NUM> may set the URRP-AMF parameter to "set", and may transmit a "Namf_EventExposure_Subscribe" request message to the AMF <NUM> in order to process the event subscription request according to the corresponding message (step <NUM>).

On receiving the "Namf_EventExposure_Subscribe" request message, the AMF <NUM> may determine whether the network entity requesting the event is eligible to subscribe to the UE reachability event. If it is determined that the network entity is eligible to subscribe to the UE reachability event, the AMF <NUM> may set the URRP-AMF parameter to "set" (step <NUM>).

In order to notify the V2X AS <NUM> that the event subscription request message transmitted by the V2X AS <NUM> in step <NUM> has been successfully processed, the AMF <NUM>, the UDM <NUM>, and the NEF <NUM> may transmit response messages back to the UDM <NUM>, the NEF <NUM>, and the V2X AS <NUM>, respectively (step <NUM>, step <NUM>, and step <NUM>).

The V2X AS according to an embodiment may simultaneously perform the UE provisioning procedure illustrated in <FIG> and the UE reachability event subscription event illustrated in <FIG>. For example, the V2X AS <NUM>, <NUM> may generate V2X service configuration information for a new vehicle UE <NUM> (step <NUM> of <FIG>), and may transmit a "Nnef_UEProvisioning" request message to the NEF <NUM> in order to provision the V2X service configuration information to the UE (step <NUM> of <FIG>), as illustrated in <FIG>. At the same time, the V2X AS <NUM>, <NUM> may determine to subscribe to a UE reachability event of the new vehicle UE (step <NUM> of <FIG>), and may transmit a "Nnef_EventExposure_Subscribe" request message to the NEF <NUM> (step <NUM> of <FIG>).

<FIG> illustrates a procedure in which a PCF subscribes to a UE reachability event of a UE according to an embodiment.

The PCF <NUM> according to an embodiment may determine whether to subscribe to a UE reachability event of a UE in order to determine when to transmit data to the UE (step <NUM>).

In contrast to the procedure of <FIG>, the PCF <NUM> may transmit a "Namf_EventExposure_Subscribe" request message to the AMF <NUM> directly, not via the NEF (step <NUM>).

In order to notify the PCF <NUM> that the event subscription request message transmitted by the PCF <NUM> has been successfully processed, the AMF <NUM> may transmit a response message back to the PCF <NUM> (step <NUM>).

The PCF according to an embodiment may perform the UE reachability event subscription procedure illustrated in <FIG> in the process of performing the UE provisioning procedure illustrated in <FIG>. For example, on receiving the "Nudr_DM_Notify" message from the UDR <NUM> in step <NUM> of <FIG>, the PCF <NUM>, <NUM> may determine to subscribe to a UE reachability event of the corresponding UE (step <NUM> of <FIG>), and may transmit the "Namf_EventExposure_Subscribe" request message to the AMF <NUM> (step <NUM> of <FIG>).

<FIG> illustrates a procedure in which an AMF detects and notifies a UE reachability event according to an embodiment.

The AMF <NUM> according to an embodiment may receive an NAS signaling message (e.g., Registration Request message, Service Request message, or the like) from the UE <NUM>. If the NAS signaling message is received from the UE <NUM> which is in a "CM-IDLE" state, the AMF <NUM> may transition the state of the UE from "CM-IDLE" to "CM-CONNECTED". Further, on detecting that the UE becomes reachable, the AMF <NUM> may transition the reachability state of the UE from "unreachable" to "reachable" (step 1c).

If the URRP-AMF is set to "set" in the AMF <NUM> according to an embodiment, the AMF may perform a "Namf_EventExposure_Notify" service. The "Namf_EventExposure_Notify" message may include the UE ID (e.g., SUPI) of the UE and the reachability state information (e.g., UE_Reachable) of the UE.

More specifically, as an example, when the V2X AS <NUM>, <NUM> requests the AMF <NUM>, <NUM> for the UE reachability event subscription according to the procedure illustrated in <FIG>, the AMF <NUM>, <NUM> may notify the V2X AS that the UE now becomes reachable, according to the procedure in step 2a.

As another example, when the PCF <NUM>, <NUM> requests the AMF <NUM>, <NUM> for the UE reachability event subscription according to the procedure illustrated in <FIG>, the AMF <NUM>, <NUM> may notify the PCF that the UE now becomes reachable, according to the procedure in step 2b.

On transmitting the "Namf_EventExposure_Notify" message according to the procedure in step 2a or 2b, the AMF <NUM>, <NUM> may set the URRP-AMF configured for the corresponding UE to "not set".

On receiving the "Namf_EventExposure_Notify" message in step 2a, the V2X AS <NUM> can recognize that the UE <NUM> now becomes reachable and thus data can be transmitted to the UE <NUM>. Accordingly, the V2X AS <NUM> may transmit the V2X service configuration information to the UE <NUM> (step 3a). The procedure in which the V2X AS <NUM> transmits the V2X service configuration information may follow the UE provisioning procedure illustrated in <FIG>. For example, on receiving the message in step 2a of <FIG>, the V2X AS <NUM> may transmit the message in step <NUM> of the <FIG> in order to transmit the V2X service configuration information to the UE <NUM>. The message in step <NUM> of <FIG> may be a "Nnef_UEProvisioning_Create" or "Nnef_UEProvisioning_Update" message.

On receiving the "Namf_EventExposure_Notify" message in step 2b, the PCF <NUM> can recognize that the UE <NUM> now becomes reachable and thus data can be transmitted to the UE <NUM>. Accordingly, the PCF <NUM> may transmit the V2X service configuration information to the UE <NUM> (step 3b). In order to transmit the V2X service configuration information to the UE <NUM>, the PCF <NUM> may perform the procedure of <FIG>, starting from step <NUM>. For example, on receiving the message in step 2b of <FIG>, the PCF <NUM> may transmit the message in step <NUM> of the <FIG> in order to transmit the V2X service configuration information to the UE <NUM>.

<FIG> illustrates a procedure of registering a vehicle UE with a <NUM> network according to an embodiment.

Referring to <FIG>, the vehicle UE <NUM> according to an embodiment may transmit a registration request message (step <NUM>). On receiving the registration request message, the base station <NUM> may select an AMF to which the registration request message is delivered (step <NUM>). The base station <NUM> may transmit the registration request message, received from the UE <NUM>, to the AMF <NUM> (step <NUM>). On receiving the registration request message, the AMF <NUM> may select a UDM (step <NUM>). The AMF <NUM> may acquire the subscription information of the UE from the selected UDM <NUM> (step <NUM> and step <NUM>). The AMF <NUM> may transmit an event subscription to the selected UDM <NUM> (step <NUM>). The AMF <NUM> may select a PCF (step <NUM>). The AMF <NUM> may perform policy association establishment with the selected PCF <NUM> (step <NUM>). The AMF <NUM> may transmit a registration response message back to the UE <NUM> in response to the registration request message received in step <NUM> (step <NUM>).

According to an embodiment, the registration request message in step <NUM> of <FIG> may be one example of the message in step 1a of <FIG>. For example, on receiving the registration request message in step <NUM> of <FIG>, the AMF <NUM>, <NUM> may perform the procedure of <FIG>, starting from step <NUM>, and at the same time, may perform the procedure of <FIG>, starting from step 1c.

The UE <NUM> according to an embodiment may include PII, which is the version information of the V2X service configuration information stored in the UE, in the registration request message in step <NUM> of <FIG>.

The AMF <NUM> according to an embodiment may acquire the subscription information of the UE from the UDM <NUM> in step <NUM> or step <NUM> of <FIG>, and the subscription information may include an indication whether the UE has subscribed to the V2X service. For example, if the subscription information includes slice information used for V2X (e.g., S-NSSAI defined for V2X), the AMF <NUM> may determine that the UE <NUM> has subscribed to the V2X service. If the UE <NUM> has subscribed to the V2X service, the AMF <NUM> may select a PCF <NUM>, which provides policy management for the V2X service, in step <NUM> of <FIG>, and may perform policy association establishment with the PCF <NUM> in step <NUM> of <FIG>. The AMF <NUM> may provide the PII, which is the version information of the V2X service configuration information included in the registration request message received from the UE <NUM> in step <NUM> of <FIG>, to the PCF <NUM> in step <NUM> of <FIG>. Step <NUM> of <FIG> may correspond to step <NUM> of <FIG>.

On completing the policy association establishment with the AMF <NUM> according to an embodiment, the PCF <NUM> may compare the PII received in step <NUM> of <FIG>, which is the version information of the V2X service configuration information transmitted by the UE <NUM>, with the PII which is the version information of the latest V2X service configuration information stored in the UDR. If the PII which is the version information of the V2X service configuration information transmitted by the UE <NUM> is not the latest version, the PCF <NUM> may perform the procedure in step <NUM> of <FIG>. The PCF <NUM>, <NUM> should select an AMF in the process of performing the procedure in step <NUM> of <FIG>, and may select the AMF <NUM> with which the policy association establishment has been completed in step <NUM> of <FIG>. The PCF <NUM> may transmit the "Namf_Communication_N1N2MessageTransfer" message to the AMF <NUM>, <NUM> with which the policy association establishment has been completed in step <NUM> of <FIG> (step <NUM> of <FIG>). The "Namf_Communication_N1N2MessageTransfer" message may include the latest V2X service configuration information stored in the UDR <NUM>. Further, the "Namf_Communication_N1N2MessageTransfer" message may include the PII which is the version information of the V2X service configuration information.

Further, on completing the policy association establishment with the AMF <NUM> according to an embodiment, the PCF <NUM> may transmit the "Nudr_DM_Subscribe" message to the UDR <NUM> after step <NUM> of <FIG> so as to subscribe to an event provided by the UDR <NUM> (step <NUM> of <FIG>).

If the event in which the V2X service configuration information is stored occurs in step <NUM> of <FIG>, the UDR <NUM> may transmit a "Nudr_DM_Notify" notification message to the PCF <NUM> which has subscribed to the event in step <NUM> of <FIG> (step <NUM> of <FIG>).

On receiving the "Nudr_DM_Notify" notification message from the UDR <NUM> according to an embodiment, the PCF <NUM> may transmit a "Namf_Communication_N1N2MessageTransfer" message to the AMF <NUM>, <NUM> with which the policy association establishment has been completed in step <NUM> of <FIG> (step <NUM> of <FIG>). The "Namf_Communication_N1N2MessageTransfer" message may include the V2X service configuration information transmitted by the V2X AS <NUM> in step <NUM> of <FIG> and stored in the UDR <NUM> in step <NUM> of <FIG>. Further, the "Namf_Communication_N1N2MessageTransfer" message may include the PII which is the version information of the V2X service configuration information.

The UE <NUM> according to an embodiment may receive the UE provisioning information in step <NUM> of <FIG>. The UE <NUM> may compare the PII, which is the version information of the V2X service configuration information received in step <NUM> of <FIG>, with the PII which is the version information of the V2X service configuration information stored in the UE. If the versions according to the two PIIs are different, the UE <NUM> may store the V2X service configuration information received in step <NUM> of <FIG>, instead of the V2X service configuration information already stored in the UE. Further, in addition to the V2X service configuration information, the UE <NUM> may store the PII information corresponding to the V2X service configuration information together.

<FIG> illustrates a block diagram of a configuration of a UE according to an embodiment.

A UE according to an embodiment may include a transceiver <NUM> and a controller <NUM> for controlling the overall operation of the UE. Further, the transceiver <NUM> may include a transmitter <NUM> and a receiver <NUM>.

The transceiver <NUM> may transmit and receive signals to and from other network entities.

The controller <NUM> may perform control such that the UE performs one of the operations according to the above embodiments. The controller <NUM> and the transceiver <NUM> do not need to be necessarily implemented as sperate modules, but of course may be implemented as one constituent unit such as a single chip. Further, the controller <NUM> may be electrically connected to the transceiver <NUM>. Further, for example, the controller <NUM> may be a circuit, an application-specific circuit, or at least one processor. Further, operations of the UE may be achieved by providing a memory device, in which corresponding program codes are stored, in any constituent unit of the UE.

<FIG> illustrates a block diagram of a configuration of a network entity according to an embodiment.

A network entity according to an embodiment may include a transceiver <NUM> and a controller <NUM> for controlling the overall operation of the network entity. Further, the transceiver <NUM> may include a transmitter <NUM> and a receiver <NUM>.

The controller <NUM> may perform control such that the network entity performs one of the operations according to the above embodiments. The controller <NUM> and the transceiver <NUM> do not need to be necessarily implemented as sperate modules, but of course may be implemented as one constituent unit such as a single chip. Further, the controller <NUM> may be electrically connected to the transceiver <NUM>. Further, for example, the controller <NUM> may be a circuit, an application-specific circuit, or at least one processor. Further, operations of the network entity may be achieved by providing a memory device, in which corresponding program codes are stored, in any constituent unit of the network entity.

It should be noted that the configuration views illustrated in <FIG>, the views illustrating the control/data signal transmission methods, the views illustrating the operation procedures, and the other configuration views are not intended to limit the protection scope of the disclosure. That is, all the constituent units, entities, or operation steps described and shown in the above drawings should not construed as elements essential for implementing the disclosure, and even when only some of the elements are included, the disclosure may be implemented without departing from the scope of the disclosure.

The above described operations of the base station or UE may be implemented by providing a memory device, in which corresponding program codes are stored, in any constituent unit of the base station or UE apparatus. That is, the controller of the base station or UE may perform the above described operations by reading and executing the program codes stored in the memory device by means of a processor or a central processing unit (CPU).

Various constituent units, modules, and the like of the entity, the base station apparatus, or the UE apparatus may also be operated using a hardware circuit, for example, a complementary metal oxide semiconductor-based logic circuit, firmware, software, and/or a combination of hardware and firmware and/or software embedded in a machine readable medium. As an example, various electric configurations and methods may be carried out using electric circuits such as transistors, logic gates, and application-specific integrated circuits (ASICs).

Claim 1:
A method performed by a device for performing a network exposure function, NEF (<NUM>), in a fifth-generation, <NUM>, communication system, the method comprising:
receiving (<NUM>), from a vehicle-to-everything, V2X, application server (<NUM>), a request message including request information, the request information comprising service description information, identification information for a user equipment, UE (<NUM>), an application function, AF, transaction identifier, and service parameters for provisioning to the UE (<NUM>) to support a V2X service; and
storing (<NUM>) data in a unified data repository, UDR (<NUM>), on the basis of the request information,
wherein the service parameters included in the request information received from the V2X application server (<NUM>) comprises:
in case the UE (<NUM>) is in coverage, information on a public land mobile network, PLMN, in which the UE (<NUM>) is authorized to perform the V2X communications and radio access technology, RAT, over which the UE (<NUM>) is authorized to perform the V2X communications in the PLMN, and
in case the UE (<NUM>) is out of coverage, information for indicating whether the UE (<NUM>) is authorized to perform V2X communications.