WO2014166294A1

WO2014166294A1 - Proximity service server selection method and apparatus, and user registration method and apparatus

Info

Publication number: WO2014166294A1
Application number: PCT/CN2013/091225
Authority: WO
Inventors: 王静; 宗在峰
Original assignee: 中兴通讯股份有限公司
Priority date: 2013-04-11
Filing date: 2013-12-31
Publication date: 2014-10-16
Also published as: CN104105086B; CN104105086A

Abstract

Disclosed are a proximity service server selection method and apparatus, and a user registration method and apparatus. The method comprises: when a home subscriber server (HSS) sends subscription information, the HSS sending, to a mobility management entity (MME), proximity service server identifier information and capability information that a user performs subscription to authorize use of a proximity service, the proximity service server identifier information and the capability information being carried in the subscription information; and the MME selecting a proximity service server according to the proximity service server identifier information obtained in the subscription information or configured. A selection unit is configured to select a proximity service server according to the proximity service server identifier information obtained in the subscription information or configured in the selection unit. By using the present invention, for a problem of how a proximity service server manages a user, and a problem of how to coordinate operation between an application server using a proximity service and a network after the proximity service server is introduced, a specific implementation solution is provided.

Description

Method and device for selecting adjacent service server, user registration method and device

The present invention relates to a proximity service technology between users in the field of mobile communications, and in particular, to a method and apparatus for selecting a proximity service server, and a registration method and apparatus for a user to an adjacent service server. Background technique

In order to maintain the competitiveness of the third-generation mobile communication system in the field of communication, to provide users with faster, less delayed, and more personalized mobile communication services, while reducing operators' operating costs, third-generation cooperation The Standards Working Group of the 3GPP (3rd Generation Partnership Project) has been working on the Evolved Packet System (EPS). FIG. 1 is a schematic structural diagram of an evolved packet domain system. In FIG. 1, the entire EPS system is divided into two parts: a radio access network and a core network. In the core network, the home subscriber server (HSS), the mobility management entity (MME, Mobility Management Entity), the serving GPRS support node (SGSN), and the policy charging rule function (PCRF) are included. , Policy and Charging Rule Function ), Service Gateway (S-GW, Serving Gateway), Packet Data Gateway (P-GW, PDN Gateway) and Packet Data Network (PDN). The functions of each part are described in detail below: HSS, which is the permanent storage location of user subscription data, is located in the home network to which the user subscribes.

The MME is the location where the subscriber subscription data is stored in the current network, and is responsible for terminal-to-network non-access stratum signaling management, terminal security verification function, terminal mobility management, user idle mode tracking and paging management functions, and Bearer management.

SGSN is the GSM (Enhanced Data Rate for GSM Evolution) Radio Access Network (GSM, GSM EDGE Radio Access Network). UMTS (Universal Mobile Telecommunications System) UMTS (UTTS, UMTS Terrestrial Radio Access Network) users access the core network's service support point, similar to the mobility management entity, responsible for the user's location Features such as update, paging management, and bearer management.

S-GW, which is the gateway of the core network to the wireless system, is responsible for the user plane bearer of the terminal to the core network, the data buffer in the terminal idle mode, the function of initiating the service request by the network side, the lawful interception and the packet data routing and forwarding function; The gateway is responsible for counting the situation in which the user terminal uses the wireless network, and generates the CDRs of the terminal using the wireless network, and transmits the CDRs to the charging gateway.

P-GW, which is the gateway of the evolved system and the external packet data network of the system, which is connected to the Internet and the packet data network, and is responsible for the Internet Protocol (IP) address allocation, charging function, packet filtering, and Features such as policy control.

The PDN is the carrier's IP service network, which provides IP services to users through the carrier's core network.

The PCRF is a server in the evolution system that provides rules for charging control, online credit control, threshold control, and quality of service (QoS) policies.

The radio access network is composed of an evolved base station (eNB, Evolved NodeB) and a 3G radio network controller (RNC, Radio Network Controllor), which is mainly responsible for transmitting and receiving wireless signals, and communicating with the terminal through the air interface to manage the wireless of the air interface. Resources, resource scheduling, and access control.

The service GPRS support node is an upgraded SGSN, which can support the S4 interface with the service gateway, and communicates with the mobility management unit by using GPRS Tunneling Protocol version 2 (GTPv2). For the SGSN supporting the 3G core network, the packet switching (PS, Packet Switching) domain network architecture is different from that of FIG. At this time, the SGSN and the MME are connected by using a Gn interface, and the interworking uses GPRS Tunneling Protocol version 1 (GTPvl, GPRS Tunneling Protocol version 1). The SGSN cannot be connected to the service gateway. The Gn interface is connected to the Gateway GPRS Support Node (GGSN, Gateway GPRS Support Node) to directly access the packet data network.

In the R12 phase of the 3GPP standard, some European and American equipment and operators, based on the requirements of national regulations, believe that public safety functions that can communicate directly between devices in a mobile communication network are needed. The public safety function is mainly used in the event that the wireless access is interrupted due to a disaster, and communication between devices is required to complete the rescue work. This requirement was discussed in the 3GPP standards organization. The application scenarios for direct inter-device connectivity have been extended during the discussion, enabling this feature to serve applications in the commercial domain. For example, when two users use the social network application, if the distance between the two users is close enough, the data can be transmitted through the direct connection between the devices, and the data is not required to be routed through the upper layer network, thereby reducing the load on the network. Increased data transmission efficiency. In addition, this function can also be used to complete commercial application advertisements, friend discovery, information delivery, etc., which enables network operators to better support user applications, and the experience of users and service operators is better, thereby further bringing economy. benefit.

Based on the EPS mobile communication network, a dedicated control network element, Prose Server (Proximity Service Server), is added to the network in order to meet the requirements of the proximity service between the users, as shown in Figure 2. Prose Server has the function of authorizing whether to allow the use of the adjacent service. The authorization is to control the user's discovery operation and communication establishment through the Sxl interface, and interact with the application through the Sx3 interface to support application-level business functions. Prose Server can carry direct messages to and from the UE through the user plane of the Sx2 interface. This interface is optional.

At present, there are no specific implementation plans for the management of users of Prose Server (such as selecting Prose Server, based on the user-selected Prose Server to accept user registration and then managing users), and using Prose Server to use adjacent services. The problem of how to work together between the application server (APP Server) and the network needs to be clarified. Summary of the invention

To solve the above problem, an embodiment of the present invention provides a method and device for selecting a proximity service server, a user registration method, and a device.

A method for selecting a proximity service server, the method comprising:

The home subscriber server HSS, when transmitting the subscription information, sends the proximity service server identification information carried in the subscription information, and the capability information of the user subscription authorization to use the proximity service to the mobility management entity MME;

The MME selects the proximity service server according to the proximity service server identification information obtained or configured in the subscription information.

The proximity service server identification information includes: at least one of a name of the proximity service server, an identifier of the proximity service server, an access point name of the proximity service server, and an address of the proximity service server.

The capability information of the user subscription to use the proximity service includes: the capability of the different operator network to authorize the use of the proximity service, and the permission/disallowment of at least one of the information discovered by one operator network user or the discovered information.

A device for selecting a service server, the device comprising: a first receiving unit and a selecting unit on the MME side;

The first receiving unit is configured to receive the proximity service server identifier information carried in the subscription information sent by the HSS, and the capability information of the user signing the authorized use of the proximity service;

The selecting unit is configured to select the proximity service server according to the proximity service server identification information obtained in the subscription information or configured by itself.

The first receiving unit and the selection unit, when performing the processing, the central processor may be used (CPU, Central Processing Unit), a digital signal processor (DSP, Digital Signal Processor) or a programmable intermixed mutli bad ¹ J (FPGA, Field - Programmable Gate Array) implementation. The proximity service server identification information includes: at least one of a name of the proximity service server, an identifier of the proximity service server, an access point name of the proximity service server, and an address of the proximity service server.

A registration method for a user to an adjacent service server, the method comprising:

The MME sends, by using the registration/update message, the user identifier, the MME identity attached to the user, and the capability information of the user subscription authorization using the adjacent service to the proximity server selected based on the identifier information of the proximity service server;

The proximity service server allocates or updates the proximity service identifier Prose ID to the user, and sends the Prose ID to the MME, and the MME sends the Prose ID and/or the adjacent service server identifier Prose Server ID to the UE through the downlink non-access stratum NAS message.

The method further includes: deleting, by the MME, the user context information saved on the neighboring service server, and the MME deleting the neighboring service information of the UE by using the downlink NAS message.

The method further includes: when receiving the message of allocating/updating/deleting the Prose ID, the UE registers/updates/deletes the binding relationship of the application layer ID, the Prose ID, and the Prose Server ID on the application server.

The Prose ID is an identifier for identifying a user in a proximity service discovery or communication process.

The user context information saved on the adjacent service server includes at least one of an MME identifier attached by the user, capability information of the user authorized to use the adjacent service, Prose ID, and proximity service discovery information.

The downlink NAS message includes: an attach accept message sent by the MME to the UE, Tracking area update accept message, any one of the newly defined Prose ID assignment messages. The triggering condition that the MME sends the registration/update message to the neighboring service server is: the user attaches to the network, or the MME accessed by the user changes, or the user in the subscription information subscribes to authorize the use of the adjacent service. The information has changed.

The triggering condition that the MME sends the logout message to the neighboring service server is: the user detaches from the network, or the network no longer authorizes the user to use the adjacent service.

The method further includes: when the MME serving the user changes, the new MME needs to obtain the proximity service server identifier information in the old MME, and the new MME signs the MME identity and the user attached by the user by using the registration/update message. The capability information authorized to use the adjacent service is sent to the proximity service server.

The method further includes: deleting, by the logout message, the user context information saved on the adjacent service server, and deactivating the UE by using an attach accept message, a tracking area update accept message, a logout request/accept message, and a defined Prose ID delete message. Adjacent services, delete information about adjacent services in the UE.

a registration device for a user to an adjacent service server, the device includes: a second receiving unit located adjacent to the service server side, and a first registration and distribution unit;

The second receiving unit is configured to receive a user identifier that is sent by the MME by using a registration/update message, an MME identifier that is attached to the user, and capability information that the user subscribes to use the adjacent service; the first registration and allocation unit is configured to provide the user The Prose ID is sent or updated to the MME, and the Prose ID is sent to the MME to notify the MME to send the Prose ID and/or the Prose Server ID to the UE through the downlink NAS message to complete registration with the neighboring service server.

The second receiving unit and the first registration and allocating unit may use a central processing unit (CPU), a digital signal processor (DSP), or a programmable array when performing processing.歹' J (FPGA, Field - Programmable Gate Array) implementation. The second receiving unit is further configured to receive the logout message sent by the MME. The device further includes: a first unregistering unit, configured to delete the user context information saved on the adjacent service server after receiving the logout message, and notify The MME deletes the proximity service information of the UE by using the downlink NAS message.

The first unregistering unit is further configured to: after deleting the user context information saved on the adjacent service server, notify the MME to delete the message by using an attach accept message, a tracking area update accept message, a logout request/accept message, and a defined Prose ID message. The neighboring service of the UE is deactivated, and information about the adjacent service in the UE is deleted.

The second receiving unit is further configured to: when the MME serving the user changes, and the new MME needs to obtain the neighboring service server identifier information in the old MME, the new MME receives the user by registering/updating the message. The attached MME identity, the user's subscription authority to use the capability information of the adjacent service.

The UE sends a registration message to the neighboring service server selected by the proximity service server identification information according to the pre-configuration or the proximity service server identifier information sent by the network, where the registration message carries the user identifier;

The proximity service server assigns or updates the Prose ID to the user and sends the Prose ID to the UE. The method further includes: the neighboring service server deletes the proximity service information of the UE by using the direct interface.

The method further includes: the MME selecting the proximity service server according to the Prose Server ID of the subscription information in the HSS, and notifying the UE by using the NAS message.

The direct interface carries a control plane interface on the user plane. The NAS message includes: any one of an attach accept message, a tracking area update accept message, and a newly defined Prose ID assignment message.

A device for registering a user to an adjacent service server, the device comprising: the device comprising: a third receiving unit located adjacent to the service server side, and a second registration and assigning unit;

The third receiving unit is configured to receive a registration message that is sent by the UE according to the pre-configured or the neighboring service server identifier information sent by the network, and the registration message carries the user identifier.

The second registration and allocation unit is configured to allocate or update a Prose ID to the user, send the Prose ID to the UE, and notify the UE to complete registration to the adjacent service server.

The third receiving unit and the second registration assigning unit may use a central processing unit (CPU), a digital signal processor (DSP), or a programmable array when performing processing.歹¹ J (FPGA, Field - Programmable Gate Array) implementation.

The device further includes: a second unregistering unit, configured to notify the UE to delete the proximity service information of the UE by using the direct interface.

The direct interface carries a control plane interface on the user plane.

When transmitting the subscription information, the HSS of the method of the embodiment of the present invention sends the proximity service server identification information carried in the subscription information and the capability information of the user subscription authorization to use the adjacent service to the MME; the MME obtains or configures according to the subscription information. The adjacent service server identification information is selected to be adjacent to the service server. With the embodiment of the present invention, a clear specific implementation scheme is provided for how the proximity service server implements the management of the user and how the application server and the network using the adjacent service are used after the proximity of the service server. DRAWINGS

1 is a schematic structural diagram of an existing evolved packet domain system;

2 is a schematic diagram of a network architecture existing to support adjacent service functions; 3 is a schematic diagram of an implementation process of Embodiment 1 of the present invention;

4 is a schematic diagram of an implementation process of Embodiment 2 of the present invention;

FIG. 5 is a schematic diagram of an implementation process of Embodiment 3 of the present invention; FIG.

6 is a schematic diagram of an implementation process of Embodiment 4 of the present invention;

7 is a schematic diagram of an implementation process of Embodiment 5 of the present invention;

8 is a schematic diagram of an implementation process of Embodiment 6 of the present invention;

9 is a schematic diagram of an implementation process of Embodiment 7 of the present invention;

FIG. 10 is a schematic diagram of an implementation process of Embodiment 8 of the present invention. detailed description

The solution of the embodiment of the present invention is how to select Prose when the mobile network provides the user with the proximity service.

Server, based on the selected Prose Server implementation registration and identity binding solution, first solved how to select Prose Server, user registration to Prose Server function and complete application layer identification, network layer identification, Prose Server binding on APP Server The problem is fixed so that Prose Server and APP Server can identify and address specific users, and can manage the specific users collaboratively if the license authorization allows.

It should be noted that: The proximity service server in this paper refers to Prose Server, and the application server or APP server refers to APP Server. The Prose Server ID information in this document refers to the Prose Server ID.

A selection method of Prose Server, which mainly includes the following contents;

A method for selecting a Prose Server includes: The HSS adds Prose Server identification information for the user service in the subscription data and capability information for the user to subscribe to use the adjacent service. The HSS sends the above information to the MME when sending the subscription information.

The MME selects Prose Server according to the Prose Server identification information obtained or configured in the contract.

Further, the Prose Server ID (Prose Server ID) includes: Prose Server Name, logo, access point name, address, etc.

Further, the capability information that the user subscribes to authorize the use of the adjacent service includes: the capability of the different operators to authorize the use of the adjacent service, the permission/prohibition of the information discovered by the network user of an operator, or the discovered information.

Further, the Prose Server selected by the MME may be sent to the UE through a non-access stratum (NAS) message.

The selecting device of the proximity service server includes: a first receiving unit and a selecting unit on the MME side; wherein, the first receiving unit is configured to receive the proximity service server identification information carried in the subscription information sent by the HSS, and the user signing authorized use The capability information of the proximity service; the selection unit is configured to select the proximity service server according to the proximity service server identification information obtained in the subscription information or configured by itself.

Here, the proximity service server identification information includes: at least one of a name of the proximity service server, an identifier of the proximity service server, an access point name of the proximity service server, and an address of the proximity service server.

Here, the capability information that the user subscribes to authorize the use of the proximity service includes: the capability of the different operator network to authorize the use of the proximity service, the permission/disallowment of at least one of the information discovered by one operator network user or the discovered information.

A user registration method to Prose Server, which mainly includes the following contents:

The first method included in the registration method of the user to the Prose Server is as follows: The MME sends the user identifier, the MME identifier attached to the user, and the capability information of the user authorized to use the adjacent service to the Prose server based identification information by using the registration/update message. The Prose Server. The Prose Server assigns or updates the Prose ID to the user and sends the Prose ID to the MME. The MME sends the Prose ID and/or Prose Server ID to the UE through the downlink NAS message.

Further, the MME can delete the user context information saved on the Prose Server by using the logout message. The MME deletes the proximity service information of the UE by using the downlink NAS message. Further, when receiving the message of allocating/updating/deleting the Prose ID, the UE registers/updates/deletes the binding relationship of the application layer ID, the Prose ID, and the Prose Server ID on the APP Server.

Further, the Prose ID is an identifier for identifying a user in the process of proximity service discovery or communication.

Further, the NAS message sent by the MME to the UE includes an attach accept, a tracking area update accept, a newly defined Prose ID assignment message, and the like.

Further, the Prose Server ID includes the name, identity, access point name, address, etc. of the Prose Server.

Further, the MME initiates registration/update to the Prose Server on the premise that the user attaches to the network or the MME accessed by the user changes or the capability information of the user authorized in the subscription to use the adjacent service changes.

Further, when the MME serving the user changes, the new MME needs to obtain the Prose Server identification information in the old MME. The new MME sends the MME identity attached by the user and the capability information of the user authorized to use the proximity service to the selected Prose Server through the registration/update message.

Further, the MME may delete the user context information saved on the Prose Server by using the logout message, and activate the adjacent service function of the UE by using the attach accept, the tracking area update accept, the logout request/accept message, and the defined Prose ID delete message, and delete the UE. Information about the adjacent service, including deleting the Prose ID in the UE.

Further, the MME initiates the logout on the premise that the user detaches from the network or the network no longer authorizes the user to use the function of the adjacent service.

Further, the user context information saved on the Prose Server includes the MME identifier attached to the user, the capability information of the user authorized to use the proximity service, the Prose ID, and the proximity service discovery information.

Further, the proximity service information on the UE side includes a Prose ID, a discovery, or a communication result. Corresponding wireless resource allocation information.

A registration device of the user to the Prose Server includes: a second receiving unit located adjacent to the service server side, and a first registration allocation unit; wherein the second receiving unit is configured to receive the user identifier and the user sent by the MME by using the registration/update message The attached MME identifier, the user subscription authority to use the capability information of the adjacent service; the first registration allocation unit is configured to allocate or update the neighboring Prose ID to the user, send the Prose ID to the MME, and notify the MME to set the Prose ID and/or the Prose Server ID. The downlink NAS message is sent to the UE to complete registration to the adjacent service server.

Here, the second receiving unit is further configured to receive a logout message sent by the MME;

The device further includes: a first logout unit configured to: after receiving the logout message, delete the user context information saved on the near service server, and notify the MME to delete the proximity service information of the UE by using the downlink NAS message.

Here, the first logout unit is further configured to: after deleting the user context information saved on the adjacent service server, notify the MME to activate the UE by using an attach accept message, a tracking area update accept message, a logout request/accept message, and a defined Prose ID delete message. The adjacent service deletes the information about the adjacent service in the UE.

Here, the second receiving unit is further configured to: when the MME serving the user changes, the new MME needs to obtain the proximity service server identification information in the old MME, and the new MME receives the user attached by the registration/update message. The MME identity and user subscription authorization use the capability information of the adjacent service.

A second method for the registration method of the user to the Prose Server is as follows: The UE initiates registration with the Prose Server selected by the Prose Server identification information according to the pre-configuration or the Prose Server identification information sent by the network, and the registration message carries the registration message. User ID.

Prose Server assigns or updates the Prose ID to the user and sends the Prose ID to the UE.

Further, the Prose Server can be deleted as a user by using a direct interface with the UE. Business information.

Further, when receiving the message of allocating/updating/deleting the Prose ID, the UE registers/updates/deletes the binding relationship of the application layer ID, the Prose ID, and the Prose Server ID on the APP Server.

Further, the network can configure the Prose Server ID for the UE through the ANDSF server. Further, the MME may select Prose according to the Prose Server ID signed in the HSS.

Server, notifies the UE through a NAS message.

Further, the direct interface is a control plane interface carried on the user plane.

Further, the NAS message includes an attach accept, a routing area update accept, a newly defined Prose

ID assignment message, etc.

Further, the proximity service information of the UE side includes: a Prose ID, a discovery or communication result, and corresponding radio resource allocation information.

A registration device for the user to the Prose Server, comprising: a third receiving unit and a second registration allocation unit located on the side of the service server; wherein the third receiving unit is configured to receive the Prose Server identification information sent by the UE according to the pre-configuration or the network. The registration message is sent by the direct interface, and the registration message carries the user identifier. The second registration allocation unit is configured to allocate or update the Prose ID to the user, and send the Prose ID to the UE to notify the UE to complete the registration to the adjacent service server.

Here, the apparatus further includes: a second logout unit configured to notify by the direct interface

The UE deletes the proximity service information of the UE.

Here, the direct interface carries the control plane interface on the user plane.

The implementation of the technical solution will be further described in detail below with reference to the accompanying drawings.

Embodiment 1 to Embodiment 5 are: based on the architecture without a direct interface between the UE and the Prose Server, that is, the case where there is no Sx2 interface in FIG. The sixth embodiment to the eighth embodiment are: based on the architecture of the direct interface between the UE and the Prose Server, that is, the Sx2 interface exists in FIG. 2.

Explain as follows:

Embodiment 1:

FIG. 3 is a schematic flowchart of an implementation process of the first embodiment of the present invention, including the following steps:

Step 301: The user accesses the mobile communication network to initiate an attach request message, where the message can carry the device capability of whether the device supports direct communication between users, and can also be referred to as proximity service capability.

Step 302: An optional step is to start, when the MME is unable to obtain the permanent identity IMSI of the user from the attach request message, to obtain the identifier IMSI of the user from the UE.

Step 303: The MME sends an update location request message to the HSS that saves the user subscription information according to the IMSI identifier. The user who saves the contract in the HSS authorizes the ability to use the proximity service and the Prose Server identification information that serves the user.

The capability information authorized by the user to use the adjacent service includes: the ability to authorize the use of the adjacent service on different carrier networks, the permission/disallowment of the discovery or discovery of information by the user of an operator network, and the like.

The Prose Server identification information includes: Prose Server name, ID, access point name, address, and so on.

Step 304: The HSS replies with an update location confirmation message, where the user subscription information includes the capability information of the user authorized to use the proximity service, and the Prose Server identification information.

Step 305: The network establishes a tunnel for data transmission by creating a session process.

Step 306: If the user equipment has the capability to support the proximity service and the user subscription allows the user to use the proximity service function on the current network, the MME needs to select a Prose Server for the user to serve. Specifically, the MME may obtain the address of the Prose Server according to the Prose Server identification information resolution or the DNS query.

Step 307: The MME sends a registration request message to the selected Prose Server. The user identification IMSI, the MME identity attached by the user, and the capability information of the user authorized to use the adjacent service.

Step 308: The Prose Server responds to the registration message, and the message carries the assigned Prose ID. Step 309: After the MME completes the attach process, the MME responds to the attach accept message, and the message carries the Prose Server to separate the Prose ID and the Prose Server ID for the user. The Prose Server ID includes the Prose Server ID, access point name, address, and so on.

Step 310: The UE sends the binding of the application identifier APP ID, Prose ID, and Prose Server ID to the APP Server for saving when the application is started. APP Server can use this binding relationship to convert the user information that the application layer needs to discover and communicate into user information that can be recognized by the network layer, and to find the Prose Server startup signaling operation for the user according to the Prose ID or Prose Server ID.

Embodiment 2:

FIG. 4 is a schematic flowchart of an implementation process of Embodiment 2 of the present invention, including the following steps:

Step 401: The UE initiates a tracking area update request when moving outside the TAI list coverage area or when the periodic update timer expires.

Step 402: The MME newly attached by the user finds the old MME that previously served the UE according to the GUTI identifier used for temporarily identifying the UE.

Step 403: The old MME sends the identifier information of the Prose Server selected by the user to the new MME in the context response message.

Step 404: The new MME establishes a core network bearer by creating a session process according to the bearer information in the context.

Step 405: The new MME sends an update location request to the HSS.

Step 406: The HSS returns the user subscription information to the new MME in the update location response message. Step 407: The new MME sends the user identity IMSI, the new MME identity attached by the user, and the capability information of the user authorized to use the proximity service to the user by using the registration/update request message. Prose Server. If the capability information of the user authorized to use the adjacent service changes in the subscription information or the capability information of the user configured by the MME to use the adjacent service changes, the new capability information is sent to the Prose Server in the process.

Step 408: The Prose Server may return the newly allocated Prose ID to the MME in the registration/update response message. Prose Server can periodically replace Prose IDs to ensure near-business discovery and communication security.

Step 409: If the Prose Server assigns a new Prose ID to the user, the Prose ID is sent to the UE in the Tracking Area Update Accept message.

Step 410: If the Prose ID changes, the UE initiates an application registration/update process to resend the APP ID, Prose ID, and Prose Server bindings to the APP server.

This embodiment is also applicable to the case where the MME changes during the handover process. The new MME obtains the Prose Server identity serving the user in the context of the context, and the new MME identity and the new user authorization to use the proximity service through the registration/update message. The information is updated to the Prose Server. At the same time, the Prose Server can re-allocate the Prose ID to the UE through the MME according to the conditions configured by the operator (for example, periodic update, etc.). The UE re-registers/updates the changed Prose ID, APP ID, and Prose ID bindings to the APP Server.

Embodiment 3:

FIG. 5 is a schematic flowchart of an implementation process of Embodiment 3 of the present invention, including the following steps:

Step 501: The operator modifies the user subscription data in the HSS, and the HSS initiates the process of inserting the user data to send the new subscription data to the MME currently registered by the user.

Step 502: The MME returns an insert user data confirmation message to the HSS.

Step 503: If the subscription parameters of the neighboring service in the user subscription data or the neighboring service related parameters configured by the MME are changed, the MME uses the registration/update request message to authorize the IMSI and the new user to use the capability information of the adjacent service. Send to Prose Server. In step 504, the Prose Server replies with a registration/update confirmation message. If the Prose Server re-assigns the Prose ID to the user, the response message also carries the Prose ID.

Step 505: If there is no suitable downstream direction NAS (such as TAU accept) message 7 carrying the newly allocated Prose ID, the MME sends the newly assigned Prose ID to the UE by using the newly defined Prose ID allocation command. This message is optional.

Step 506: The UE replies to the Prose ID Assignment Complete Response message.

Step 507, if the Prose ID is changed, the UE initiates an application registration/update process to resend the binding of the APP ID, the Prose Server ID, and the Prose ID to the APP Server.

Embodiment 4:

FIG. 6 is a schematic flowchart of an implementation process of Embodiment 4 of the present invention, including the following steps:

Step 601: When the UE initiates the logout user request or the HSS initiates the logout user request or the MME decides to log off the user or the MME checks that the subscription or the locally configured authorization to use the proximity service fails, the neighboring service logout process is initiated.

Step 602: The MME sends a logout request to the Prose Server serving the user, where the message carries the user identifier IMSI.

Step 603: The Prose Server deletes all the adjacent service context information related to the user identifier, including the Prose ID, the recorded user attached MME information, the subscription information for authorizing the use of the adjacent service, and the result information of the discovery/communication.

In step 604, the Prose Server replies to the MME with a reply response after deleting the user proximity service information.

Step 605: If the operation of this embodiment is triggered by the process of canceling the user, the UE may release the Prose ID of the network allocation when entering the logout state. If the adjacent service is deactivated due to the invalidation of the adjacent service subscription, the MME passes the newly defined The Prose ID delete command deletes the adjacent service information in the UE. During the user logout process, it is possible that the wireless link has been released, so 605 is optionally sent. It should be noted that: In this embodiment, the message name is not specifically limited. The meaning of the message is to deactivate the adjacent service function on the user side, and release the related service information (such as discovery, communication result, and corresponding radio resource allocation) saved by the user side. Information), including the release of Prose ID.

Step 606: The UE returns a Prose ID deletion response message. This step is optional and exists when the user is still attached to the network.

Step 607: If the Prose ID is invalid, the UE initiates an application deletion process to delete the binding relationship between the APP ID, the Prose ID, and the Prose ID in the APP server. This step is optional and exists when the user is still attached to the network.

Embodiment 5:

FIG. 7 is a schematic flowchart of an implementation process of Embodiment 5 of the present invention, including the following steps:

Step 701: The Prose Server can dynamically update the Prose ID according to the operator configuration, and send the newly allocated Prose ID to the MME by using the Prose ID assignment message.

Step 702: The MME sends the updated Prose ID to the UE by using a defined Prose ID assignment message.

Step 703: The UE replies to the MME with a Prose ID Assignment Response message.

Step 704: The MME returns an allocation response message to the Prose Server.

Step 705: The UE updates the binding of the APP ID, the Prose ID, and the Prose Server ID to the APP Server by using an application layer message.

Example 6:

FIG. 8 is a schematic flowchart of an implementation process of Embodiment 6 of the present invention, including the following steps:

Step 801: The user accesses the mobile network to initiate an attach request, where the message carries the capability of the user equipment to support the adjacent service.

Step 802: The MME sends an update location request to the HSS.

Step 803: The HSS replies to the update location confirmation message, where the user subscription information includes the capability information of the user authorized to use the proximity service, and the Prose Server identification information. Step 804: If the user equipment has the capability to support the proximity service and the user subscription allows the user to use the proximity service function on the current network, the MME needs to select a Prose Server for the user to serve. Specifically, the MME may obtain the address of the Prose Server according to the Prose Server identification information resolution or the DNS query.

Step 805: The MME sends a registration request message to the selected Prose Server, where the message includes the user identifier IMSI, the MME identifier attached by the user, and the capability information of the user authorized to use the adjacent service.

Step 806, the Prose Server responds to the registration message.

Step 807: The MME sends the Prose Server ID information to the UE in the attach accept message. The Prose Server ID includes the Prose Server ID, access point name, address, and so on.

Step 808: The UE sends a registration message to the selected Prose Server, where the message carries the user identifier IMSI.

Step 809, the Prose Server confirms that the user authorizes the use of the proximity service according to the content of the 805 message, and assigns the Prose ID to the user.

Step 810, the Prose Server replies with a registration response message, and the message carries the user-assigned

Prose ID.

Step 811, the user sends the binding of the APP ID, the Prose ID, and the Prose Server ID to the APP server by using the application layer message.

It should be noted that, in this embodiment, the user can pre-configure (for example, obtain from the ANDSF server) the Prose Server identification information for the service, so the Prose Server ID in step 807 is optional. When the user selects Prose Server according to the pre-configuration information, it needs to be consistent with the Prose Server selected by the network. The Prose Server is required to be resolved by the user and the network according to the configuration/registration Prose Server ID. The registration process of steps 808 and 809 can occur at any time after the user attaches, without the need for complete tight coupling with the attachment process.

Example 7: FIG. 9 is a schematic flowchart of the implementation process of the seventh embodiment of the present invention, including the following steps: Step 901: The Prose Server can periodically modify the Prose ID according to the requirements of the operator.

The Prose ID Assignment message sends the newly assigned Prose ID to the UE.

Step 902: The UE replies to the Prose Server with a Prose ID Assignment Response message.

Step 903: The UE updates the binding relationship between the APP ID, the Prose ID, and the Prose Server ID to the APP server.

It should be noted that the sending of the Prose ID in this embodiment does not depend on the NAS message, and is a direct interface between the UE and the Prose Server. If the MME changes on the network side, or the user authorizes the use of the change of the adjacent service capability, the MME still needs to complete the MME identity or the user authorization to use the proximity service capability to the Prose Server update, as shown in Figure 4 and Figure 5. In this embodiment, the allocation of the Prose ID is separated from the EPS flow, and can be performed separately in logic.

Example 8:

FIG. 10 is a schematic flowchart of an implementation process of Embodiment 8 of the present invention, including the following steps:

In step 1001, the Prose Server learns that the user is logged out of the network or the user is authorized to use the adjacent service capability. The learning method is as described in FIG. 6, and the MME attached by the user can notify Prose Ssrvsr according to the detection condition.

Step 1002: The Prose Server sends a Prose ID deletion message to the user, deletes the Prose ID assigned to the user, and further deletes the adjacent service information (such as the discovery, the communication result, and the corresponding radio resource allocation information) saved by the user side. This step can be sent optionally. If it is a user or network initiated EPS network logout process, then there may be no bearer connection at this time, then there is no need to send a Prose ID delete message. If the capability is invalid but the user is still connected to the EPS network, then this message can be sent. In this embodiment, the message name is not specifically limited, and the purpose is to activate the proximity service function on the user side.

In step 1003, the UE may optionally reply to the Prose ID deletion confirmation message. Whether to send depends on whether the user is currently able to access the EPS network. Step 1004: The UE deletes the binding of the APP ID, the Prose ID, and the Prose Server ID on the APP server by applying the delete message. This message can be sent optionally, depending on whether the user is currently able to access the EPS network.

The above embodiments of the embodiments of the present invention focus on the registration, Prose ID allocation, Prose ID information update, and logout processes required by the user to use the proximity service, and are not limited to being executed in a specific EPS process, and may be invoked according to actual conditions. , the preconditions for logical calls are not limited.

The above is only the preferred embodiment of the present invention and is not intended to limit the scope of the present invention. Industrial applicability

In the embodiment of the present invention, when the HSS sends the subscription information, the HSS sends the proximity service server identification information carried in the subscription information and the capability information of the user subscription to use the adjacent service to the MME; the MME obtains or is configured according to the subscription information. The service server identification information is selected to be adjacent to the service server. The embodiment of the present invention provides a clear specific implementation solution for how the proximity service server implements the management of the user and how the application server and the network using the adjacent service after the proximity of the service server cooperate with each other.

Claims

claims

1. A method for selecting a nearby business server. The method includes:

When the home user server HSS sends the subscription information, it sends the proximity service server identification information carried in the subscription information and the user's subscription authorization to use the proximity service capability information to the mobility management entity MME;

The MME selects a proximity service server based on the proximity service server identification information obtained or configured in the subscription information.

2. The method according to claim 1, wherein the proximity service server identification information includes: the name of the proximity service server, the identity of the proximity service server, the access point name of the proximity service server, and the address of the proximity service server. At least one piece of information.

3. The method according to claim 1, wherein the user's ability information to authorize the use of proximity services when signing up includes: the ability of different operator networks to authorize the use of proximity services, permission/denial information to be discovered by a user of an operator's network, or to be Discover at least one piece of information.

4. A selection device for a proximity service server, which includes: a first receiving unit and a selection unit located on the MME side; wherein,

The first receiving unit is configured to receive the proximity service server identification information carried in the subscription information sent by the HSS and the user's ability information to authorize the use of the proximity service when signing up;

The selection unit is configured to select a proximity service server based on proximity service server identification information obtained from the subscription information or configured by itself.

5. The device according to claim 4, wherein the proximity service server identification information includes: the name of the proximity service server, the identity of the proximity service server, the access point name of the proximity service server, and the address of the proximity service server. At least one piece of information.

6. The device according to claim 4, wherein the information about the ability of the user to sign up to authorize the use of proximity services includes: the ability of different operator networks to authorize the use of proximity services, permission/forbidden information to be discovered by an operator network user, or information about being discovered by a user of an operator network. Discover at least one piece of information.

7. A method for users to register with a nearby business server. The method includes:

The MME sends the user identification, the MME identification attached to the user, and the user's ability information to sign and authorize the use of proximity services through the registration/update message to the proximity service server selected based on the proximity service server identification information;

The proximity service server allocates or updates the proximity service identification Prose ID to the user, and sends the Prose ID to the MME. The MME sends the Prose ID and/or the proximity service server identification Prose Server ID to the UE through the downlink non-access layer NAS message.

8. The method according to claim 7, wherein the method further includes: the MME deletes the user context information saved on the proximity service server through a logout message, and the MME deletes the UE's proximity service information through a downlink NAS message.

9. The method according to claim 7, wherein the method further includes: when the UE receives a message to allocate/update/delete the Prose ID, the binding relationship of the application layer ID, Prose ID, and Prose Server ID in the application Register/update/delete on the server.

10. The method according to claim 7, 8 or 9, wherein the Prose ID is an identifier used to identify a user during proximity service discovery or communication.

11. The method according to claim 8, wherein the user context information saved on the proximity service server includes the MME identification attached to the user, the user's ability information authorized to use the proximity service, Prose ID, and proximity service discovery information. At least one piece of information.

12. The method according to claim 7, 8 or 9, wherein the downlink NAS message includes: any one of an attachment accept message sent by the MME to the UE, a tracking area update accept message, and a newly defined Prose ID allocation message. kind of news.

13. The method according to claim 7, 8 or 9, wherein the triggering condition for the MME to send the registration/update message to the proximity service server is: the user attaches to the network, or the MME accessed by the user occurs. Change, or the user's ability information in the subscription information to authorize the use of proximity services changes.

14. The method according to claim 8, wherein the triggering condition for the MME to send a logout message to the proximity service server is: the user detaches from the network, or the network no longer authorizes the user to use the proximity service.

15. The method according to claim 7, 8 or 9, wherein the method further includes: when the MME serving users changes, the new MME needs to obtain the proximity service server identification information in the old MME, and the new MME The MME identity attached to the user and the capability information of the user's contract authorization to use the proximity service are sent to the proximity service server through the registration/update message.

16. The method according to claim 8, wherein the method further comprises: the MME deletes the user context information saved on the adjacent service server through a logout message, and accepts the message through attachment, tracking area update, and logout request/accept message. , the defined Prose ID deletion message is used to activate the proximity service of the UE, and delete the proximity service related information in the UE.

17. A registration device for users to a nearby service server, the device includes: a second receiving unit and a first registration distribution unit located on the nearby service server side; wherein,

The second receiving unit is configured to receive the user identification sent by the MME through the registration/update message, the MME identification attached to the user, and the user's ability information to authorize the use of proximity services through contract signing; and the first registration allocation unit is configured to provide the user with Allocate or update the nearby Prose ID, send the Prose ID to the MME, and notify the MME to send the Prose ID and/or Prose Server ID to the UE through the downlink NAS message to complete the registration with the nearby service server.

18. The device according to claim 17, wherein the second receiving unit is further configured to receive a logout message sent by the MME;

The device also includes: a first deregistration unit configured to delete the user context information saved on the proximity service server after receiving the deregistration message, and notify the MME to delete the proximity service information of the UE through the downlink NAS message.

19. The device according to claim 18, wherein the first logout unit is further configured to notify the MME by attaching after deleting the user context information saved on the adjacent service server. Accept messages, tracking area update accept messages, logout request/accept messages, and defined Prose ID deletion messages to activate the proximity service of the UE and delete proximity service related information in the UE.

20. The apparatus according to claim 17, wherein the second receiving unit is further configured to: when the MME serving the user changes and the new MME needs to obtain the proximity service server identification information in the old MME, The new MME receives the MME identity attached to the user and the capability information of the user's contract authorization to use the proximity service through the registration/update message.

21. A method for users to register with a nearby business server. The method includes:

The UE sends a registration message to the proximity service server selected based on the proximity service server identification information through a direct interface based on the preconfigured or network-sent proximity service server identification information, and the registration message carries the user identification;

The proximity service server allocates or updates the Prose ID to the user and sends the Prose ID to the UE.

22. The method according to claim 21, wherein the method further comprises: the proximity service server deletes the proximity service information of the UE through the direct interface.

23. The method according to claim 21, wherein the method further includes: when the UE receives a message to allocate/update/delete a Prose ID, the binding relationship between the application layer ID, Prose ID, and Prose Server ID is Register/update/delete on the server.

24. The method according to claim 21, 22 or 23, wherein the method further includes: the MME selects a proximity service server based on the Prose Server ID of the subscription information in the HSS, and notifies the UE through a NAS message.

25. The method according to claim 24, wherein the direct interface carries a control plane interface on the user plane.

26. The method according to claim 24, wherein the NAS message includes: any one of an attachment acceptance message, a tracking area update acceptance message, and a newly defined Prose ID allocation message.

27. A device for registering users to a nearby service server. The device includes: The device package It includes: a third receiving unit and a second registration allocation unit located on the proximity service server side; wherein, the third receiving unit is configured to receive the registration sent by the UE through the direct interface according to the preconfiguration or the proximity service server identification information sent by the network. Message, the registration message carries the user ID;

The second registration allocation unit is configured to allocate or update the Prose ID for the user, and assign the Prose ID to the user.

The ID is sent to the UE to notify the UE to complete the registration with the nearby service server.

28. The device according to claim 27, wherein the device further includes: a second deregistration unit configured to notify the UE to delete the proximity service information of the UE through the direct interface.

29. The device according to claim 28, wherein the direct interface carries a control plane interface on the user plane.