CN104105086A

CN104105086A - Selection method and device of Prose Server, and user registration method and device

Info

Publication number: CN104105086A
Application number: CN201310125212.8A
Authority: CN
Inventors: 王静; 宗在峰
Original assignee: ZTE Corp
Current assignee: ZTE Corp
Priority date: 2013-04-11
Filing date: 2013-04-11
Publication date: 2014-10-15
Anticipated expiration: 2033-04-11
Also published as: CN104105086B; WO2014166294A1

Abstract

The invention discloses a selection method and device of a Prose Server, and a user registration method and device. The method includes the following steps: when a Home Subscriber Server (HSS) sends subscription information, Prose Server identification information and capability information of user subscribing and authorizing use of a proximity service which are carried by the subscription information are sent to a mobility management entity (MME); and the MME selects a Prose Server according to the acquired or configured Prose Server identification information in the subscription information. A selection unit is used for selecting a Prose Server according to acquired or self-configured Prose Server identification information in subscription information. By adoption of the selection method of the Prose Server in the invention, a specific implementation scheme is provided directed at the problems that how does a Prose Server realize management of users, and how do an Application Server that uses a proximity service and a network realize collaborative operation after introduction of a Prose Server.

Description

Selection method and device of proximity business server and user registration method and device

Technical Field

The invention relates to an inter-user proximity service technology in the field of mobile communication, in particular to a method and a device for selecting a proximity service server and a method and a device for registering a user to the proximity service server.

Background

In order to maintain the competitiveness of the third Generation mobile communication System in the communication field, provide a mobile communication service with faster rate, lower delay, and more personalized for users, and at the same time, reduce the operation cost of operators, the third Generation Partnership Project (3 GPP) standard working group has been dedicated to the research of the Evolved Packet System (EPS). As shown in fig. 1, which is a schematic structural diagram of an evolved packet domain system, in fig. 1, the whole EPS system is divided into two parts, namely a radio access network and a core network. In the core Network, a Home Subscriber Server (HSS), a Mobility Management Entity (MME), a Serving GPRS Support Node (SGSN), a Policy and Charging Rule Function (PCRF), a Serving Gateway (S-GW), a Packet Data Gateway (P-GW), and a Packet Data Network (PDN, Packet Data Network) are included. The functions of each part are described in detail below:

the HSS is a permanent storage location for the user subscription data, and is located in a home network to which the user subscribes.

And the MME is a storage place of the user subscription data in the current network and is responsible for non-access stratum signaling management from the terminal to the network, the security verification function of the terminal, the mobility management of the terminal, the tracking and paging management function and the bearer management in the idle mode of the user.

The SGSN is a service support point for a Global System for Mobile communications (GSM) Enhanced Data Rate for GSM evolution (EDGE) Radio Access Network (GERAN, GSM EDGE Radio Access Network) and a Universal Mobile Telecommunications System (UMTS) Terrestrial Radio Access Network (UTRAN, UMTS Terrestrial Radio Access Network) user to Access a core Network, and is similar in function to a mobility management entity and responsible for functions such as location update, paging management, bearer management, and the like of the user.

The S-GW is a gateway from a core network to a wireless system and is responsible for user plane bearing from a terminal to the core network, data caching in a terminal idle mode, a function of initiating a service request at a network side, and functions of lawful interception and packet data routing and forwarding; the service gateway is responsible for counting the condition of the user terminal using the wireless network, generating a bill of the terminal using the wireless network and transmitting the bill to the charging gateway.

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

PDN, an IP service network of an operator, which provides IP services to users through the operator's core network.

The PCRF is a server in the evolved system responsible for providing rules in charging control, online credit control, threshold control, and Quality of Service (QoS) policies.

The Radio access Network is composed of an Evolved node b (eNB) and a 3G Radio Network Controller (RNC), and is mainly responsible for receiving and transmitting Radio signals, and manages Radio resources, resource scheduling, and access control of an air interface by contacting the air interface with a terminal.

The serving GPRS support node is an upgraded SGSN, can support an S4 interface with a serving gateway, and performs interworking with a mobility management unit using a GPRS tunneling Protocol version 2(GTPv2, GPRS tunneling Protocol version 2). Whereas for SGSNs supporting 3G core networks the Packet Switching (PS) domain network architecture differs from that of fig. 1. At this time, the SGSN and the MME are connected by a Gn interface, and communicate by using a GPRS tunneling Protocol version 1(GTPv1, GPRS tunneling Protocol version 1). The SGSN can not be connected with the service Gateway, and is connected with a Gateway GPRS Support Node (GGSN) through a Gn interface to directly access the packet data network.

In the stage R12 of the 3GPP standard, some european and american devices and operators have recognized the need to implement public safety functions in mobile communication networks that allow direct communication between devices, based on the requirements of national regulations. The public safety function is mainly used in a scene that wireless access is interrupted due to disaster and communication between devices is needed to complete rescue work. This need is discussed in a 3GPP standards organization. The applicable scene of direct connection between devices is expanded in the discussion process, so that the function can serve the application in the business field. For example, when two users use the social network application, if the distance between the two users is close enough, the data can be transferred in a direct mode between the devices without carrying and routing the data through an upper network, thereby reducing the load of the network and improving the transmission efficiency of the data. In addition, advertisement pushing, friend discovery, information delivery and the like of business application can be completed through the function, so that a network operator can better provide support for user application, and the user and the business operator have good experience, thereby further bringing economic benefits.

Based on the EPS mobile communication network, in order to meet the Proximity service requirement of direct connection between users, a special control network element, i.e., a Proximity service Server (Proximity service Server), is added in the network, as shown in fig. 2. The Prose Server has the functions of authorizing whether a user is allowed to use the adjacent service, controlling the discovery operation and the establishment of communication of the user through an Sx1 interface during authorization, and supporting the service function at the application level through interaction with an application through an Sx3 interface. The Prose Server may carry direct messages with the UE over the user plane of the Sx2 interface, which may optionally exist.

At present, no specific implementation scheme exists for the problem of managing users by a Prose Server (for example, selecting a Prose Server, and managing users after accepting user registration based on the Prose Server selected by the user), and how to interoperate an application Server (APPServer) using an adjacent service after introducing the Prose Server and a network also needs to be determined.

Disclosure of Invention

In view of the above, the present invention provides a method and an apparatus for selecting a proximity service server, and a method and an apparatus for registering a user to solve the above problems.

In order to achieve the purpose, the technical scheme of the invention is realized as follows:

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

when a Home Subscriber Server (HSS) sends subscription information, sending the identification information of an adjacent service server carried in the subscription information and the capability information of a user subscription authorization for using the adjacent service to a Mobility Management Entity (MME);

and the MME selects the adjacent service server according to the identification information of the adjacent service server obtained or configured in the subscription information.

Wherein the proximity service server identification information includes: the name of the adjacent service server, the identification of the adjacent service server, the name of the access point of the adjacent service server and the address of the adjacent service server.

Wherein, the capability information of the user signing and authorizing the use of the proximity service comprises: different operator networks authorize at least one of the ability to use nearby services, enable/disable discovery information or discovery information by one operator network user.

A selection device proximate to a service server, the device comprising: a first receiving unit and a selecting unit which are positioned at the MME side; wherein,

the first receiving unit is used for receiving the identification information of the adjacent service server carried in the subscription information sent by the HSS and the capability information of the user signing and authorizing the use of the adjacent service;

and the selection unit is used for selecting the adjacent service server according to the identification information of the adjacent service server obtained in the subscription information or configured by the selection unit.

A method of registering a user with a proximity services server, the method comprising:

the MME sends the user identification, the MME identification attached by the user and the ability information of the user signing authorization to use the proximity service to a proximity service server selected based on the identification information of the proximity service server through a registration/update message;

the adjacent service Server distributes or updates the adjacent service identification Prose ID for the user, sends the Prose ID to the MME, and the MME sends the Prose ID and/or the adjacent service Server identification Prose Server ID to the UE through the downlink non-access stratum NAS message.

Wherein, the method also comprises: and the MME deletes the user context information stored on the adjacent service server through a logout message, and the MME deletes the adjacent service information of the UE through a downlink NAS message.

Wherein, the method also comprises: and when the UE receives the message of distributing/updating/deleting the Prose ID, the binding relation of the application layer ID, the Prose ID and the Prose Server ID is registered/updated/deleted on the application Server.

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

The user context information stored on the proximity service server includes at least one of an MME identifier attached to the user, capability information that the user authorizes the use of the proximity service, a Prose ID, and proximity service discovery information.

Wherein the downlink NAS message comprises: and the MME sends any one of an attach accept message, a tracking area update accept message and a newly defined Prose ID allocation message to the UE.

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 is changed, or the capability information of the user signing and authorizing the use of the adjacent service in the signing information is changed.

Wherein, the triggering condition for the MME to send the logout message to the adjacent service server is as follows: the user detaches from the network or the network no longer authorizes the user to use the proximity service.

Wherein, the method also comprises: when the MME serving the user is changed, the new MME needs to acquire the identification information of the adjacent service server in the old MME, and the new MME sends the MME identification attached to the user and the capability information of the user signing and authorizing the use of the adjacent service to the adjacent service server through a registration/update message.

Wherein, the method also comprises: the MME deletes the user context information stored on the adjacent service server through the logout message, deactivates the adjacent service of the UE through the attachment acceptance message, the tracking area update acceptance message, the logout request/acceptance message and the defined Prose ID deletion message, and deletes the information related to the adjacent service in the UE.

An apparatus for registering a user with a proximity service server, the apparatus comprising: the second receiving unit and the first registration distributing unit are positioned at the side close to the service server; wherein,

the second receiving unit is configured to receive a user identifier sent by the MME through the registration/update message, an MME identifier attached to the user, and capability information of the user signing and authorizing to use the proximity service;

the first registration allocation unit is used for allocating or updating a proximity Prose ID for a user, sending the Prose ID to the MME, and informing the MME to send the Prose ID and/or the Prose Server ID to the UE through a downlink NAS message to complete the registration to the proximity service Server.

The second receiving unit is further configured to receive a deregistration message sent by an MME;

the device also includes: and the first logout unit is used for deleting the user context information stored on the adjacent service server after receiving the logout message and informing the MME of deleting the adjacent service information of the UE through the downlink NAS message.

The first cancellation unit is further configured to, after deleting the user context information stored in the proximity service server, notify the MME of deactivating the proximity service of the UE through an attach accept message, a tracking area update accept message, a cancellation request/accept message, and a defined Prose ID delete message, and delete information related to the proximity service in the UE.

The second receiving unit is further configured to receive, when the MME serving the user changes and the new MME needs to obtain the identifier information of the proximity service server in the old MME, the new MME identifying the MME to which the user is attached and the capability information of subscribing and authorizing the user to use the proximity service through the registration/update message.

the UE sends a registration message to a proximity service server selected based on the identification information of the proximity service server through a direct interface according to the identification information of the proximity service server pre-configured or sent by a network, wherein the registration message carries a user identification;

and the adjacent service server allocates or updates the Prose ID for the user and sends the Prose ID to the UE.

Wherein, the method also comprises: and the adjacent service server deletes the adjacent service information of the UE through the direct interface.

Wherein, the method also comprises: and the MME selects an adjacent service Server according to the Prose Server ID of the subscription information in the HSS and informs the UE through the NAS message.

Wherein the direct interface is carried by a control plane interface on a user plane.

Wherein the NAS message comprises: any one of an attach accept message, a tracking area update accept message, and a newly defined Prose ID assignment message.

An apparatus for registering a user with a proximity service server, the apparatus comprising: the device includes: a third receiving unit and a second registration distributing unit which are positioned at the side close to the service server; wherein,

the third receiving unit is configured to receive a registration message sent by the UE through the direct interface according to the identifier information of the proximity service server sent by the pre-configuration or the network, where the registration message carries the user identifier;

and the second registration allocation unit is used for allocating or updating the Prose ID for the user, sending the Prose ID to the UE and informing the UE of completing the registration to the adjacent service server.

Wherein, the device still includes: and the second cancellation unit is used for notifying the UE to delete the adjacent service information of the UE through the direct interface.

When HSS sends subscription information, the HSS sends the identification information of the adjacent service server carried in the subscription information and the ability information of the user signing authorization using the adjacent service to MME; and the MME selects the adjacent service server according to the identification information of the adjacent service server obtained or configured in the subscription information. The invention provides a specific implementation scheme aiming at the problems of how to realize the management of the user by the adjacent service server and how to realize the cooperative operation between the application server using the adjacent service after the adjacent service server is introduced and the network.

Drawings

FIG. 1 is a block diagram of an evolved packet domain system;

fig. 2 is a schematic diagram of a conventional network architecture supporting proximity service functions;

FIG. 3 is a flow chart illustrating an implementation of one embodiment of the present invention;

FIG. 4 is a schematic flow chart of a second embodiment of the present invention;

FIG. 5 is a flow chart illustrating a third embodiment of the present invention;

FIG. 6 is a flow chart illustrating an implementation of the fourth embodiment of the present invention;

FIG. 7 is a schematic flow chart of a fifth embodiment of the present invention;

FIG. 8 is a schematic flow chart of a sixth embodiment of the present invention;

FIG. 9 is a schematic flow chart of a seventh implementation of the present invention;

fig. 10 is a schematic flow chart of an implementation of the eighth embodiment of the present invention.

Detailed Description

The scheme of the invention is how to select the Prose Server when the mobile network provides the proximity service for the user, and the user realizes the registration and the identification binding based on the selected Prose Server, firstly, the invention solves the problems of how to select the Prose Server, the function of the user registering to the Prose Server, and the binding of the application layer identification, the network layer identification and the Prose Server on the APP Server, so that the Prose Server and the APP Server can identify and address the specific user, and can cooperate to complete the management of the specific user under the condition of the permission of the subscription authorization.

It should be noted that: the proximity service Server is referred to as a Prose Server, and the application Server or APP Server is referred to as an APP Server. The Prose Server identification information herein refers to the Prose Server ID.

A method for selecting a Prose Server mainly comprises the following steps;

a method for selecting a Prose Server comprises the following steps: the HSS adds the Prose Server identification information for the user service and the capability information of the user signing authorization using the adjacent service in the signing data. And the HSS sends the information to the MME when sending the subscription information.

And the MME selects the proseSERVER according to the proseSERER identification information obtained or configured in the subscription.

Further, the Prose Server identification information (Prose Server ID) includes: name, identity, access point name, address, etc. of the Prose Server.

Further, the capability information of the user signing and authorizing the use of the proximity service includes: different operator networks authorize the ability to use nearby services, allow/disallow discovery information or discovery information by certain operator network users, etc.

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

A selection device proximate to a service server comprising: a first receiving unit and a selecting unit which are positioned at the MME side; the first receiving unit is used for receiving the identification information of the adjacent service server carried in the subscription information sent by the HSS and the capability information of the user signing and authorizing the use of the adjacent service; the selection unit is used for selecting the adjacent service server according to the identification information of the adjacent service server obtained from the subscription information or configured by the selection unit.

Here, the proximity service server identification information includes: the name of the adjacent service server, the identification of the adjacent service server, the name of the access point of the adjacent service server and the address of the adjacent service server.

Here, the capability information of the user signing up for authorization to use the proximity service includes: different operator networks authorize at least one of the ability to use nearby services, enable/disable discovery information or discovery information by one operator network user.

A method for registering a user to a Prose Server mainly comprises the following steps:

a method for registering a user to a Prose Server comprises a first scheme as follows: and the MME sends the user identification, the MME identification attached by the user and the capability information of the user authorized to use the proximity service to the Prose Server selected based on the Prose Server identification information through the registration/update message. The Prose Server allocates or updates the Prose ID for the user, and sends the Prose ID to the MME. And the MME sends the Prose ID and/or the Prose Server ID to the UE through a downlink NAS message.

Further, the MME may delete the user context information saved on the Prose Server through a deregistration message. And the MME deletes the adjacent service information of the UE through the downlink NAS message.

Further, when receiving the message of allocating/updating/deleting the Prose ID, the UE registers/updates/deletes the binding relationship among 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 an adjacent service discovery or communication process.

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, identification, access point name, address, etc. of the Prose Server.

Further, the premise of the MME initiating the registration/update to the Prose Server is that the MME to which the user attaches to the network or the MME to which the user accesses changes or the capability information of the user authorized to use the proximity service in the subscription changes.

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

Further, the MME may delete the user context information stored in the Prose Server through a deregistration message, deactivate the proximity service function of the UE through an attach accept, a tracking area update accept, a deregistration request/accept message, and a defined Prose ID delete message, delete the proximity service related information in the UE, including deleting the Prose ID in the UE.

Further, the premise of the MME initiating the logoff is that the user is detached from the network or the network no longer authorizes the user to use the function of the adjacent service.

Further, the user context information stored in the Prose Server includes an MME identifier attached to the user, capability information that the user authorizes to use the proximity service, a Prose ID, proximity service discovery information, and the like.

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

A device for registering a user with a Prose Server, comprising: the second receiving unit and the first registration distributing unit are positioned at the side close to the service server; the second receiving unit is used for receiving a user identifier sent by the MME through the registration/update message, an MME identifier attached to the user, and capability information of the user signing and authorizing the use of the adjacent service; the first registration allocation unit is used for allocating or updating a proximity Prose ID for a user, sending the proximity Prose ID to the MME, and informing the MME to send the proximity Prose ID and/or the proximity Server ID to the UE through a downlink NAS message to complete the registration to the proximity service Server.

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

Here, the first deregistration unit is further configured to, after deleting the user context information stored in the neighboring service server, notify the MME of deactivating the neighboring service of the UE by an attach accept message, a tracking area update accept message, a deregistration request/accept message, and a defined Prose ID delete message, and delete the information related to the neighboring service in the UE.

Here, the second receiving unit is further configured to receive, when the MME serving the user changes and the new MME needs to obtain the neighbor service server identification information in the old MME, the new MME identifying the MME to which the user is attached and the capability information of subscribing and authorizing the user to use the neighbor service through the registration/update message.

A method for registering a user to a Prose Server comprises a second scheme as follows: and the UE initiates registration to the Prose Server selected based on the Prose Server identification information through a direct interface according to the Prose Server identification information sent by the pre-configuration or the network, wherein the registration message carries the user identification. And the Prose Server allocates or updates the Prose ID for the user and sends the Prose ID to the UE.

Further, the Prose Server may delete the proximity service information as the user through a direct interface with the UE.

Further, the network may configure the UE with the Prose Server ID via the ANDSF Server.

Further, the MME may select a Prose Server according to the Prose Server ID subscribed in the HSS, and notify the UE through an NAS message.

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

Further, the NAS message includes attach accept, routing area update accept, newly defined Prose ID assignment message, and the like.

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

A device for registering a user with a Prose Server, comprising: a third receiving unit and a second registration distributing unit which are positioned at the side close to the service server; the third receiving unit is used for receiving a registration message sent by the UE through a direct interface according to the Prose Server identification information sent by the pre-configuration or the network, wherein the registration message carries the user identification; the second registration allocation unit is used for allocating or updating the Prose ID for the user, sending the Prose ID to the UE and informing the UE of completing the registration to the adjacent service server.

Here, the apparatus further includes: and the second cancellation unit is used for notifying the UE to delete the adjacent service information of the UE through the direct interface.

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

The following describes the embodiments in further detail with reference to the accompanying drawings.

The first embodiment to the fifth embodiment are as follows: based on the architecture without direct interface between UE and Prose Server, i.e. without Sx2 interface in fig. 2.

The sixth embodiment to the eighth embodiment are: based on the architecture that there is a direct interface between the UE and the Prose Server, i.e. the case of the Sx2 interface in fig. 2.

Are illustrated below:

the first embodiment is as follows:

fig. 3 is a schematic diagram of an implementation flow of the first embodiment of the present invention, which includes the following steps:

step 301, a user accesses to a mobile communication network and initiates an attach request message, where the message may carry a device capability of whether the device supports direct communication between users, which may also be referred to as an adjacent service capability.

Step 302, optional step, when the MME cannot obtain the permanent identity IMSI of the user from the attach request message, the procedure is started to obtain the identity IMSI of the user from the UE.

Step 303, the MME sends a location update request message to the HSS storing the subscriber subscription information according to the IMSI identity. The HSS stores the capability information of the signed user authorizing the use of the adjacent service and the Prose Server identification information for the user service.

The capability information of the user authorizing the use of the proximity service includes: the ability to authorize the use of adjacent services at different operator networks, the enabling/disabling of discovery or discovery information by users of a certain operator network, etc.

The Prose Server identification information includes: name, ID, access point name, address, etc. of the Prose Server.

Step 304, the HSS replies an update location confirmation message, where the user subscription information in the message includes capability information that the user authorizes to use the proximity service, and Prose Server identification information.

At step 305, the network establishes a tunnel for data transmission through a create session procedure.

In step 306, if the ue has the capability of supporting the proximity service and the user subscribes to allow the user to use the proximity service function in the current network, the MME needs to select a Prose Server for the user. Specifically, the MME may obtain the address of the Prose Server according to Prose Server identification information analysis or DNS query.

Step 307, the MME sends a registration request message to the selected Prose Server, where the message includes a user identifier IMSI, an MME identifier attached to the user, and capability information of the user authorizing to use the proximity service.

Step 308, the Prose Server responds to the registration message, which carries the allocated Prose ID.

Step 309, after the MME completes the attach process, the MME responds to the attach accept message, which carries the Prose ID and the Prose Server ID allocated by the Prose Server to the user. The Prose Server ID includes the Prose Server identity, access point name, address, etc.

In step 310, the UE sends the binding of the APP ID, the Prose ID, and the Prose Server ID to the APP Server for storage when starting the application. The APP Server can use the binding relationship to convert the user information which needs to be discovered and communicated by the application layer into user information which can be identified by the network layer, and find out the Prose Server starting signaling operation for the user service according to the Prose ID or the Prose Server ID.

Example two:

fig. 4 is a schematic flow chart of an implementation of the second embodiment of the present invention, which includes the following steps:

in step 401, the UE initiates a tracking area update request when moving outside the TAI list coverage area or when the periodic update timer times out.

In step 402, the MME newly attached to the user finds the old MME serving the UE previously according to the GUTI used for temporarily identifying the UE.

In step 403, the old MME brings the identity information of the Prose Server selected for the user back to the new MME in the context response message.

In step 404, the new MME establishes a core network bearer through a session creation procedure according to the bearer information in the context.

In step 405, the new MME sends an update location request to the HSS.

In step 406, the HSS returns the user subscription information to the new MME in an update location response message.

Step 407, the new MME sends the user identifier IMSI, the new MME identifier attached to the user, and the capability information of the user authorized to use the proximity service to the ProseServer serving the user through the registration/update request message. If the capability information of the user authorized to use the proximity service in the subscription information changes or the capability information of the user authorized to use the proximity service locally configured by the MME changes, the new capability information is sent to the Prose Server in the process.

In step 408, the Prose Server may return the newly allocated Prose ID to the MME in a registration/update response message. The Prose Server can regularly replace the Prose ID to ensure the safety of the adjacent service discovery and communication.

Step 409, if the Prose Server allocates a new Prose ID to the user, then the Prose ID is sent to the UE in the tracking area update accept message.

Step 410, if the Prose ID changes, the UE starts the application registration/update process to resend the binding of APP ID, Prose ID and Prose Server to APP Server.

The embodiment is also applicable to the case that the MME changes during the handover process, where the new MME obtains a Prose Server identifier serving the user during the context interaction process, and updates the new MME identifier and the new capability information of the user authorizing to use the proximity service to the Prose Server through the registration/update message, and at the same time, the Prose Server may reallocate the Prose ID according to the conditions (e.g., periodic update, etc.) configured by the operator and forward the Prose ID to the UE through the MME. And the UE re-registers/updates the changed Prose ID, APP ID and the binding of the Prose ID to the APP Server.

Example three:

fig. 5 is a schematic flow chart of an implementation of the third embodiment of the present invention, which includes the following steps:

step 501, the operator modifies the user subscription data in the HSS, and then the HSS initiates a 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 subscriber data confirm message to the HSS.

In step 503, if the subscription parameters related to the proximity service in the subscription data of the user or the related parameters of the proximity service configured locally by the MME change, the MME sends the user identifier IMSI and the new capability information of the user authorizing to use the proximity service to the Prose Server through the registration/update request message.

In step 504, the Prose Server replies to the registration/update confirm message. If the Prose Server allocates the Prose ID to the user again, the response message carries the Prose ID at the same time.

In step 505, if there is no suitable NAS (e.g. TAU accept) message in the downlink direction to carry the newly allocated Prose ID, the MME sends the newly allocated Prose ID to the UE using the newly defined Prose ID allocation command. This message is an optional transmission.

In step 506, the UE replies a Prose ID assignment complete response message.

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

Example four:

fig. 6 is a schematic flow chart of an implementation of the fourth embodiment of the present invention, which includes the following steps:

step 601, when the UE initiates a user logout request, or the HSS initiates a user logout request, or the MME determines to logout the user, or the MME checks that the capability information of the subscribed or locally configured authorized use of the proximity service is invalid, then a proximity service logout procedure is initiated.

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

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

Step 604, the Prose Server replies a logout response to the MME after deleting the service information that the user is close to.

Step 605, if the operation of this embodiment is initiated in the process of deregistering the user, the UE may release the Prose ID allocated by the network when entering the deregistered state, and if the service deregisters due to the proximity service subscription failure, the MME deletes the proximity service information in the UE through the newly defined Prose ID deletion command. At the time of the user logoff procedure, it is possible that the wireless link has been released, and therefore 605 may be sent optionally.

It should be noted that: the message name is not specifically limited in this embodiment, and the meaning of the message is to deactivate the proximity service function of the user side, release the proximity service related information (such as discovery, communication result, and corresponding radio resource allocation information) stored by the user side, and include release of the Prose ID.

In step 606, the UE returns a Prose ID delete response message. This step is optional, as it exists while 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 APP ID in the APP server, the Prose ID, and the binding relationship of the Prose ID. This step is optional, as it exists while the user is still attached to the network.

Example five:

fig. 7 is a schematic flow chart of an implementation of the fifth embodiment of the present invention, which includes the following steps:

step 701, the Prose Server can dynamically update the Prose ID according to the configuration of the operator, and send the newly allocated Prose ID to the MME through the Prose ID allocation message.

In step 702, the MME sends the updated Prose ID to the UE via the defined Prose ID assignment message.

In step 703, the UE replies a Prose ID assignment response message to the MME.

In step 704, the MME replies 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 the application layer message.

Example six:

fig. 8 is a schematic flow chart of an implementation of the sixth embodiment of the present invention, which includes the following steps:

step 801, a user accesses a mobile network to initiate an attach request, and a message carries the capability of whether the user equipment supports the adjacent service.

In step 802, the MME sends an update location request to the HSS.

Step 803, the HSS replies an update location confirmation message, where the user subscription information in the message includes capability information that the user authorizes to use the proximity service, and Prose Server identification information.

In step 804, if the ue has the capability of supporting proximity services and the user subscribes to allow the user to use the proximity services function in the current network, the MME needs to select a Prose Server for the user. Specifically, the MME may obtain the address of the Prose Server according to Prose Server identification information analysis or DNS query.

Step 805, the MME sends a registration request message to the selected Prose Server, where the message includes a user identifier IMSI, an MME identifier attached to the user, and capability information of the user authorizing to use the proximity service.

In step 806, the Prose Server responds to the registration message.

In step 807, the MME sends the Prose Server ID information to the UE in the attach accept message. The Prose Server ID includes the identity, access point name, address, etc. of the Prose Server.

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 to use the proximity service according to the 805 message content, and allocates the Prose ID to the user.

Step 810, the Prose Server replies to the registration response message, and the message carries the Prose id allocated to the user.

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

It should be noted that: the user of this embodiment may pre-configure (e.g., obtain from the ANDSF Server) the Prose Server identification information served for him, so the Prose Server ID in step 807 is optional. When the user selects the Prose Server according to the pre-configuration information, the user needs to ensure the consistency with the Prose Server selected by the network. The user and the network are required to analyze the unique Prose Server according to the configuration/subscription Prose Server ID. The registration process of steps 808 and 809 may be performed at any time after the user attaches, and need not be fully tightly coupled to the attachment process.

Example seven:

fig. 9 is a schematic flow chart of an implementation of the seventh embodiment of the present invention, which includes the following steps:

in step 901, the Prose Server can periodically modify the Prose ID according to the operator requirement, and send the newly allocated Prose ID to the UE through the Prose ID allocation message.

In step 902, the UE replies a Prose ID assignment response message to the Prose Server.

Step 903, the UE updates the binding relationship among the APP ID, the Prose ID and the Prose Server ID to the APP Server.

It should be noted that, in this embodiment, the sending of the Prose ID does not depend on the NAS message, and a direct interface between the UE and the Prose Server is adopted. If the change of the MME or the change of the user authorization to use the proximity service capability occurs on the network side, the MME still needs to complete the update of the MME identifier or the user authorization to use the proximity service capability to the Prose Server, as described in fig. 4 and fig. 5. The embodiment separates the allocation of the Prose ID from the EPS flow, and can be logically performed separately.

Example eight:

fig. 10 is a schematic flow chart of an implementation of the eighth embodiment of the present invention, which includes the following steps:

step 1001, the Prose Server learns that the user logs off from the network or the user authorizes the use of the adjacent service capability to be invalid. The learning method is as described in fig. 6, and the MME attached by the user may notify the proseerver according to the detection condition.

Step 1002, the Prose Server sends a Prose ID delete message to the user, deletes the Prose ID allocated to the user, and further deletes the adjacent service information (such as discovery, communication result and corresponding radio resource allocation information) stored at the user side. This step may optionally be sent, and if it is a user or network initiated EPS network deregistration procedure, there may be no bearer connection already at this time, and there is no need to send the Prose ID delete message. This message can be sent if the user is still accessing the EPS network because of the failed capability. The message name is not specifically limited in this embodiment, and the purpose is to deactivate the proximity service function on the user side.

In step 1003, the UE may optionally reply to the Prose ID delete confirmation message. Whether to send depends on whether the user is currently also 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 through the application deletion message. This message may optionally be sent depending on whether the user is currently also able to access the EPS network.

The above embodiments of the present invention mainly reflect 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 be executed in a specific EPS flow, and may be logically invoked according to the actual situation, and the precondition of the logical invocation is not limited.

The above description is only a preferred embodiment of the present invention, and is not intended to limit the scope of the present invention.

Claims

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

2. The method of claim 1, wherein the proximity service server identification information comprises: the name of the adjacent service server, the identification of the adjacent service server, the name of the access point of the adjacent service server and the address of the adjacent service server.

3. The method of claim 1, wherein the capability information of the user signing up for authorization to use the proximity service comprises: different operator networks authorize at least one of the ability to use nearby services, enable/disable discovery information or discovery information by one operator network user.

4. A selection device proximate to a service server, the device comprising: a first receiving unit and a selecting unit which are positioned at the MME side; wherein,

5. The apparatus of claim 4, wherein the proximity service server identification information comprises: the name of the adjacent service server, the identification of the adjacent service server, the name of the access point of the adjacent service server and the address of the adjacent service server.

6. The apparatus of claim 4, wherein the capability information for the user to sign up for authorization to use the proximity service comprises: different operator networks authorize at least one of the ability to use nearby services, enable/disable discovery information or discovery information by one operator network user.

7. A method for registering a user with a proximity service server, the method comprising:

8. The method of claim 7, further comprising: and the MME deletes the user context information stored on the adjacent service server through a logout message, and the MME deletes the adjacent service information of the UE through a downlink NAS message.

9. The method of claim 7, further comprising: and when the UE receives the message of distributing/updating/deleting the Prose ID, the binding relation of the application layer ID, the Prose ID and the Prose Server ID is registered/updated/deleted on the application Server.

10. The method according to claim 7, 8 or 9, wherein the Prose ID is an identifier for identifying a user in an adjacent service discovery or communication process.

11. The method according to claim 8, wherein the user context information stored on the proximity service server includes at least one of MME identification attached to the user, capability information of the user authorizing the use of proximity service, Prose ID, and proximity service discovery information.

12. The method according to claim 7, 8 or 9, wherein the downstream NAS message comprises: and the MME sends any one of an attach accept message, a tracking area update accept message and a newly defined Prose ID allocation message to the UE.

13. The method according to claim 7, 8 or 9, wherein the trigger 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 is changed, or the capability information of the user signing and authorizing the use of the adjacent service in the signing information is changed.

14. The method of claim 8, wherein the trigger condition for the MME to send the deregistration 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 of claim 7, 8 or 9, further comprising: when the MME serving the user is changed, the new MME needs to acquire the identification information of the adjacent service server in the old MME, and the new MME sends the MME identification attached to the user and the capability information of the user signing and authorizing the use of the adjacent service to the adjacent service server through a registration/update message.

16. The method of claim 8, further comprising: the MME deletes the user context information stored on the adjacent service server through the logout message, deactivates the adjacent service of the UE through the attachment acceptance message, the tracking area update acceptance message, the logout request/acceptance message and the defined Prose ID deletion message, and deletes the information related to the adjacent service in the UE.

17. An apparatus for registering a user with a proximity service server, the apparatus comprising: the second receiving unit and the first registration distributing unit are positioned at the side close to the service server; wherein,

18. The apparatus of claim 17, wherein the second receiving unit is further configured to receive a deregistration message sent by an MME;

19. The apparatus of claim 18, wherein the first deregistration unit is further configured to, after deleting the user context information stored in the proximity service server, notify the MME to deactivate the proximity service of the UE through an attach accept message, a tracking area update accept message, a deregistration request/accept message, and a defined Prose ID delete message, thereby deleting the proximity service related information in the UE.

20. The apparatus of claim 17, wherein the second receiving unit is further configured to receive, when an MME serving the user changes and the new MME needs to obtain the proximity service server identification information in the old MME, capability information that the new MME identifies the MME to which the user is attached and the user signs up to authorize the user to use the proximity service through a registration/update message.

21. A method for registering a user with a proximity service server, the method comprising:

22. The method of claim 21, further comprising: and the adjacent service server deletes the adjacent service information of the UE through the direct interface.

23. The method of claim 21, further comprising: and when the UE receives the message of distributing/updating/deleting the Prose ID, the binding relation of the application layer ID, the Prose ID and the Prose Server ID is registered/updated/deleted on the application Server.

24. The method of claim 21, 22 or 23, further comprising: and the MME selects an adjacent service Server according to the Prose Server ID of the subscription information in the HSS and informs the UE through the NAS message.

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

26. The method of claim 24, wherein the NAS message comprises: any one of an attach accept message, a tracking area update accept message, and a newly defined Prose ID assignment message.

27. An apparatus for registering a user with a proximity service server, the apparatus comprising: the device includes: a third receiving unit and a second registration distributing unit which are positioned at the side close to the service server; wherein,

28. The apparatus of claim 27, further comprising: and the second cancellation unit is used for notifying the UE to delete the adjacent service information of the UE through the direct interface.

29. The apparatus of claim 28, wherein the direct interface carries a control plane interface on a user plane.