CN116866844A

CN116866844A - Communication method and device

Info

Publication number: CN116866844A
Application number: CN202210315174.1A
Authority: CN
Inventors: 姚琦; 朱强华
Original assignee: Huawei Technologies Co Ltd
Current assignee: Huawei Technologies Co Ltd
Priority date: 2022-03-28
Filing date: 2022-03-28
Publication date: 2023-10-10

Abstract

The application provides a communication method and a communication device, belongs to the technical field of communication, and is used for guaranteeing service experience of group members. In the method, since the service range or the internal range of the group can indicate the group member to obtain the limited area of the service provided by the application network element, that is, the group member can obtain the service provided by the application network element only within the limited area, otherwise, the group member cannot obtain the service provided by the application network element. Therefore, the group members obtaining the service can be ensured to be positioned in the limited area where the application network element provides the service, and the group members can be ensured to obtain consistent service experience.

Description

Communication method and device

Technical Field

The present application relates to the field of communications, and in particular, to a communication method and apparatus.

Background

The fifth generation (5th generation,5G) local area network (5G local area network,5G LAN), also referred to as the 5G virtual network (5G virtual network,5G VN), is commonly used in home communications, business offices, factory manufacturing, internet of vehicles, grid modification, and public security authorities. A 5G VN is a group service provided by a 5G network. For example, a 5G VN can provide private communications based on internet protocol (internet protocol, IP) type, or non-IP type (e.g. ethernet type) protocols for two or more terminals in a group (group members), i.e. communications that do not need to be forwarded through a 5G core,5gc, to reduce communication latency.

However, in the 5G network and the subsequent evolution communication system, new group communication scenarios, such as multi-person interactive games, multi-person autopilot fleet, etc., appear, and group members are required to acquire corresponding application data from application functions (application function, AF) to realize interactive interaction. In this case, the distance between the group member and the AF may affect the service experience of the group member. For example, for group members closer to the AF, their communication latency with the AF is lower and the service experience is better. However, for group members farther from the AF, their communication latency with the AF is higher and the service experience is worse. Therefore, how to ensure that group members can obtain consistent service experience is currently being addressed.

Disclosure of Invention

The embodiment of the application provides a communication method and a communication device, which are used for guaranteeing that group members can obtain consistent service experience.

In order to achieve the above purpose, the application adopts the following technical scheme:

in a first aspect, a communication method is provided. The method comprises the following steps: the capability open network element receives the group creation request message #1 from the application network element, and sends a group creation request message #2 to the core network element according to the group creation request message # 1. The core network element receives the group creation request message #2 from the capability open network element to associate and store the group identity, the group member and the internal scope of the group. The group creation request message #1 includes a group identifier, a group member included in a group corresponding to the group identifier, and a service range of the group, where the service range is used to indicate the group member to obtain a restricted area of the service provided by the application network element. The group creation request message #2 includes a group identification, a group member, and an internal range for indicating the group member to acquire a restricted area of the service provided by the application network element.

According to the method of the first aspect, it is known that, since the service scope or the internal scope of the group may indicate the restricted area where the group member obtains the service provided by the application network element, that is, the group member can obtain the service provided by the application network element only within the restricted area, otherwise, the group member cannot obtain the service provided by the application network element. Therefore, the group members obtaining the service can be ensured to be positioned in the limited area where the application network element provides the service, and the group members can be ensured to obtain consistent service experience.

In one possible design, the internal scope is mapped by the service scope, where the internal scope is a scope that can be identified by the operator network or the core network, so as to avoid failure in group creation due to failure of the operator network or the core network to identify the service scope. Alternatively, the internal range may be the same as the service range, i.e. the service range is originally a range that the operator network or the core network can identify. In this case, the capability open network element does not need to do mapping, so as to save the overhead of the capability open network element.

In one possible design, the service scope of the group is the service scope of the application network element. That is, the service scope of the group can be determined according to the existing service scope of the application network element, and the service scope does not need to be additionally configured for the application network element, so that the configuration complexity of the application network element is reduced, and the deployment is convenient and flexible.

Optionally, the application network element comprises at least one of: one or more edge application servers EAS, or one or more edge enabling servers EES to which EAS corresponds. The service scope of the application network element comprises at least one of the following: a set of service areas for one or more EAS, or a service area for EES. In this case, multiple EAS can provide service for the group through load balancing, so that the service experience of the user is better. In addition, the EAS can share the service range of the EES (i.e., the service range of the group is the service range of the EES), so that the service range does not need to be additionally configured for each EAS, the configuration complexity of the EAS is reduced, and the EAS is convenient and flexible to deploy.

In one possible embodiment, the service area is characterized by at least one of the following information: geographic location information, or network location information. That is, the application network element may select the representation mode of the service range according to the capability of the capability-releasing network element, so as to ensure that the capability-releasing network element can identify the service range. For example, if the capabilities of the capability-releasing network element support a geographic location, the application network element may characterize the service scope with geographic location information. For example, the geographic location information includes at least one of: geographic identification information, or latitude and longitude information. Alternatively, if the capability of the capability-releasing network element supports network location, the application network element may characterize the service scope with network location information. For example, the network location information includes at least one of: a data network access identifier DNAI, a track area identity TAI, a TAI list, an area identity list, a cell identity, or a cell identity list.

Optionally, the method of the first aspect may further include: the capability opening network element sends a subscription message for the position change to the mobility management network element corresponding to the group member, and receives a notification message for the position change from the mobility management network element. The subscription message carries an internal scope, and the notification message is used for indicating the relationship between the position of the group member and the internal scope. For example, the relationship of the group member's location to the internal range may include any one or more of the following: group members move into an internal range; group members move out of the internal range; group members are within an internal range; or the group members are out of internal range. Therefore, the capability opening network element can timely and accurately know whether the group member is located in the internal range or not, or know the event that the group member moves into or moves out of the internal range.

Or, alternatively, the method of the first aspect may further include: the capability opening network element sends a subscription message for the position change to the mobility management network element corresponding to the group member, and receives a notification message for the position change from the mobility management network element. The subscription message carries a service scope, and the notification message is used for indicating the relationship between the position of the group member and the service scope. For example, the relationship of the group member's location to the service scope includes any one or more of the following: group members move into service range; group members move out of service; group members are within service; alternatively, the group members are out of service. Thus, the capability opening network element can timely and accurately know whether the group member is located in the service range or not, or know the event that the group member moves into or out of the service range.

Further, the method of the first aspect may further include: the capability opening network element sends a notification message of the position change to the application network element, and receives a group update request message #1 from the application network element, so as to send a group update request message #2 to the core network element according to the group update request message # 1. The group update request message #1 is used for requesting to update the group, and the update request message #2 is used for requesting to update the group. It can be seen that the capability open network element does not directly transmit the group update request message #1, but converts the group update request message #1 into a message that can be identified by the core network element, such as the group update request message #2, so as to avoid failure of group update caused by the identification of the group update request message by the core network element.

Optionally, the method of the first aspect may further include: the capability opening network element sends a group update request message #2 to the core network element according to the notification message of the position change. The group update request message #2 is used for requesting to update the group; that is, the capability opening network element may directly request the core network element to update the group without going through the application network element, so as to reduce the communication delay.

Optionally, the method of the first aspect may further include: the capability opening network element receives the position change notification indication information from the application network element. The location change notification indication information is used for indicating the location change condition of the capability opening network element subscription group member. In this way, the capability opening network element can send the subscription message of the position change to the mobility management network element corresponding to the group member according to the position change notification indication information, so as to ensure that the capability opening network element can know whether the group member is located within the service range. Of course, the capability opening network element may send the subscription message of the location change to the mobility management network element corresponding to the group member by default, which is not limited specifically.

In one possible design, the capability-releasing network element sends a group creation request message #2 to the core network element according to the group creation request message #1, including: the capability open network element determines the type of the group according to the group creation request message #1, and sends a group creation request message #2 to the core network element according to the type of the group. That is, for different types of groups, different core network elements can provide services to realize differentiated services, and the requirements of each group are matched. For example, for temporary groups, dynamic groups, etc., services may be provided by policy control network elements. For a fifth generation lan 5G VN, services may be provided by data storage network elements.

Optionally, the group creation request message #1 carries group type indication information, where the group type indication information is used to indicate a group type, so that the capability open network element can accurately know the group type. Of course, the type of the group may be indicated by other means, such as implicitly indicating the type of the group by the type of the group creation request message #1, which is not particularly limited.

Optionally, the type of group is a temporary group or a dynamic group. It should be noted that, since the randomness of the temporary group or the dynamic group is relatively strong, for example, the location of the group member often changes, even the group member often changes, so that the service scope needs to be limited to ensure the service quality of the temporary group.

In one possible implementation manner, the method of the first aspect may further include: the core network element updates the group according to the relationship between the position of the group member and the internal range, so as to ensure that the group member positioned in the internal range can obtain the service provided by the application network element.

Optionally, the core network element updates the group according to a relationship between a location of the group member and an internal range, including: if the group member is outside the internal range or the group member moves out of the internal range, the core network element deletes the group member or marks the group member as a deactivated state to ensure that the group member can no longer obtain the service provided by the application network element. Or if the group member moves into the service range, the core network element re-adds the group member into the group, or marks the group member as active state, so as to ensure that the group member can regain the service provided by the application network element.

In a possible design, the method of the first aspect may further include: and triggering the session management network element to manage the protocol data unit PDU session corresponding to the group member by the core network element according to the relation between the position of the group member and the internal range. For example, if the group member is out of the internal range or the group member moves out of the internal range, the core network element triggers the session management network element to release the PDU session, or marks the PDU session as a deactivated state, so as to improve the resource utilization of the session management network element and avoid resource waste caused by maintaining redundant PDU sessions. For another example, if the group member is within the service scope, or the group member moves into the service scope, the core network element triggers the session management network element to create a PDU session, or marks the PDU session as active, to ensure that the group member can regain the service provided by the application network element through the PDU session.

Optionally, the method of the first aspect may further include: the core network element sends the subscription information of the position change to the mobility management network element corresponding to the group member, and receives the notification information of the position change from the mobility management network element. The subscription message carries an internal range, and the notification message is used for indicating the relationship between the position of the group member and the internal range, so that the core network element can timely know whether the group member is located in the internal range.

In a possible design, the method of the first aspect may further include: the core network element receives a group update request message #2 from the capability open network element, where the group update request message #2 is used to request to update the group. Thus, the core network element can update the group according to the group update request message # 2. For example, the update group may include at least one of: deleting group members, re-adding group members to a group, marking group members as active, marking group members as inactive, or adding new group members. Thus, the dynamic management of the group can be realized, and the group members in the internal range can be ensured to obtain the service provided by the application network element.

In one possible design, the core network element stores the group identifier, the group member and the internal range in association with each other, including: the core network element stores the group identification, the group members and the internal range into the subscription information or the policy information of the group so as to realize centralized storage and facilitate subsequent inquiry. Or the core network element stores the group identification and the internal range into the subscription information or the policy information of the group members so as to realize distributed storage and improve the utilization rate of the storage space.

It should be noted that, the group identifier stored in the core network element may be an external group identifier or an internal group identifier. The internal group identity may be a group identity that can be identified by the operator network or the core network. Similarly, the group member stored in the core network element may be an external Identifier (ID) of the group member, or may be an internal Identifier (ID) of the group member. The internal identity of the group member may be an identity that can be identified by the operator network or the core network.

In one possible implementation manner, the method of the first aspect may further include: the core network element sends an internal scope to the session management element, which can be used to indicate a restricted area where the session management element is allowed to establish a session, so as to ensure that the session management element can only establish a session for terminals that are within the internal scope. Or the core network element receives the identification of the terminal from the session management network element and indicates to the session management network element whether the terminal is in the internal range according to the identification of the terminal, so as to ensure that the session management network element allows the terminal to establish the session only if the terminal is in the internal range.

In one possible embodiment, the core network element is a data storage network element or a policy control network element.

In a second aspect, a communication method is provided. The method comprises the following steps: the capability open network element receives the group creation request message #1 from the application network element, and triggers management of the group according to the group creation request message # 1. The group creation request message comprises a #1 group identifier, group members included in a group corresponding to the group identifier, and a service range of the group; the service scope is used for indicating the group member to acquire the limited area of the service provided by the application network element.

In one possible design, the service scope of the group may be the service scope of the application network element.

Optionally, the application network element may include at least one of: one or more edge application servers EAS, or one or more edge enabling servers EES to which EAS corresponds. The service scope of the application network element comprises at least one of the following: a set of service areas for one or more EAS, or a service area for EES.

In one possible embodiment, the service area can be characterized by at least one of the following information: geographic location information, or network location information. Optionally, the geographic location information may include at least one of: geographic identification information, or latitude and longitude information. Optionally, the network location information may include at least one of: DNAI, TAI, TAI list, area identity list, cell identity, or cell identity list.

In one possible design, the capability openness network element triggers management of the group according to the group creation request message #1, including: the capability opening network element maps the service range to an internal range which can be identified by the operator network or the core network, and sends the group identifier, the group member and the internal range to the core network element, wherein the internal range is used for indicating the group member to acquire the limited area of the service provided by the application network element.

Optionally, the method of the second aspect may further include: the capability opening network element sends a subscription message for the position change to the mobility management network element corresponding to the group member, and receives a notification message for the position change from the mobility management network element. The subscription message carries an internal scope, and the notification message is used for indicating the relationship between the position of the group member and the internal scope.

Further, the relationship of the group member's location to the internal range includes any one or more of the following: group members move into an internal range; group members move out of the internal range; group members are within an internal range; alternatively, the group members are outside the internal range.

Or, in another possible design, the capability opening network element triggers management of the group according to the group creation request message #1, including: the capability opening network element sends the group identification, the group members and the service range of the group to the core network element.

Optionally, the method of the second aspect may further include: the capability opening network element sends a subscription message for the position change to the mobility management network element corresponding to the group member, and receives a notification message for the position change from the mobility management network element. The subscription message carries a service scope, and the notification message is used for indicating the relationship between the position of the group member and the service scope.

Further, the relationship between the location of the group member and the service scope includes any one or more of the following: group members move into service range; group members move out of service; group members are within service; alternatively, the group members are out of service.

Further, the method of the second aspect may further include: the capability opening network element sends a notification message of the position change to the application network element, and receives a group update request message #1 from the application network element, so as to send a group update request message #2 to the core network element according to the group update request message # 1. Wherein, the group update request message #1 is used for requesting to update the group, and the update request message #2 is also used for requesting to update the group.

Optionally, the method of the second aspect may further include: the capability opening network element sends a group update request message #2 to the core network element according to the notification message of the position change. The group update request message #2 is used to request update of the group.

Optionally, the method of the second aspect may further include: the capability opening network element receives the position change notification indication information from the application network element. The location change notification indication information is used for indicating the location change condition of the capability opening network element subscription group member.

Further, the other technical effects of the communication method described in the second aspect may refer to the technical effects of the communication method described in the first aspect, and are not described herein.

In a third aspect, a communication method is provided. The method comprises the following steps: the core network element receives the group creation request message #2 from the capability open network element. The group creation request message #2 includes a group identifier, a group member included in a group corresponding to the group identifier, and an internal range of the group. The internal range is used to indicate a restricted area for group members to obtain services provided by the application network element. In this way, the core network element associates and stores the group identity, group members and internal scope.

In a possible design, the method of the third aspect may further include: and the core network element updates the group according to the relationship between the positions of the group members and the internal range.

Optionally, the core network element updates the group according to a relationship between a location of the group member and an internal range, including: if the group member is outside the internal range, or the group member moves out of the internal range, the core network element deletes the group member, or marks the group member as a deactivated state. Alternatively, if the group member moves into service, the core network element re-adds the group member into the group, or marks the group member as active.

In a possible design, the method of the third aspect may further include: and triggering the session management network element to manage the PDU session corresponding to the group member by the core network element according to the relation between the position of the group member and the internal range. Optionally, if the group member is outside the internal range, or the group member moves out of the internal range, the core network element triggers the session management network element to release the PDU session, or marks the PDU session as a deactivated state. Optionally, if the group member is within the service scope, or the group member moves into the service scope, the core network element triggers the session management network element to create a PDU session, or marks the PDU session as an active state.

Optionally, the method of the third aspect may further include: the core network element sends the subscription information of the position change to the mobility management network element corresponding to the group member, and receives the notification information of the position change from the mobility management network element. The subscription message carries an internal scope, and the notification message is used for indicating the relationship between the position of the group member and the internal scope.

In a possible design, the method of the third aspect may further include: the core network element receives a group update request message #2 from the capability open network element, where the group update request message #2 is used to request to update the group. Thus, the core network element can update the group according to the group update request message # 2. For example, the update group may include at least one of: deleting group members, re-adding group members to a group, marking group members as active, marking group members as inactive, or adding new group members.

In one possible design, the core network element stores the group identifier, the group member and the internal range in association with each other, including: the core network element stores the group identifier, the group member and the internal range into the subscription information or policy information of the group. Or the core network element stores the group identification and the internal range into the subscription information or the policy information of the group members.

In a possible design, the method of the third aspect may further include: the core network element sends the internal scope to the session management network element. Or the core network element receives the identification of the terminal from the session management network element and indicates whether the terminal is in an internal range to the session management network element according to the identification of the terminal.

Further, the other technical effects of the communication method described in the third aspect may refer to the technical effects of the communication method described in the first aspect, and are not described herein.

In a fourth aspect, a communication system is provided. The system comprises: capability open network elements and core network elements.

The capability opening network element is configured to receive a group creation request message #1 from the application network element, and send a group creation request message #2 to the core network element according to the group creation request message # 1. A core network element for receiving a group creation request message #2 from the capability open network element, thereby storing the group identification, the group member and the internal range of the group in association. The group creation request message #1 includes a group identifier, a group member included in a group corresponding to the group identifier, and a service range of the group, where the service range is used to indicate the group member to obtain a restricted area of the service provided by the application network element. The group creation request message #2 includes a group identification, a group member, and an internal range for indicating the group member to acquire a restricted area of the service provided by the application network element.

In one possible design, the internal range may be the same as the service range. Alternatively, the internal scope is mapped by the service scope, and the internal scope is a scope that can be identified by the operator network or the core network.

In one possible design, the service scope of the group is the service scope of the application network element.

Optionally, the application network element comprises at least one of: one or more edge application servers EAS, or one or more edge enabling servers EES to which EAS corresponds. The service scope of the application network element comprises at least one of the following: a set of service areas for one or more EAS, or a service area for EES.

In one possible embodiment, the service area is characterized by at least one of the following information: geographic location information, or network location information. Optionally, the geographic location information may include at least one of: geographic identification information, or latitude and longitude information. Optionally, the network location information may include at least one of: DNAI, TAI, TAI list, area identity list, cell identity, or cell identity list.

Optionally, the capability opening network element is further configured to send a subscription message for location change to a mobility management network element corresponding to the group member, and receive a notification message for location change from the mobility management network element. The subscription message carries an internal scope, and the notification message is used for indicating the relationship between the position of the group member and the internal scope. For example, the relationship of the group member's location to the internal range may include any one or more of the following: group members move into an internal range; group members move out of the internal range; group members are within an internal range; alternatively, the group members are outside the internal range.

Optionally, the capability opening network element is further configured to send a subscription message for location change to a mobility management network element corresponding to the group member, and receive a notification message for location change from the mobility management network element. The subscription message carries a service scope, and the notification message is used for indicating the relationship between the position of the group member and the service scope. For example, the relationship of the group member's location to the service scope includes any one or more of the following: group members move into service range; group members move out of service; group members are within service; alternatively, the group members are out of service.

Further, the capability open network element is further configured to send a notification message of the location change to the application network element, and receive a group update request message #1 from the application network element, so that a group update request message #2 is sent to the core network element according to the group update request message # 1. The group update request message #1 is used for requesting to update the group, and the update request message #2 is used for requesting to update the group.

Optionally, the capability open network element is further configured to send a group update request message #2 to the core network element according to the notification message of the location change. The group update request message #2 is used to request update of the group.

Optionally, the capability open network element is further configured to receive a location change notification indication information from the application network element. The location change notification indication information is used for indicating the location change condition of the capability opening network element subscription group member. In this way, the capability opening network element is further configured to send, according to the location change notification instruction information, a subscription message for location change to the mobility management network element corresponding to the group member.

In a possible design, the capability-open network element is further configured to determine a group type according to the group creation request message #1, and send a group creation request message #2 to the core network element according to the group type.

Optionally, the group creation request message #1 carries group type indication information, where the group type indication information is used to indicate a type of the group.

Optionally, the type of group is a temporary group or a dynamic group.

In a possible design, the core network element is further configured to update the group according to a relationship between the location of the group member and the internal range.

Optionally, if the group member is outside the internal range or the group member moves out of the internal range, the core network element is further configured to delete the group member or mark the group member as a deactivated state. Or if the group member moves into the service range, the core network element is further configured to re-add the group member into the group, or mark the group member as active.

In one possible design, the core network element is further configured to trigger the session management network element to manage the PDU session corresponding to the group member according to the relationship between the position of the group member and the internal range. For example, if the group member is outside the internal scope, or if the group member moves out of the internal scope, the core network element is further configured to trigger the session management network element to release the PDU session, or mark the PDU session as a deactivated state. For another example, if the group member is within the service scope, or if the group member moves into the service scope, the core network element is further configured to trigger the session management network element to create a PDU session, or mark the PDU session as an active state.

Optionally, the core network element is further configured to send a subscription message for the location change to a mobility management network element corresponding to the group member, and receive a notification message for the location change from the mobility management network element. The subscription message carries an internal scope, and the notification message is used for indicating the relationship between the position of the group member and the internal scope.

In a possible design, the core network element is further configured to receive a group update request message #2 from the capability open network element, where the group update request message #2 is used to request updating the group. In this way, the core network element is further configured to update the group according to the group update request message # 2. For example, the update group may include at least one of: deleting group members, re-adding group members to a group, marking group members as active, marking group members as inactive, or adding new group members.

In one possible design, the core network element is further configured to store the group identifier, the group member, and the internal range in subscription information or policy information of the group. Or the core network element is further configured to store the group identifier and the internal range in subscription information or policy information of the group member.

In a possible design, the core network element is further configured to send the internal range to the session management network element. Or the core network element is further configured to receive the identifier of the terminal from the session management network element, and indicate, to the session management network element, whether the terminal is in the internal range according to the identifier of the terminal.

Further, the technical effects of the communication system described in the fourth aspect may refer to the technical effects of the communication method described in the first aspect, and will not be described herein.

In a fifth aspect, a communication device is provided. The device comprises: the module for performing the communication method of the first aspect, for example, a transceiver module and a processing module.

The receiving and transmitting module is used for receiving a group creation request message #1 from the application network element. And the processing module is used for triggering the management of the group according to the group creation request message #1. The group creation request message comprises a #1 group identifier, group members included in a group corresponding to the group identifier, and a service range of the group; the service scope is used for indicating the group member to acquire the limited area of the service provided by the application network element.

In one possible design, the processing module is further configured to map the service range to an internal range that can be identified by the operator network or the core network, and control the transceiver module to send the group identifier, the group member, and the internal range to the core network element, where the internal range is used to instruct the group member to obtain the restricted area of the service provided by the application network element.

Optionally, the transceiver module is further configured to send a subscription message for location change to a mobility management network element corresponding to the group member, and receive a notification message for location change from the mobility management network element. The subscription message carries an internal scope, and the notification message is used for indicating the relationship between the position of the group member and the internal scope.

Or the processing module is further used for controlling the receiving and transmitting module to send the group identification, the group member and the service range of the group to the core network element.

Optionally, the transceiver module is further configured to send a subscription message for location change to a mobility management network element corresponding to the group member, and receive a notification message for location change from the mobility management network element. The subscription message carries a service scope, and the notification message is used for indicating the relationship between the position of the group member and the service scope.

Further, the transceiver module is further configured to send a notification message of the location change to the application network element, and receive a group update request message #1 from the application network element; the processing module is further configured to control the transceiver module to send a group update request message #2 to the core network element according to the group update request message # 1. Wherein, the group update request message #1 is used for requesting to update the group, and the update request message #2 is also used for requesting to update the group.

Optionally, the processing control is further configured to control the transceiver module to send a group update request message #2 to the core network element according to the notification message of the location change. The group update request message #2 is used to request update of the group.

Optionally, the transceiver module is further configured to receive location change notification indication information from the application network element. The location change notification indication information is used for indicating the location change condition of the capability opening network element subscription group member.

Alternatively, the transceiver module may include a transmitting module and a receiving module. The sending module is used for realizing the sending function of the communication device according to the third fifth aspect, and the receiving module is used for realizing the receiving function of the communication device according to the fifth aspect.

Optionally, the communication device according to the fifth aspect may further include a storage module, where the storage module stores a program or instructions. The processing module, when executing the program or instructions, causes the communication device to perform the communication method described in the second aspect.

The communication apparatus according to the fifth aspect may be a network device, such as an energy-saving network element, a chip (system) or other parts or components that may be disposed in the network device, or an apparatus including the network device, which is not limited in this aspect of the present application.

Further, the technical effects of the communication apparatus according to the fifth aspect may refer to the technical effects of the communication method according to the second aspect, and will not be described herein.

In a sixth aspect, a communication device is provided. The device comprises: a module for performing the communication method according to the third aspect, for example, a transceiver module and a processing module.

The receiving and transmitting module is used for receiving a group creation request message #2 from the capability opening network element. The group creation request message #2 includes a group identifier, a group member included in a group corresponding to the group identifier, and an internal range of the group. The internal range is used to indicate a restricted area for group members to obtain services provided by the application network element. In this way, the processing module is configured to store the group identifier, the group member, and the internal scope in association.

In one possible design, the processing module is further configured to update the group according to a relationship between the location of the group member and the internal range.

Optionally, if the group member is outside the internal range or the group member moves out of the internal range, the processing module is further configured to delete the group member or mark the group member as a deactivated state. Alternatively, if the group member moves into the service area, the processing module is further configured to re-add the group member into the group, or mark the group member as active.

In one possible design, the processing module is further configured to trigger the session management network element to manage the PDU session corresponding to the group member according to the relationship between the position of the group member and the internal range. Optionally, if the group member is out of the internal range or the group member moves out of the internal range, the processing module is further configured to trigger the session management network element to release the PDU session or mark the PDU session as a deactivated state. Optionally, if the group member is within the service scope or the group member moves into the service scope, the processing module is further configured to trigger the session management network element to create a PDU session, or mark the PDU session as an active state.

In a possible design, the transceiver module is further configured to receive a group update request message #2 from the capability-open network element, where the group update request message #2 is used to request updating the group. Thus, the processing module is further configured to update the group according to the group update request message # 2. For example, the update group may include at least one of: deleting group members, re-adding group members to a group, marking group members as active, marking group members as inactive, or adding new group members.

In one possible design, the processing module is further configured to store the group identifier, the group member, and the internal range in subscription information or policy information of the group. Or the processing module is further used for storing the group identifier and the internal range into subscription information or policy information of the group members.

In a possible design, the transceiver module is further configured to send the internal range to the session management network element. Or, the transceiver module is further used for receiving the identification of the terminal from the session management network element; the processing module is further used for controlling the receiving and transmitting module to indicate whether the terminal is in an internal range to the session management network element according to the identification of the terminal.

Alternatively, the transceiver module may include a transmitting module and a receiving module. The transmitting module is configured to implement a transmitting function of the communication device according to the sixth aspect, and the receiving module is configured to implement a receiving function of the communication device according to the sixth aspect.

Optionally, the communication device according to the sixth aspect may further include a storage module, where the storage module stores a program or instructions. The processing module, when executing the program or instructions, enables the communication device to perform the communication method according to the third aspect.

It should be noted that the communication apparatus according to the sixth aspect may be a network device, such as a core network element, for example, a data storage network element or a policy control network element, or may be a chip (system) or other parts or components that may be disposed in the network device, or may be an apparatus including the network device, which is not limited in this disclosure.

Further, the technical effects of the communication apparatus according to the sixth aspect may refer to the technical effects of the communication method according to the first aspect, and will not be described herein.

In a seventh aspect, a communication device is provided. The communication device includes: a processor configured to perform the communication method according to the second or third aspect.

In one possible configuration, the communication device according to the seventh aspect may further comprise a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be for use in a communication device according to the seventh aspect to communicate with other communication devices.

In one possible configuration, the communication device according to the seventh aspect may further comprise a memory. The memory may be integral with the processor or may be separate. The memory may be used for storing computer programs and/or data related to the communication method according to the second or third aspect.

In the present application, the communication apparatus according to the seventh aspect may be the network device according to the second or third aspect, or a chip (system) or other part or component that may be provided in the terminal, or an apparatus including the terminal.

Further, the technical effects of the communication apparatus according to the seventh aspect may refer to the technical effects of the communication method according to the first aspect, and will not be described herein.

In an eighth aspect, a communication device is provided. The communication device includes: a processor coupled to the memory, the processor being configured to execute a computer program stored in the memory to cause the communication device to perform the communication method according to the second or third aspect.

In one possible configuration, the communication device according to the eighth aspect may further comprise a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be for use in a communication device according to the eighth aspect to communicate with other communication devices.

In the present application, the communication apparatus according to the eighth aspect may be the network device according to the second aspect or the third aspect, or may be a chip (system) or other part or component provided in the network device, or an apparatus including the network device.

Further, the technical effects of the communication apparatus according to the eighth aspect may refer to the technical effects of the communication method according to the first aspect, and will not be described herein.

In a ninth aspect, there is provided a communication apparatus comprising: a processor and a memory; the memory is for storing a computer program which, when executed by the processor, causes the communication device to perform the communication method according to the second or third aspect.

In one possible configuration, the communication device according to the ninth aspect may further comprise a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be for use in a communication device according to the ninth aspect to communicate with other communication devices.

In the present application, the communication apparatus according to the ninth aspect may be the network device according to the second aspect or the third aspect, or may be a chip (system) or other part or component provided in the network device, or an apparatus including the network device.

Further, the technical effects of the communication apparatus according to the ninth aspect may refer to the technical effects of the communication method according to the first aspect, and will not be described herein.

In a tenth aspect, there is provided a communication apparatus comprising: a processor; the processor is configured to execute the communication method according to the second or third aspect according to the computer program after being coupled to the memory and reading the computer program in the memory.

In one possible configuration, the communication device according to the tenth aspect may further comprise a transceiver. The transceiver may be a transceiver circuit or an interface circuit. The transceiver may be for use in a communication device according to the eighth aspect to communicate with other communication devices.

In the present application, the communication apparatus according to the tenth aspect may be the network device according to the second aspect or the third aspect, or may be a chip (system) or other part or component provided in the network device, or an apparatus including the network device.

Further, the technical effects of the communication apparatus according to the tenth aspect may refer to the technical effects of the communication method according to the second or third aspect, and will not be described here.

In an eleventh aspect, there is provided a computer-readable storage medium comprising: computer programs or instructions; the computer program or instructions, when run on a computer, cause the computer to perform the communication method of any of the first to third aspects.

In a twelfth aspect, there is provided a computer program product comprising a computer program or instructions which, when run on a computer, cause the computer to perform the communication method of any of the first to third aspects.

Drawings

FIG. 1 is a schematic diagram of a 5G system architecture;

FIG. 2 is a flow diagram of a 5G LAN;

fig. 3 is a schematic diagram of a communication system according to an embodiment of the present application;

fig. 4 is a schematic flow chart of a communication method according to an embodiment of the present application;

fig. 5 is a second schematic flow chart of a communication method according to an embodiment of the present application;

fig. 6 is a flow chart of a communication method according to an embodiment of the present application;

fig. 7 is a flow chart of a communication method according to an embodiment of the present application;

Fig. 8 is a flow chart of a communication method according to an embodiment of the present application;

fig. 9 is a schematic structural diagram of a communication device according to an embodiment of the present application;

fig. 10 is a schematic diagram of a communication device according to an embodiment of the present application.

Detailed Description

For convenience of understanding, technical terms related to the embodiments of the present application are first described below.

1. Fifth generation (5th generation,5G) mobile communication systems (5G systems, 5gs for short):

fig. 1 is a schematic diagram of a 5GS non-roaming architecture. As shown in fig. 1, 5GS includes: access Networks (ANs) and Core Networks (CNs), may further include: and (5) a terminal.

The terminal may be a terminal having a transceiver function, or a chip system that may be provided in the terminal. The terminal may also be referred to as a User Equipment (UE), an access terminal, a subscriber unit (subscriber unit), a subscriber station, a Mobile Station (MS), a remote station, a remote terminal, a mobile device, a user terminal, a wireless communication device, a user agent, or a user device. The terminals in embodiments of the present application may be mobile phones (mobile phones), cellular phones (cellular phones), smart phones (smart phones), tablet computers (pads), wireless data cards, personal digital assistants (personal digital assistant, PDAs), wireless modems (modems), handheld devices (handsets), laptop computers (lap computers), machine type communication (machine type communication, MTC) terminals, computers with wireless transceiving functions, virtual Reality (VR) terminals, augmented reality (augmented reality, AR) terminals, wireless terminals in industrial control (industrial control), wireless terminals in unmanned aerial vehicle (self driving), wireless terminals in smart grid (smart grid), wireless terminals in transportation security (transportation safety), wireless terminals in smart city (smart city), wireless terminals in smart home (smart home), roadside units with functions, RSU, etc. The terminal of the present application may also be an in-vehicle module, an in-vehicle part, an in-vehicle chip, or an in-vehicle unit built in a vehicle as one or more parts or units.

The AN is used for realizing the function related to access, providing the network access function for authorized users in a specific area, and determining transmission links with different qualities according to the level of the users, the service requirements and the like so as to transmit user data. The AN forwards control signals and user data between the terminal and the CN. The AN may include: an access network device, which may also be referred to as a radio access network device (radio access network, RAN) device. The CN is mainly responsible for maintaining subscription data of the mobile network and providing session management, mobility management, policy management, security authentication and other functions for the terminal. The CN mainly comprises the following network elements: user plane function (user plane function, UPF) network elements, authentication service function (authentication server function, AUSF) network elements, access and mobility management function (access and mobility management function, AMF) network elements, session management function (session management function, SMF) network elements, network slice selection function (network slice selection function, NSSF) network elements, network opening function (network exposure function, NEF) network elements, network function warehousing function (NF repository function, NRF) network elements, policy control function (policy control function, PCF) network elements, unified data management (unified data management, UDM) network elements, unified data storage (unified data repository, UDR), and application function (application function, AF).

As shown in fig. 1 (a), a UE accesses a 5G network through RAN equipment, and the UE communicates with an AMF network element through an N1 interface (abbreviated as N1); the RAN network element communicates with the AMF network element through an N2 interface (N2 for short); the RAN network element communicates with the UPF network element through an N3 interface, namely N3; the SMF communicates with a UPF network element through an N4 interface (abbreviated as N4), and the UPF network element accesses a Data Network (DN) through an N6 interface (abbreviated as N6). In addition, control plane functions such as an AUSF network element, an AMF network element, an SMF network element, an NSSF network element, a NEF network element, an NRF network element, a PCF network element, a UDM network element, a UDR network element, or an AF shown in (a) in fig. 1 use a service interface to interact. For example, the server interface provided by the AUSF network element is Nausf; the AMF network element provides a service interface as Namf; the SMF network element provides a serving interface as Nsmf; the NSSF provides a service interface for the outside as Nnssf; the network element of NEF provides a service interface for the outside as Nnef; the service interface externally provided by the NRF network element is Nnrf; the service interface externally provided by the PCF network element is an Npcf; the service interface externally provided by the UDM network element is Nudm; the server interface externally provided by the UDR network element is Nudr; the service interface provided by the AF is Naf. In addition, as shown in (b) in fig. 1, NSSF network elements, AUSF network elements, UDM network elements, UE, RAN network elements, PCF network elements, SMF network elements, and other network elements can also communicate with AMF network elements. The AUSF network element can also communicate with a UDM network element, the UDM can also communicate with an SMF network element, and the SMF network element can also communicate with a UPF network element and a PCF network element in addition to the AMF network element and the UDM network element. The PCF network element is also capable of communicating with AF and NEF network elements. The NEF network element is also capable of communicating with the AF. The UPF network element is capable of communicating with RAN devices and DNs. As shown in fig. 1 (b), a "Nxx" between two network elements represents an interface between the two network elements. For example, N22 represents an interface between an NSSF network element and an AMF network element, N12 represents an interface between an AUSF network element and an AMF network element, N8 represents an interface between a UDM network element and an AMF network element, and so on, which are not listed here.

The RAN device may be a device that provides access to the terminal. For example, the RAN device may include: the next generation mobile communication system, such as a 6G access network device, such as a 6G base station, or in the next generation mobile communication system, the network device may have other naming manners, which are covered by the protection scope of the embodiments of the present application, which is not limited in any way. Alternatively, the RAN device may also include a 5G, such as a gNB in a New Radio (NR) system, or one or a group (including multiple antenna panels) of base stations in the 5G, or may also be a network node, such as a baseband unit (building base band unit, BBU), or a Centralized Unit (CU) or a Distributed Unit (DU), an RSU with a base station function, or a wired access gateway, or a core network element of the 5G, which forms a gNB, a transmission point (transmission and reception point, TRP or transmission point, TP), or a transmission measurement function (transmission measurement function, TMF). Alternatively, the RAN device may also include an Access Point (AP) in a wireless fidelity (wireless fidelity, wiFi) system, a wireless relay node, a wireless backhaul node, various forms of macro base stations, micro base stations (also referred to as small stations), relay stations, access points, wearable devices, vehicle devices, and so on.

The UPF network element is mainly responsible for user data processing (forwarding, receiving, charging, etc.). For example, the UPF network element may receive user data from a Data Network (DN), which is forwarded to the terminal through the access network device. The UPF network element may also receive user data from the terminal through the access network device and forward the user data to the DN. DN network elements refer to the operator network that provides data transmission services for subscribers. Such as the internet protocol (internet protocol, IP) Multimedia Services (IMS), the internet, etc. The DN may be an external network of the operator or a network controlled by the operator, and is configured to provide service to the terminal device.

The AUSF network element is mainly used for executing security authentication of the terminal.

The AMF network element is mainly used for mobility management in a mobile network. Such as user location updates, user registration networks, user handoffs, etc.

The SMF network element is mainly used for session management in a mobile network. Such as session establishment, modification, release. Specific functions are for example assigning internet protocol (internet protocol, IP) addresses to users, selecting UPF network elements providing packet forwarding functions, etc.

The PCF network element mainly supports providing a unified policy framework to control network behavior, provides policy rules for a control layer network function, and is responsible for acquiring user subscription information related to policy decision. The PCF network element may provide policies, such as quality of service (quality of service, qoS) policies, slice selection policies, etc., to the AMF network element, SMF network element.

The NSSF network element is mainly used to select network slices for the terminal.

The NEF network element is mainly used for supporting the opening of capabilities and events.

The UDM network element is mainly used for storing subscriber data, such as subscription data, authentication/authorization data, etc.

The UDR network element is mainly used for storing structured data, and the stored content includes subscription data and policy data, externally exposed structured data and application related data.

AF mainly supports interactions with CN to provide services, such as influencing data routing decisions, policy control functions or providing some services of third parties to the network side.

2. 5G local area network (5G local area network,5G LAN):

the 5G LAN is also called a 5G virtual network (5G virtual network,5G VN), and is generally applied to the fields of home communications, business offices, factory manufacturing, internet of vehicles, power grid transformation, public security authorities, and the like. A 5G VN is a group service provided by a 5G network. For example, a 5G VN can provide private communications based on internet protocol (internet protocol, IP) type, or non-IP type (e.g. ethernet type) protocols for two or more terminals in a group (group members), i.e. communications that do not need to be forwarded through a 5G core,5gc, to reduce communication latency. For example, devices in a factory may form a group, and the group members may send ethernet packets to each other. Alternatively, office equipment (e.g., cell phones, computers or notebook computers, etc.) of all employees in a department of an enterprise may form a group, group members may send IP packets to each other, etc. If the two terminals are not in the same group, they cannot communicate with each other.

To achieve the above functionality, third generation partnership project (3rd Generation Partnership Project,3GPP) technical standard (technical standard, TS) 23.502 defines a method of statically configuring 5G VN groups. For example, fig. 2 is a schematic flow chart of a method for statically configuring a 5G VN group, and as shown in fig. 2, the flow of the method includes the following steps.

S201, the AF sends a NEF parameter configuration creation/Update/deletion request (nnef_parameter provisioning_create/Update/Delete request) message to the NEF network element. Correspondingly, the NEF network element receives the NEF parameter configuration creation/update/deletion request message from the AF.

Wherein the NEF parameter configuration creation/update/deletion request message is used to provide the NEF network element with one or more parameters to be created or updated. For example, the NEF parameter configuration creation/update/deletion request message includes at least one of: external group Identification (ID), 5G VN group data (i.e. 5G-VN configuration parameters), and 5G VN group member management parameters.

The external group ID is used to identify the 5G VN group. For example, a 5G VN group may be identified by a data network name (data network name, DNN)/single network slice selection assistance information (single network slice selection assistance information, S-nsai), so DNN/S-nsai may be the external group ID of that 5G VN group; alternatively, the external group ID may be characterized by AF assignment or other cells, which are not particularly limited.

The 5G VN group member management parameters may include: the list of group member identifications, which may be identified by a common public subscription identifier (generic public subscription identifier, GPSI) or other identifier (e.g., the group member IP address). In general, each member of the 5G VN group member corresponds to a GPSI identification.

The 5G VN group data may comprise at least one of: protocol data unit (protocol data unit, PDU) session type, application description, or information related to secondary authentication/authorization (noted as related information). The PDU session type is that of the 5 GVGN group. The application description may be used to construct a UE routing policy (UE route selection policy, urs) for the 5G VN group members. The related information may include at least one of: the 5G VN group requires secondary authentication/authorization, or addressing information of a Data Network (DN) -authentication, authorization, and accounting (AAA) server, etc.

It will be appreciated that 5G VN group data is generally applicable to the creation flow, i.e. the NEF parameter configuration creation request message generally carries 5G VN group data, and the NEF parameter configuration update/deletion request message may not carry 5G VN group data. Furthermore, for the NEF parameter configuration creation request message, the parameters carried by the message are used to create the 5G VN group, i.e. the GPSI list comprises: identification of all members within the 5G VN group. For the NEF parameter configuration update/delete request message, the parameters carried by the message are used to update/delete members in the 5G VN group, i.e. the GPSI list includes: the identity of members that need to be updated to within the 5G VN group, or the identity of members that need to be deleted from within the 5G VN group.

After the NEF network element receives the NEF parameter configuration creation/update/deletion request message from the AF, the NEF network element may determine whether the NEF has the right to grant the AF providing parameters, for example whether the AF creates/updates/deletes the parameter 5G VN group. If the NEF network element has the right to grant the AF provisioning parameters, the NEF network element performs S202. If the NEF network element does not grant the authority of the AF provisioning parameters, S204 is performed.

S202, the NEF network element sends a UDM parameter configuration creation/Update/deletion request (nudm_ Parameter Provision _create/Update/Delete request) message to the UDM network element. Accordingly, the UDM network element receives a UDM parameter configuration creation/update/deletion request message from the NEF network element.

The UDM parameter configuration creation/update/deletion request message carries the parameters in the NEF parameter configuration creation/update/deletion request message. After the UDM network element receives the UDM parameter configuration creation/update/deletion request message from the NEF network element, the UDM network element may determine whether the UDM network element has the right to grant the AF providing parameters, for example, whether the UDM network element has the right to grant the AF creation/update/deletion parameters 5G VN group. If the UDM network element has the authority to grant the AF providing parameters, the UDM network element configures the corresponding parameters. For example, the UDM network element creates a 5G VN group according to the UDM parameter configuration creation request message, i.e. saves the configuration of the 5G VN group in the UDM parameter configuration creation request message; or, the UDM network element configures an update/delete request message according to the UDM parameters to update or delete members in the 5G VN group. If the UDM network element does not grant the authority of the AF provisioning parameters, the UDM network element directly performs S203.

It is noted that for creating a 5G VN group, a UDM network element may assign an inner group ID to the 5G VN group, which inner group ID corresponds to the outer group ID of the 5G VN group, i.e. the UDM network element maintains the 5G VN group by means of the inner group ID. Furthermore, the UDM network element may parse the GPSI in the parameter configuration creation/update/deletion request message into a user permanent identifier (subscription permanent identifier, SUPI), i.e. the UDM network element maintains members within the 5G VN group by means of the SUPI of the members, such as creating, updating or deleting the corresponding members.

S203, the UDM network element sends a UDM parameter configuration creation/Update/deletion response (nudm_ Parameter Provision _create/Update/Delete response) message to the NEF network element. Accordingly, the NEF network element receives the UDM parameter configuration creation/update/deletion response message from the UDM network element.

The UDM parameter configuration creation/update/deletion response message is used to respond to the UDM parameter configuration creation/update/deletion request message. If the flow fails, the cause value in the UDM parameter configuration create/update/delete response message indicates the reason for the failure, e.g. the UDM network element does not grant the authority for the AF to provide parameters.

S204, the NEF network element sends a NEF parameter configuration creation/Update/deletion response (nudm_parameter provision_create/Update/Delete response) message to the AF. Accordingly, the AF receives the NEF parameter configuration creation/update/deletion response message from the NEF network element.

The NEF parameter configuration creation/update/deletion response message is used to respond to the NEF parameter configuration creation/update/deletion request message. If the flow fails, the cause value in the NEF parameter configuration create/update/delete response message indicates the reason for the failure, e.g., NEF network element does not grant the AF provisioning parameters.

After the 5G VN group is successfully created/updated/deleted, members in the group can directly communicate with other members in the group through UPF network elements (without connecting with an external loopback DN through an N6 interface), so that communication time delay can be reduced, data can not go out of a core network, and data security is ensured. However, for some new group scenarios, such as those of temporary group construction, including multi-person interactive games, multi-person autopilot fleets, etc., it is necessary for members within the group to acquire corresponding application data from AF, such as from a server of the interactive game, a control center of the autopilot fleets, etc., to achieve interactive interaction. At this time, the distance between the group member and the AF may affect the service experience of the group member. For example, for group members closer to the AF, the communication delay between the group members and the AF is lower, and the service experience is better. However, for group members farther from the AF, the communication delay between the group members and the AF is higher, and the service experience is poor. Therefore, how to ensure that group members can obtain consistent service experience is currently being addressed.

In summary, aiming at the technical problems, the embodiment of the application provides the following technical scheme to ensure that group members can obtain consistent service experience. The technical scheme of the application will be described below with reference to the accompanying drawings.

The technical solution of the embodiment of the present application may be applied to various communication systems, such as a wireless fidelity (wireless fidelity, wiFi) system, a vehicle-to-object (vehicle to everything, V2X) communication system, an inter-device (D2D) communication system, a vehicle networking communication system, a 4th generation (4th generation,4G) mobile communication system, such as a long term evolution (long term evolution, LTE) system, a worldwide interoperability for microwave access (worldwide interoperability for microwave access, wiMAX) communication system, a 5th generation (5th generation,5G) mobile communication system, such as a new radio, NR) system, and future communication systems, such as a sixth generation (6th generation,6G) mobile communication system, and the like.

The present application will present various aspects, embodiments, or features about a system that may include a plurality of devices, components, modules, etc. It is to be understood and appreciated that the various systems may include additional devices, components, modules, etc. and/or may not include all of the devices, components, modules etc. discussed in connection with the figures. Furthermore, combinations of these schemes may also be used.

In addition, in the embodiments of the present application, words such as "exemplary," "for example," and the like are used to indicate an example, instance, or illustration. Any embodiment or design described herein as "exemplary" is not necessarily to be construed as preferred or advantageous over other embodiments or designs. Rather, the term use of an example is intended to present concepts in a concrete fashion.

In the embodiment of the present application, "information", "signal", "message", "channel", and "signaling" may be used in a mixed manner, and it should be noted that the meaning of the expression is matched when the distinction is not emphasized. "of", "corresponding" and "corresponding" are sometimes used in combination, and it should be noted that the meanings to be expressed are matched when the distinction is not emphasized. Furthermore, references to "/" in this disclosure may be used to indicate an "or" relationship.

The network architecture and the service scenario described in the embodiments of the present application are for more clearly describing the technical solution of the embodiments of the present application, and do not constitute a limitation on the technical solution provided by the embodiments of the present application, and those skilled in the art can know that, with the evolution of the network architecture and the appearance of the new service scenario, the technical solution provided by the embodiments of the present application is applicable to similar technical problems.

1) Group: a group may be a combination of members having the same attributes. For example, the combination of members that can enjoy the consistency service provided by the application network element may be a combination of all terminal devices located in a specific area. The group may be a 5G VN, or other type of group, such as a temporary group or a dynamic group (a group requiring dynamic management of group members), which is not particularly limited.

2) Internal group ID of group: the internal group ID may refer to an identity that can be identified by a core network (e.g., 5 GC) or a network element (e.g., SMF network element, AMF network element, UDM network element, PCF network element, NEF network element, etc.) within an operator network, and uniquely characterizes the group. The internal group ID may be DNN, S-nsai, or a combination of DNN and S-nsai, or be characterized by other information.

3) External group ID of group: the external group ID may refer to an identification that is identified and uniquely characterizes the group outside the core network or the operator network, e.g., within AF range. The external group ID may be a string, or a random number, etc., or be characterized by other information. It should be noted that the network elements inside the core network or the operator network may not be able to identify the external group ID. The external group ID may have a mapping relationship with the internal group ID.

4) Internal ID of group member: the internal ID of a group member may refer to an identification of a group member within the group that can be identified by a network element within the core network or the operator network. The internal ID of the group member may be SUPI.

5) External ID of group member: the external ID of a group member may refer to an identification of a group member within the group that may be identified and uniquely characterized outside the core network or operator network, e.g., within AF range. The internal ID of the group member may be an IP address, or GPSI. It should be noted that network elements inside the core network or the operator network may not be able to identify the external ID of the group member. The external ID of the group member may have a correspondence with the internal ID of the group member.

6) Service scope of group: the service scope may be used to instruct group members of the group to acquire a restricted area of service provided by the AF. In other words, the group members (UEs) are within service range to obtain the service provided by the AF, such as high-quality application service. Otherwise, if the group member is out of service range, the service provided by the AF cannot be obtained, or only a low-quality application service is obtained. The service scope may be characterized by geometrical (geographical) location information, such as XX province, XX city, XX region, or latitude and longitude range, etc., or may also be characterized by topology (network) location information, such as a data network access identifier (data network access identifier, DNAI), a track area identity (track area identifier, TAI), a TAI list (list), an area ID list, a cell (eell) ID, or a cell ID list, etc., that can be identified by network elements inside the core network or the operator network.

7) Internal range of group: the internal range may also be used to indicate a restricted area for group members of the group to obtain the services provided by the AF. The internal range and the service range may be the same, e.g., both the internal range and the service range may be characterized by the network location information described above. Alternatively, the internal range may be different from the service range, e.g., the service range is characterized by the geographic location information described above, but the internal range is characterized by the network location information described above. At this time, the internal range may be obtained by mapping a core network element, such as a NEF network element, according to the service range, that is, converting the geographic location information into network location information. It should be noted that whether the internal range is the same as the service range refers to whether the characterization manner is the same, and whether the characterization manner is the same or not, the internal range and the service range can be used to indicate the same limitation area.

For convenience of description, in various embodiments of the present application, a limited area corresponding to a group determined by AF may be referred to as a "service range" of the group, and a limited area related to a core network element may be referred to as an "internal range" of the group.

A communication system suitable for use in the embodiment of the present application will be described in detail below by taking the communication system shown in fig. 3 as an example. Fig. 3 is a schematic diagram of a communication system to which the communication method according to the embodiment of the present application is applicable.

As shown in fig. 3, the communication system may be applied to the above 5G system, and mainly includes: AMF network element, UDM network element/PCF network element, NEF network element, and AF, optionally, may further include: UE, and SMF network element. The related functions of the network elements may refer to related descriptions in the 5G system, which are not described herein. In the communication system of the embodiment of the application, when the AF creates the group, the service range corresponding to the group can be provided to the UDM network element/PCF network element through the NEF network element or directly. The UDM/PCF network element or the NEF network element may instruct the AMF network element to perform mobility tracking on the group members based on the service range, so that the UDM/PCF network element dynamically updates the group members, such as deleting or deactivating the group members moving out of the service range or out of the service range, joining devices moving into the service range or within the service range into the group, or activating/rejoining the group members moving into the service range, so as to ensure that only the group members located within the service range can obtain the service provided by the AF, and ensure that the group members can obtain a consistent service experience.

In order to facilitate the understanding of this,

the following describes the interaction flow between each network element in the above communication system in detail through an embodiment of the method in conjunction with fig. 4 to fig. 6.

The communication method provided by the embodiment of the application can be applied to the communication system. In different scenarios, different flows of the communication method may be performed by different devices/network elements in the communication system, which are described in detail below.

Scene 1:

fig. 4 is a schematic flow chart of a communication method according to an embodiment of the present application. In scenario 1, the AF may provide the service scope of the group to the UDM/PCF network element through the NEF network element when creating the group. The UDM network element/PCF network element can instruct the AMF network element to carry out mobility tracking on the group members according to the service range, so that the UDM network element/PCF network element dynamically updates the group members, and only the group members positioned in the service range can be ensured to obtain the service provided by the AF, thereby ensuring that the group members can obtain consistent service experience.

Specifically, as shown in fig. 4, the flow of the communication method is as follows:

s401, the UE reports the identification of the UE to the AF.

The UE may access the 5G network and create a PDU session. The UE may access the AF through the created PDU session so that the AF obtains the identity of the UE, such as the IP address of the UE or the GPSI of the UE. For example, the UE may send a packet of traffic to the AF, the source address of the packet being the IP address of the UE. That is, the AF obtains the identity of the UE in the process of performing service interaction with the UE. For another example, the UE may report the IP address of the UE or the GPSI of the UE to the AF exclusively in the payload (payload) portion of the packet. Optionally, the UE may also send service information corresponding to the UE, such as an identifier of the service, to the AF. The service information may be used to indicate a service type of the UE, so that the AF determines the group in which the UE is located according to the service type of the UE, and the specific implementation principle may refer to the following description in S402, which is not repeated.

AF is used to provide specific services. The AF may be an edge application server (edge application server, EAS) or a control network element for managing one or more EAS, which may be, for example, an edge enabling server (edge enable server, EES). Wherein each EAS may provide one or more services. When the AF is an EES, the services it provides may be the sum of the services it manages for the EAS it manages. Of course, the AF may be any other possible network element, which is not limited in detail.

It will be appreciated that S401 is an optional step, for example, the AF may be preconfigured with the UE identity, or by other means: if the UE identity is obtained from a UDM network element, or if the AF obtains the UE identity from a specific portal, S401 may not be performed.

S402, the AF determines the group to be created, and the service scope of the group.

Wherein if one or more UEs access the AF, the AF may create a corresponding group for the one or more UEs.

In one possible implementation, the AF may determine UEs accessing the AF as the same group, determine or assign a group identification to the UEs. The group identifier may be an external group ID or an internal group ID, which is not particularly limited. Alternatively, in another possible implementation, the AF may determine UEs accessing the same service as the same group, and determine or assign a corresponding one of the group identities for each group. For example, ue#1, ue#2, …, and ue#10 all need to access service #1 provided by AF, and ue#11, ue#12, …, and ue#20 all need to access service #2 provided by AF. In this way, the AF determines 10 UEs ue#1 to ue#10 as group#1, assigns group identification #11 to group#1, and determines 10 UEs ue#11 to ue#2 as group#2, and assigns group identification #22 to group#2. Alternatively, in yet another possible implementation, the AF may subscribe to the 5GC for the location of the UE according to the identity of the UE accessing the service provided by the AF. The AF may cluster UEs according to their locations, thereby determining which UEs belong to the same class of devices. On this basis, the AF may determine each type of device as a group, assign each group or determine a corresponding group identification. For example, AF determines 10 UEs ue#1 to ue#10 as the same class of device and 10 UEs ue#11 to ue#20 as the same class of device by clustering. In this way, the AF determines ue#1 to ue#10 as group#1, and assigns group id#11 to group#1. Similarly, the AF determines UE#11 to UE#20 as group#2, and assigns group identity #22 to group#2.

The service scope of the group may be the service scope of the AF, e.g., a set of service scopes of one or more EAS, or may also be the service scope of the EES. Wherein, the service scope of one EES may be a set of service scopes of multiple EAS. In this case, the service ranges of different groups may be the same, for example, the service ranges of EES, and the service ranges of different groups may also be different, for example, the service ranges corresponding to different EAS, respectively, without limitation. Alternatively, in another possible implementation manner, if the AF subscribes to the core network, such as 5GC, to the location of the UE according to the identity of the UE, the AF may determine an area formed by the locations according to the location of the UE in each group, where the area is the service area of the group. In this case, the service ranges of different groups may also be different. Alternatively, the AF may determine the service scope of the group according to a local policy in any other possible manner, which is not specifically limited.

It will be appreciated that S402 is an optional step, e.g. in case the AF has created a group and the service scope of the group is configured by default, S402 may not be performed.

S403, the AF sends a group creation request message to the NEF network element. Accordingly, the NEF network element receives the group creation request message from the AF.

For convenience of description, in the embodiment of the present application, the group creation request sent by the AF to the NEF network element is marked as a group creation request message #1. The group creation request message #1 may be used to request creation of one or more groups determined in S402. The group creation request message #1 may be an existing signaling, such as a NEF parameter configuration creation request (nnef_parameter_create request) message, i.e. multiplexing the existing signaling, to reduce implementation difficulty; alternatively, the signaling may be new, and this is not particularly limited.

In one possible scenario, the group created is one, and the group creation request message #1 may be used only to request creation of this one group. For example, the group creation request message #1 includes at least one of: a group identification of the group, an identification of a corresponding group member (UE) within the group, or a service scope of the group. The identification of the group member may be an internal ID of the group member or an external ID of the group member, which is not particularly limited. Optionally, the group creation request message #1 may also indicate the type of the group, such as the group is a 5G VN type, or other types of groups, such as a temporary group type or a dynamic group type (a group requiring dynamic management of group members), which is not particularly limited. For example, the group creation request message #1 includes a new cell, such as group type indication information, for displaying the type indicating the group; alternatively, the type of the group is implicitly indicated by an existing cell in the group creation request message #1, such as a group identification. In addition, the group type indication information is only one exemplary naming, and any possible naming such as group indication information, type indication information, etc. may be substituted, which is not limited in particular.

In another possible scenario, the number of groups to be created is multiple, and one group creation request message #1 may be used to request creation of the multiple groups, i.e., by sending the group creation request message #1 once to request creation of the multiple groups, so as to improve communication efficiency. In this case, the group creation request message #1 may include at least one of: each group identification, an identification of a group member to which each group corresponds, or a service scope of each group. Optionally, the group creation request message #1 may further indicate the respective types of the multiple groups, and the specific implementation principles may refer to the above related description, which is not repeated herein. Alternatively, the number of groups to be created is plural, the group creation request message #1 is plural, and each group creation request message #1 may be used to request creation of a corresponding one of the groups, i.e., creation of plural groups is requested by transmitting the group creation request message #1 plural times. In addition, the specific implementation principle of each group creation request message #1 may also refer to the above related description, and will not be described herein.

In addition, the group creation request message #1 may further include other parameters, and the specific implementation principle is similar to that described in the above description of "2, 5G LAN", and will be understood with reference to the description thereof, which is not repeated.

S404, the NEF network element verifies the authority of the AF.

After the NEF network element receives the group creation request message #1 from the AF, the NEF network element may determine whether the AF has the right to request to create a group. If the AF has rights, the NEF network element performs S405. If it is determined that the AF has no rights, the NEF network element returns a Create group response message to the AF to indicate that the request failed. The group creation response message may be an existing signaling, such as an NEF parameter configuration creation response message (nnef_parameter creation_create response) message, that is, multiplexing the existing signaling, so as to reduce implementation difficulty; alternatively, the signaling may be new, and this is not particularly limited. Optionally, the create group response message #1 may also carry a cause value of the request failure, such as an AF unauthorized.

It will be appreciated that S404 is an optional step, e.g. in case the AF defaults to authorized, S404 may not be performed.

S405, the NEF network element sends a group creation request message to the UDM network element/PCF network element. Correspondingly, the UDM network element/PCF network element receives the group creation request message from the NEF network element.

For convenience of description, in the embodiment of the present application, a group creation request sent by a NEF network element to a UDM network element/PCF network element is marked as a group creation request message #2. The group creation request message #1 and the group creation request message #2 may be the same message or may be different messages.

When the group creation request message #1 and the group creation request message #2 are different messages, the group creation request message #2 may be determined according to the group creation request message #1 for requesting creation of one or more groups determined in S402 described above. For example, the group creation request message #2 includes at least one of: the specific implementation principles of the group identifier of the group, the identifier of the corresponding group member in the group, or the internal range of the group may also refer to the above related description, which is not repeated herein. The group creation request message #2 may be an existing signaling, such as a UDM parameter configuration creation request (nudm_parameter creation_create request) message, i.e. multiplexing the existing signaling, to reduce implementation difficulty; alternatively, the signaling may be new, and this is not particularly limited. In addition, the group creation request message #2 may further include other parameters, and the specific implementation principle is similar to that described in the above description of "2, 5G LAN", and will be understood with reference to the description thereof, which is not repeated.

Optionally, the NEF network element may also determine, according to the type of the group, whether to send the group creation request message #2 to the UDM network element or to send the group creation request message #2 to the PCF network element. For example, for a group whose group members are not easily changeable, such as a 5g vn, the nef network element may send a group creation request message #2 to the UDM network element to request the UDM network element to create and maintain the group. For groups that are easily changed by group members, such as temporary groups or dynamic groups, the NEF network element may send a group creation request message #2 to the PCF network element to request the PCF network element to create and maintain the group. Alternatively, the NEF network element may send the group creation request message #2 to only the UDM network element or the PCF network element by default, which is not particularly limited.

For ease of understanding, the following description will be given by taking the example of the UDM/PCF network element creating and maintaining a group.

The UDM network element/PCF network element may obtain, from the group creation request message #2, a group identification of the group, an identification of a group member corresponding to the group, and an internal range of the group. Alternatively, if the group identity of the group is an external group ID, the UDM network element/PCF network element may map the external group ID to an internal group ID. Alternatively, if the group member's identification is an external ID of the group member, the UDM/PCF network element may also map the external ID of the group member to an internal ID of the group member.

The UDM network element/PCF network element may create subscription information or policy information (for example subscription information) for the group at the group member granularity. For example, the UDM/PCF network element may save the group identification (external group ID and/or internal group ID) of the group, the internal range of the group, and the group type indication information (optional) of the group to the subscription information of each group member within the group. Alternatively, the UDM network element/PCF network element may create subscription information or policy information (for example subscription information) with group granularity. For example, the UDM/PCF network element may store the group identification of the group, the identification of the corresponding group member within the group (the external ID of the group member and/or the internal ID of the group member), the internal range of the group, and the group type indication information of the group (optional) as or into the subscription information of the group.

In addition, the Create group response message #2 may be an existing signaling, such as a UDM parameter configuration Create response message (nudm_parameter configuration_create response) message, that is, multiplexing the existing signaling to reduce implementation difficulty; alternatively, the signaling may be new, and this is not particularly limited. Optionally, the create group response message #2 may also carry a cause value of the request failure, such as an AF unauthorized.

S406, the UDM network element/PCF network element sends subscription information of position change to the AMF network element. Accordingly, the AMF network element receives the subscription message from the UDM network element/PCF network element for the location change.

The location-altered subscription message (denoted subscription message) may be used to inform the AMF network element to perform mobility tracking for group members within the group. The subscription message may be an existing signaling, such as an AMF event open subscription (namf_eventexposure_subscribe) message, that is, multiplexing the existing signaling, to reduce implementation difficulty, or may be a new message, which is not limited specifically. The subscription message may include at least one of: an internal scope of the group, or an identification of a corresponding group member within the group. Wherein group members within a group may be served by one or more AMF network elements. For the case of multiple group members served by one AMF network element, the UDM network element/PCF network element may carry the identifiers of the multiple group members in one subscription message, or may send one subscription message to the AMF network element for each group member, which is not specifically limited in the embodiment of the present application. For example, two group members in the group, ue#1 and ue#2, are served by AMF network element#1, and ue#3 is served by AMF network element#2, then the UDM network element/PCF network element sends a subscription message#1 to AMF network element#1, and sends a subscription message#2 to AMF network element#2. The subscription message #1 includes: { service area, ue#1, ue#2}. Or, the UDM network element/PCF network element sends 2 subscription messages #1 to the AMF network element #1, each subscription message #1 carrying a service range and an identity of a corresponding one of the UEs #1-UE #2. The subscription message #2 includes: { service area, ue#3}.

The UDM network element/PCF network element may determine an AMF network element serving a group member according to the identification of the corresponding group member in the group. For example, the UDM/PCF network element may determine, from the SUPI of each group member, an AMF network element to which the SUPI of the group member points, i.e. an AMF network element serving the group member. Of course, the manner of determining the AMF by the UDM network element/PCF network element may refer to the existing technology, which is not limited in detail.

S407, the AMF network element sends a notification message of the position change to the UDM network element/PCF network element. Correspondingly, the UDM network element/PCF network element receives a notification message of a location change from the AMF network element.

A notification message of the change of location (denoted as notification message) may be used to indicate the location of the group member in relation to the internal scope. The notification message may carry an identification of the corresponding group member within the group, as well as location indication information of the group member. The location indication information may be used to indicate a relationship of the location of the group member to an internal range. The relationship of the group member's location to the internal range may include any of the following: the group member moves out of the internal range, the group member moves into the internal range, the group member is within the internal range, or the group member is outside the internal range. The location indication information is only one exemplary naming, and may be replaced by any possible naming, such as member location indication information, group member location indication information, etc., which is not limited in particular. In addition, the notification message may not carry location indication information, such as by the type of notification message, to implicitly indicate the relationship between the location of the group member and the internal scope. Alternatively, the notification message may also carry the location of the group member, so that the UDM/PCF network element may determine the relationship between the location of the group member and the internal range based on the location of the group member.

In addition, the notification message #1 may be an existing signaling, such as an AMF event open notification (namf_eventExposure_notify) message, that is, multiplexing the existing signaling, to reduce implementation difficulty, or may be a new message, which is not limited specifically.

Taking an AMF network element as an example, the AMF network element may perform mobility tracking on group members indicated by the subscription message. For example, the AMF network element may determine the location of the group member based on mobility data of the group member (e.g., the location of the group member) reported by the RAN device, or an identification of the RAN device that the group member is currently accessing. The AMF network element may determine whether the group member is within an internal range according to the location of the group member. If the AMF network element determines that the group member is within an internal range (determined when mobility tracking is performed for the group member for the first time), a notification message need not be sent, or may still be sent, which is not particularly limited. If the AMF network element determines that a group member has moved out of the inner range, e.g. from a cell within the service range to a cell outside the service range, a notification message is sent indicating that the group member has moved out of the inner range. If the AMF network element determines that the group member is out of internal range (determined the first time the mobility tracking is performed on the group member), a notification message is sent to indicate that the group member is out of internal range. If the AMF network element determines that the group member moves into the internal range, from a cell located outside the service range of the group to a cell located within the service range, a notification message is sent to instruct the group member to move into the internal range.

S408, the UDM network element/PCF network element maintains group information.

Wherein the UDM network element/PCF network element may update the status of the group members or update the group members.

If the notification message indicates that the group member is moving out of the internal range, or that the group member is outside the internal range, the UDM/PCF network element may mark the group member as deactivated, or delete the group member. Wherein a group member being in a deactivated state indicates that the group member is not currently available, i.e., the AF may no longer currently serve the group member, but is still in the group at this time. The UDM network element/PCF network element may delete the identity of the group member in the subscription information of the group, or delete the group identity and the internal range of the group in the subscription information of the group member, etc. When the UDM/PCF network element deletes the group member, the group member may no longer obtain the service provided by the AF.

If the notification message indicates that the group member is moving into an internal range, the UDM/PCF network element may flag the group member in an active state or re-add the group member to the group. Wherein the group member being active indicates that the group member is currently available, i.e., the AF is currently in need or may provide service to the group member. The UDM network element/PCF network element re-adds the identification of the group member to the subscription information of the group, or re-adds the group identification and the internal range of the group to the subscription information of the group member. If the group member is re-added to the group, it should be necessary to provide the service of the AF for the group member.

It will be appreciated that whether a UDM/PCF network element marks the status of a group member or deletes or re-adds a group member may depend on the subscription information of the group or whether the subscription information of the group member has a status to maintain the group member. If there is a status maintaining group member, the UDM/PCF network element may flag the status of the group member, otherwise the UDM/PCF network element may delete or re-add the group member.

S409, the UDM network element/PCF network element triggers the SMF network element to adjust PDU session.

Adjusting the PDU session may include, among other things, releasing the PDU session, deactivating the PDU session, or activating the PDU session.

If the UDM network element/PCF network element marks the group member as a deactivated state or deletes the group member, the UDM network element/PCF network element can trigger the SMF network element to adjust the PDU session corresponding to the group member. For example, the UDM network element/PCF network element sends a request message, such as a UDM subscription data management Notification (nudm_sdm_notification) message, to the SMF network element, so as to notify the SMF network element to release or deactivate the PDU session corresponding to the UE, so as to optimize resources and improve the operation efficiency of the device. In this way, the SMF network element may trigger the UPF network element to delete the relevant configuration of the PDU session; alternatively, the SMF network element may retain the relevant configuration of the PDU session, but mark the PDU session as deactivated to indicate that the PDU session is currently not transmissible.

Or if the UDM/PCF network element marks the group member as active or adds the group member to the group again, the UDM/PCF network element may trigger the SMF network element to adjust the PDU session corresponding to the UE. For example, the UDM network element/PCF network element may send a request message to the SMF network element to notify the SMF network element to create or activate a PDU session corresponding to the UE, so as to ensure normal communication of the service. In this manner, the SMF network element may create a related configuration of the PDU session; alternatively, in the case where the UPF network element has previously stored the relevant configuration of the PDU session, the SMF network element may mark the PDU session as active to activate the user plane path of the PDU session, enabling the transmission of data.

It will be appreciated that S409 is an optional step, e.g. the adjustment of PDU sessions is triggered by other network elements, and S409 is not performed.

S410, the AMF network element/SMF network element refuses the request initiated by the UE which is positioned outside the internal range.

The AMF network element may acquire or be configured with an internal range (see S406). On this basis, if the UE sends a registration request message to the AMF network element, the AMF network element may determine whether the UE is within an inner range. If the UE is within the internal range, the AMF network element allows the UE to register with the core network, such as a 5GC. If the UE is outside the internal range, the AMF network element refuses the UE to register with the core network.

Alternatively, in the case where the AMF network element allows the UE to register with the core network by default, the SMF network element may determine whether to allow the UE to establish a data connection session, such as a PDU session, according to the internal range. For example, the SMF network element may obtain the internal range from the UDM network element/PCF network element in advance. Thereafter, if the UE initiates a session establishment request message to the SMF network element, the SMF network element may determine whether the UE is within an internal range. The SMF network element allows the UE to establish a data connection session if the UE is within an internal range. If the SMF network element determines that the UE is outside the internal range, the data connection session is refused to be established for the UE. For another example, after the SMF network element receives the session establishment request message from the UE, the SMF network element may request the UDM network element/PCF network element to determine whether the UE is located in an internal range. Thereafter, if the UDM/PCF network element indicates to the SMF network element that the UE is within an internal range, the SMF network element allows the UE to establish a data connection session. If the UDM network element/PCF network element indicates to the SMF network element that the UE is within the internal range, the SMF network element refuses to establish a data connection session for the UE.

S411, the AF sends a group update request message to the NEF network element. Accordingly, the NEF network element receives the group update request message from the AF.

For convenience of description, in the embodiment of the present application, a group update request message sent by an AF to a NEF network element is denoted as a group update request message #1.

The group update request message #1 may be used to request an update of the group members. For example, the group update request message #1 may carry a group identification of the group, an identification of a corresponding group member within the group, and update indication information.

Wherein the update instruction information is used for indicating any one of the following: deleting group members, re-adding group members to the group, marking group members as active, marking group members as inactive. For example, the AF may track the group member's traffic packets to determine if the group member's traffic packets are not acquired for a long period of time (e.g., more than a preset period of time). If the service data packet of the group member is not obtained for a long time, the AF transmits a group update request message #1 for requesting deletion of the group member or marking the group member as a deactivated state. It will be appreciated that the update indication information is only one exemplary naming, and that any possible naming may be substituted, such as member update indication information, group update indication information, etc., without being limited thereto. In addition, the group update request message #1 may not carry update indication information, such as an indication function by replacing the update indication information with the type of the group update request message #1.

Optionally, the group update request message #1 may also carry an identifier of the UE, so as to request that the UE be added in the group, i.e. a new group member is added. The AF may acquire the UE identifier in the manner described in S401, and determine which group the UE should belong to in the manner described in S402, which is not described herein.

Optionally, the group update request message #1 may also be used to update the service scope of the group. For example, the group update request message #1 carries a new service scope of the group, and the specific implementation principle of the new service scope may refer to the related description of the service scope and will not be described in detail.

In addition, the group Update request message #1 may be an existing signaling, such as a NEF parameter configuration Update request (nnef_ Parameter Provision _update request) message, that is, multiplexing the existing signaling, so as to reduce implementation difficulty; alternatively, the signaling may be new, and this is not particularly limited.

And S412, the NEF network element verifies the authority of the AF.

After the NEF network element receives the group update request message #1 from the AF, the NEF network element may determine whether the AF has the authority to update the group. If the AF has rights, the NEF network element performs S413. If the AF has no authority, the NEF network element returns an update group response message to the AF to indicate that the request fails. The Update group response message may be an existing signaling, such as an NEF parameter configuration Update response message (nnef_parameter_update response) message, that is, the existing signaling is multiplexed, so as to reduce implementation difficulty; alternatively, the signaling may be new, and this is not particularly limited. Optionally, the update group response message may also carry a cause value of the request failure, such as an AF unauthorized.

It will be appreciated that S412 is an optional step, e.g., where the default AF is authorized, or where the AF is a trusted AF, S412 may not be performed.

S413, the NEF network element sends a group update request message to the UDM network element/PCF network element. Correspondingly, the UDM network element/PCF network element receives the group update request message from the NEF network element.

For convenience of description, in the embodiment of the present application, the NEF network element sends a group update request message to the UDM network element/PCF network element, which is marked as a group update request message #2.

The group update request message #2 may be the same message as the group update request message #1 or may be a different message. When the group update request message #2 and the group update request message #1 are different messages, the group update request message #2 may be determined according to the group update request message #1, for example, the group update request message #2 carries the information in the group update request message #1 (see S411) for updating the group members. In addition, the group Update request message #2 may be an existing signaling, such as a UDM parameter configuration Update request (nudm_parameter Update request) message, i.e. multiplexing the existing signaling, to reduce implementation difficulty; alternatively, the signaling may be new, and this is not particularly limited.

The UDM network element/PCF network element may update the group based on the information in the group update request message # 2. For example, the UDM/PCF network element may delete the group member, re-add the group member to the group, mark the group member as active, mark the group member as inactive. For another example, the UDM/PCF network element may also determine, based on the identity of the UE, that the UE is not a group member within the group, thereby adding the UE to the group. For example, the UDM network element/PCF network element may add the identifier of the UE to the subscription information of the group, or add the group identifier and the internal range of the group to the subscription information of the UE. In addition, the UDM network element/PCF network element may subscribe the mobility of the UE to the AMF network element, and the specific implementation principle may refer to the related description in S406-S408, which is not described again.

It will be appreciated that S411-S413 are optional steps, e.g., where the group members are not updated, S411-S413 are not performed. Further, S411 to S413 are executed after S405, and the execution order between S411 to S413 and S406 to S410 is not limited.

Scene 2:

fig. 5 is a schematic flow chart of a communication method according to an embodiment of the present application. In scenario 2, the AF may provide the service scope of the group to the UDM/PCF network element through the NEF network element when creating the group. The NEF network element can instruct the AMF network element to carry out mobility tracking on the group members according to the service range so as to dynamically update the group members by the UDM network element/PCF network element, thereby ensuring that only the group members positioned in the service range can obtain the service provided by the AF, and further ensuring that the group members can obtain consistent service experience.

Specifically, as shown in fig. 5, the flow of the communication method is as follows:

s501, the UE reports the identification of the UE to the AF.

S502, the AF determines the group to be created and the service scope of the group.

The specific implementation principle of S501-S502 is similar to that of S401-S402, and may be understood with reference to the above, and will not be described again.

S503, the AF sends a group creation request message #1 to the NEF network element. Accordingly, the NEF network element receives the group creation request message #1 from the AF.

The group creation request message #1 may carry at least one of the following: an identification of the AF, or change of position notification instruction information. The identifier of the AF may be an address of the AF, such as an IP address of the AF, for the NEF network element to access the AF. The identification of the AF is an optional cell, e.g. the NEF network element may be preconfigured or obtain the identification of the AF in advance. The location change notification indication information may be used to indicate that the NEF network element subscribes to the mobility of the group member with the AMF network element. The location change notification indication information is an optional cell, e.g., the NEF network element may subscribe to the mobility of the group member with the AMF network element by default. Further, the location change notification indicator information is only one exemplary naming, and it may be replaced by any possible naming, such as location subscription notification information, location update notification information, etc.

It will be appreciated that the group creation request message #1 may also contain other information, and the specific implementation principle may refer to the related description in S403, which is not described in detail.

And S504, the NEF network element verifies the authority of the AF.

S505, the NEF network element sends a group creation request message #2 to the UDM network element/PCF network element. Correspondingly, the UDM/PCF network element receives the group creation request message #2 from the NEF network element.

The specific implementation principles of S504-S505 are similar to those of S404-S405, and will be understood with reference to the foregoing, and will not be repeated.

S506, the NEF network element sends a subscription message to the AMF network element. Accordingly, the AMF network element receives the read message from the NEF network element.

The specific implementation principle of S506 may refer to the related description in S406, and will not be described herein. Optionally, the subscription message may also carry an AF identifier, so that the AMF network element may directly send a notification message to the AF according to the AF identifier.

S507, the AMF network element sends a notification message to the NEF network element/AF, or the AMF network element sends a notification message to the AF. Correspondingly, the NEF network element/AF receives the notification message from the AMF network element, or the AF receives the notification message from the AMF network element.

Wherein whether the AMF network element sends a notification message to the NEF network element or to the AF may depend on whether the AMF network element has acquired an identification of the AF. If the AMF network element obtains the AF identification, the AMF network element can send a notification message to the AF. If the AMF network element does not acquire the identification of the AF, the AMF network element may send a notification message to the NEF.

If the NEF receives the notification message (recorded as notification message # 1), the NEF network element can automatically send a group update request message #2 to the UDM network element/PCF network element according to the notification message # 1; alternatively, the NEF network element may also send a notification message (denoted as notification message # 2) to the AF according to the identity of the AF. The notification message #1 and the notification message #2 may be the same message, i.e. the NEF forwards the notification message #1 directly to the AF. Alternatively, the notification message #1 and the notification message #2 may be different messages carrying the same cell, which is not particularly limited.

In addition, the specific implementation principle of S507 may refer to the related description in S407, which is not described herein.

S508, the AF sends a group update request message #1 to the NEF network element. Accordingly, the NEF network element receives the group update request message #1 from the AF.

And S509, the NEF network element verifies the authority of the AF.

S510, the NEF network element sends a group update request message #2 to the UDM network element/PCF network element. Correspondingly, the UDM/PCF network element receives the group update request message #2 from the NEF network element.

The specific implementation principles of S508-S510 are similar to those of S408, S411-S413, and will be understood with reference to the foregoing, and will not be repeated.

S511, the UDM network element/PCF network element triggers and adjusts the PDU session.

S512, the AMF network element/SMF network element refuses the request initiated by the UE which is positioned outside the internal range.

The specific implementation principles of S511-S512 are similar to those of S409-S410, and may be understood with reference to the above, and will not be described again.

Scene 3:

fig. 6 is a schematic flow chart of a communication method according to an embodiment of the present application. In scenario 3, the AF may provide the service scope of the group directly to the UDM/PCF network element when creating the group. The UDM network element/PCF network element can instruct the AMF network element to carry out mobility tracking on the group members according to the service range, so that the UDM network element/PCF network element dynamically updates the group members, only the group members positioned in the service range can be ensured to obtain the service provided by the AF, and the group members can be ensured to obtain consistent service experience.

S601, the UE reports the identification of the UE to the AF.

S602, the AF determines the group to be created and the service scope of the group.

The specific implementation principle of S601-S602 is similar to that of S401-S402, and may be understood with reference to the above, and will not be repeated.

S603, the AF sends a group creation request message to the UDM network element/PCF network element. Correspondingly, the UDM network element/PCF network element receives a group creation request message from the AF.

The group creation request message may be used to request creation of one or more groups determined in S602. For example, the group creation request message includes at least one of: group identification of a group, identification of a corresponding group member within a group, or service scope of a group. The AF may pre-configure the address of the UDM/PCF network element to send a group creation request message to the UDM/PCF network element accordingly.

In addition, the specific implementation principle of S603 is similar to that of S405 described above, and reference may be made to understanding, and details are not repeated.

S604, the UDM network element/PCF network element sends a subscription message to the AMF network element. Accordingly, the AMF network element receives subscription messages from the UDM network element/PCF network element.

S605, the AMF network element sends a notification message to the UDM network element/PCF network element. Correspondingly, the UDM network element/PCF network element receives the notification message from the AMF network element.

S606, the UDM network element/PCF network element maintains a group.

S607, the UDM/PCF network element triggers the adjustment of the PDU session.

S608, the AMF network element/SMF network element rejects the UE initiated request outside the internal range.

The specific implementation principles of S604-S608 are similar to those of S406-S410, and will be understood with reference to the foregoing, and will not be repeated.

S609, AF sends a group update request message to UDM network element/PCF network element. Correspondingly, the UDM network element/PCF network element receives the group update request message from the AF.

The group update request message may be used to request to update the group members, and the specific implementation principle may refer to the description related to S413, which is not repeated.

Scene 4:

fig. 7 is a schematic flow chart of a communication method according to an embodiment of the present application. In scenario 4, the AF may provide the service scope of the group directly to the UDM/PCF network element when creating the group. The AF can also instruct the AMF network element to carry out mobility tracking on the group members according to the service range, so that the UDM network element/PCF network element dynamically updates the group members, and only the group members positioned in the service range can be ensured to obtain the service provided by the AF, thereby ensuring that the group members can obtain consistent service experience.

S701, the UE reports the identification of the UE to the AF.

S702, the AF determines the group to be created and the service scope of the group.

S703, the AF sends a group creation request message to the UDM network element/PCF network element. Correspondingly, the UDM network element/PCF network element receives a group creation request message from the AF.

The specific implementation principle of S701-S702 is similar to S401-S402, and the specific implementation principle of S703 is similar to S603, which is referred to for understanding and will not be repeated.

S704, the AF sends a subscription message to the AMF network element. Accordingly, the AMF network element receives the subscription message from the NEF network element.

The specific implementation principle of S704 may refer to the related descriptions in S406 and S506, and will not be described herein.

S705, the AMF network element sends a notification message to the AF. Correspondingly, the AF receives a notification message from the AMF network element.

The specific implementation principle of S705 may refer to the related descriptions in S407 and S507, and will not be described again.

S706, AF sends a group update request message to UDM network element/PCF network element. Correspondingly, the UDM network element/PCF network element receives the group update request message from the AF.

S707, the UDM/PCF network element triggers an adjustment PDU session.

S708, the AMF network element/SMF network element rejects the UE-initiated request that is outside the internal range.

The specific implementation principles of S704-S708 are similar to those of S406-S410, and will be understood with reference to the foregoing, and will not be repeated.

The flow of the communication method provided by the embodiment of the application under various scenes is described in detail above with reference to fig. 4 to 7. The overall flow of the communication method is described below in connection with fig. 8.

Fig. 8 is a schematic flow chart of a communication method according to an embodiment of the present application. The communication method is suitable for the communication system and is used for communication between an application network element, a realization capability opening network element and a core network element (such as a data storage network element or a strategy control network element). The application network element may be the AF, the capability-open network element may be the NEF network element, and the core network element may be the UDM network element/PCF network element. As shown in fig. 8, the flow of the communication method is as follows:

S801, the capability open network element receives a group creation request message #1 from an application network element

The group creation request message #1 may include a group identifier, a group member included in a group corresponding to the group identifier, and a service range of the group. The service scope is used for indicating the group member to acquire the limited area of the service provided by the application network element.

The service scope of the group may be a service scope of the application network element. That is, the service scope of the group can be determined according to the existing service scope of the application network element, and the service scope does not need to be additionally configured for the application network element, so that the configuration complexity of the application network element is reduced, and the deployment is convenient and flexible. Optionally, the application network element comprises at least one of: one or more edge application servers EAS, or one or more edge enabling servers EES to which EAS corresponds. The service scope of the application network element comprises at least one of the following: a set of service areas for one or more EAS, or a service area for EES. In this case, multiple EAS can provide service for the group through load balancing, so that the service experience of the user is better. In addition, the EAS can share the service range of the EES (i.e., the service range of the group is the service range of the EES), so that the service range does not need to be additionally configured for each EAS, the configuration complexity of the EAS is reduced, and the EAS is convenient and flexible to deploy.

The service scope may be characterized by at least one of the following information: geographic location information, or network location information. That is, the application network element may select the representation mode of the service range according to the capability of the capability-releasing network element, so as to ensure that the capability-releasing network element can identify the service range. For example, if the capability of the capability-releasing network element supports a geographic location, the application network element may characterize the service scope with geographic location information. For example, the geographic location information includes at least one of: geographic identification information, or latitude and longitude information. Alternatively, if the capability of the capability-open network element supports network location, the application network element may characterize the service scope with network location information. For example, the network location information includes at least one of: DNAI, TAI, TAI list, area identity list, cell identity, or cell identity list.

In addition, the specific implementation principle of S801 may refer to the related descriptions in S401-S404, and will not be described again.

S802, the capability opening network element sends a group creation request message #2 to the core network element according to the group creation request message # 1. Correspondingly, the core network element receives the group creation request message #2 from the capability open network element.

The group creation request message #2 may include a group identifier, a group member included in a group corresponding to the group identifier, and an internal range of the group. The internal range is used to indicate a restricted area for group members to obtain services provided by the application network element.

In one possible implementation, the internal scope is mapped by the service scope, where the internal scope is a scope that can be identified by the operator network or the core network, so as to avoid failure in group creation due to failure of the operator network or the core network to identify the service scope. For example, the capability opening network element may map the service scope to an internal scope that can be identified by the operator network and send the group identity, group members, and internal scope to a core network element (e.g., a data storage network element or a policy control network element). Alternatively, in another possible implementation, the internal range may be the same as the service range, i.e. the service range is originally a range that the operator network or the core network can identify. In this case, the capability open network element does not need to do mapping, so as to save the overhead of the capability open network element. That is, the capability opening network element may send the group identity, the group member, and the service scope directly to the core network element (e.g., a data storage network element or a policy control network element). It can be understood that the capability opening network element sends the group creation request message #2 to the core network element according to the group creation request message #1, and can also be considered that the capability opening network element triggers the management of the group according to the group creation request message # 1.

Optionally, the capability open network element may also determine the type of the group according to the group creation request message #1, and send the group creation request message #2 to the core network element according to the type of the group. Wherein the group type is a temporary group or a dynamic group. It should be noted that, since the randomness of the temporary group or the dynamic group is relatively strong, for example, the location of the group member often changes, even the group member often changes, so that the service scope needs to be limited to ensure the service quality of the temporary group. It can be seen that for different types of groups, different core network elements can provide services to implement differentiated services, matching the respective requirements of each group. For example, for temporary groups, dynamic groups, etc., services may be provided by policy control network elements. For a fifth generation lan 5G VN, services may be provided by data storage network elements.

Alternatively, the group creation request message #1 may carry group type indication information. The group type indication information is used for indicating the type of the group so that the capability open network element can accurately know the type of the group. Of course, the type of the group may be indicated by other means, such as implicitly indicating the type of the group by the type of the group creation request message #1, which is not particularly limited.

In addition, the specific implementation principle of S802 may refer to the related description in S405, which is not repeated.

S803, the core network element associates and stores the group identification, the group member and the internal range.

The core network element can store the group identifier, the group member and the internal range into the subscription information of the group so as to realize centralized storage and facilitate subsequent inquiry. Or the core network element can store the group identifier and the internal range into the subscription information of the group members so as to realize distributed storage and improve the utilization rate of the storage space.

In addition, the specific implementation principle of S803 may refer to the description related to S405, which is not repeated.

In summary, according to the above method, since the service range or the internal range of the group may indicate the restricted area where the group member obtains the service provided by the application network element, that is, the group member may obtain the service provided by the application network element only within the restricted area, otherwise, the group member may not obtain the service provided by the application network element. Therefore, the group members obtaining the service can be ensured to be positioned in the limited area where the application network element provides the service, and the group members can be ensured to obtain consistent service experience.

Optionally, in one possible design, in the communication method provided by the embodiment of the present application, the capability opening network element may send a subscription message for location change to a mobility management network element corresponding to a group member, and receive a notification message for location change from the mobility management network element. The subscription message carries an internal scope/service scope, and the notification message is used for indicating the relationship between the position of the group member and the internal scope/service scope. The relationship of the group member's location to the service scope/internal scope includes any one or more of the following: group members move into service/internal scope; group members move out of service/internal range; group members are within service/internal range; alternatively, the group members are outside of service/internal range. Thus, the capability opening network element can timely and accurately know whether the group member is located in the internal range or not, or know the event that the group member moves into or out of the internal range.

After receiving the notification message, the capability-open network element may further send a notification message of the location change to the application network element, and receive a group update request message #1 from the application network element, so as to send a group update request message #2 to the core network element according to the group update request message # 1. Wherein, both the group update request message #1 and the update request message #2 may be used to request an update of the group. That is, the capability open network element does not directly transmit the group update request message #1, but converts the group update request message #1 into a message that can be identified by the core network element, such as the group update request message #2, so as to avoid failure of group update caused by failure of the core network element to identify the group update request message.

Or, after receiving the notification message, the capability opening network element may directly send a group update request message #2 to the core network element according to the notification message of the location change. The group update request message #2 is used to request update of the group. That is, the capability opening network element may directly request the core network element to update the group without going through the application network element, so as to reduce the communication delay. In this case, the capability open network element may optionally receive the location change notification indication information from the application network element in advance. The location change notification indication information is used for indicating the location change condition of the subscription group member of the capability opening network element. In this way, the capability opening network element can send the subscription message of the position change to the mobility management network element corresponding to the group member according to the indication of the position change notification indication information, so as to ensure that the capability opening network element can timely know whether the group member is located in the service range/internal range. Of course, the capability opening network element may send the subscription message of the location change to the mobility management network element corresponding to the group member by default, which is not limited specifically.

After receiving the group update request message #2, the core network element may update the group according to the group update request message # 2. For example, the update group may include at least one of: deleting group members, re-adding group members to a group, marking group members as active, marking group members as inactive, or adding new group members. Thus, the dynamic management of the group can be realized, and the group members in the internal range can be ensured to obtain the service provided by the application network element.

In addition, the specific implementation principles of this design scheme may refer to the relevant descriptions in S408, S411-S413, and S506-S510, which are not repeated.

Optionally, in one possible design, in the communication method provided by the embodiment of the present application, the core network element may send a subscription message for location change to a mobility management network element corresponding to a group member, and receive a notification message for location change from the mobility management network element. The subscription message carries an internal range, and the notification message is used for indicating the relationship between the position of the group member and the internal range, so that the core network element can timely know whether the group member is located in the internal range.

Based on the above, the core network element can update the group according to the relationship between the position of the group member and the internal range, so as to ensure that the group member located in the internal range can obtain the service provided by the application network element. For example, if the group member is outside the internal range, or the group member moves out of the internal range, the core network element deletes the group member, or marks the group member as deactivated, to ensure that the group member can no longer obtain the service provided by the application network element. Or if the group member moves into the service range, the core network element re-adds the group member into the group, or marks the group member as active state, so as to ensure that the group member can regain the service provided by the application network element.

In addition, the specific implementation principle of the design scheme may also refer to the related description in S406-S408, and will not be repeated.

Optionally, in one possible design, in the communication method provided by the embodiment of the present application, the core network element triggers the session management network element to manage a protocol data unit PDU session corresponding to the group member according to a relationship between the position of the group member and the internal range. For example, if the group member is out of the internal range or the group member moves out of the internal range, the core network element triggers the session management network element to release the PDU session, or marks the PDU session as a deactivated state, so as to improve the resource utilization of the session management network element and avoid resource waste caused by maintaining redundant PDU sessions. For another example, if the group member is within the service scope, or the group member moves into the service scope, the core network element triggers the session management network element to create a PDU session, or marks the PDU session as active, to ensure that the group member can regain the service provided by the application network element through the PDU session.

In addition, the specific implementation principle of the design scheme may refer to the related description in S409, which is not repeated.

Optionally, in a possible design, in the communication method provided by the embodiment of the present application, the core network element further leaves an internal range for sending to the session management network element, where the internal range may be used to indicate a limited area where the session management network element is allowed to establish a session, so as to ensure that the session management network element may only establish a session for a terminal in the internal range. Or the core network element may also receive the identifier of the terminal from the session management network element, and instruct the session management network element whether the terminal is in the internal range according to the identifier of the terminal, so as to ensure that the session management network element allows the terminal to establish the session only if the terminal is in the internal range.

In addition, the specific implementation principle of the design scheme may also refer to the related description in S410, which is not repeated.

It should be noted that the communication flow provided by the above method embodiments is only some examples and is not limiting. For example, the application network element may also interact directly with the core network element without going through the capability open network element, and the specific implementation principle may refer to the related description in the above scenario 3-scenario 4, which is not repeated.

The communication method provided by the embodiment of the application is described in detail above with reference to fig. 4 to 8. A communication apparatus for performing the communication method provided by the embodiment of the present application is described in detail below with reference to fig. 9 to 10.

Fig. 9 is a schematic structural diagram of a communication device according to an embodiment of the present application. As shown in fig. 9, the communication apparatus 900 includes: a transceiver module 901 and a processing module 902. For convenience of explanation, fig. 9 shows only major components of the communication apparatus.

In some embodiments, the communication device 900 may be adapted for use in the communication system shown in fig. 3, perform the functions of a NEF network element in the method shown in fig. 4-5, or perform the functions of a capability-open network element in the method shown in fig. 8.

The transceiver module 901 is configured to receive a group creation request message #1 from an application network element. A processing module 902, configured to trigger management of a group according to the group creation request message #1. The group creation request message comprises a #1 group identifier, group members included in a group corresponding to the group identifier, and a service range of the group; the service scope is used for indicating the group member to acquire the limited area of the service provided by the application network element.

In a possible design, the processing module 902 is further configured to map the service range to an internal range that can be identified by the operator network or the core network, and control the transceiver module 901 to send the group identifier, the group member, and the internal range to the core network element, where the internal range is used to instruct the group member to obtain the restricted area of the service provided by the application network element.

Optionally, the transceiver module 901 is further configured to send a subscription message for location change to a mobility management network element corresponding to a group member, and receive a notification message for location change from the mobility management network element. The subscription message carries an internal scope, and the notification message is used for indicating the relationship between the position of the group member and the internal scope.

Or, the processing module 902 is further configured to control the transceiver module 901 to send the group identifier, the group member, and the service range of the group to the core network element.

Optionally, the transceiver module 901 is further configured to send a subscription message for location change to a mobility management network element corresponding to a group member, and receive a notification message for location change from the mobility management network element. The subscription message carries a service scope, and the notification message is used for indicating the relationship between the position of the group member and the service scope.

Further, the transceiver module 901 is further configured to send a notification message of the location change to an application network element, and receive a group update request message #1 from the application network element; the processing module 902 is further configured to control the transceiver module 901 to send a group update request message #2 to the core network element according to the group update request message # 1. Wherein, the group update request message #1 is used for requesting to update the group, and the update request message #2 is also used for requesting to update the group.

Optionally, the processing module 902 is further configured to control the transceiver module 901 to send a group update request message #2 to the core network element according to the notification message of the location change. The group update request message #2 is used to request update of the group.

Optionally, the transceiver module 901 is further configured to receive a location change notification indication information from an application network element. The location change notification indication information is used for indicating the location change condition of the capability opening network element subscription group member.

Alternatively, the transceiver module 901 may include a transmitting module (not shown in fig. 9) and a receiving module (not shown in fig. 9). The transmitting module is configured to implement a transmitting function of the communication device 900, and the receiving module is configured to implement a receiving function of the communication device 900.

Optionally, the communication device 900 may further include a storage module (not shown in fig. 9) storing programs or instructions. The processing module 902, when executing the program or instructions, causes the communications apparatus 900 to perform the functions of the NEF network element in the method shown in fig. 4-5 or the capability open network element in the method shown in fig. 8.

The communication apparatus 900 may be a network device, a chip (system) or other components or assemblies that may be disposed in the network device, or an apparatus including the network device, which is not limited in the present application.

In addition, the technical effects of the communication apparatus 900 may refer to the technical effects of the communication method shown in fig. 4 to 8, and will not be described herein.

In other embodiments, the communication device 900 may be adapted for use in the communication system shown in fig. 3, perform the functions of a UDM network element/PCF network element in the method shown in fig. 4-7, or perform the functions of a core network element in the method shown in fig. 8.

The transceiver module 901 is configured to receive a group creation request message #2 from a capability open network element. The group creation request message #2 includes a group identifier, a group member included in a group corresponding to the group identifier, and an internal range of the group. The internal range is used to indicate a restricted area for group members to obtain services provided by the application network element. As such, the processing module 902 is configured to store the group identification, the group members, and the internal scope in association.

In one possible design, the processing module 902 is further configured to update the group according to a relationship between the location of the group member and the internal range.

Alternatively, if the group member is outside the internal range, or if the group member moves out of the internal range, the processing module 902 is further configured to delete the group member, or mark the group member as deactivated. Alternatively, if the group member moves into service, the processing module 902 is further configured to re-add the group member into the group, or mark the group member as active.

In a possible design, the processing module 902 is further configured to trigger the session management network element to manage the PDU session corresponding to the group member according to the relationship between the position of the group member and the internal range. Optionally, if the group member is outside the internal scope, or the group member moves out of the internal scope, the processing module 902 is further configured to trigger the session management network element to release the PDU session, or mark the PDU session as a deactivated state. Optionally, if the group member is within the service scope, or the group member moves into the service scope, the processing module 902 is further configured to trigger the session management network element to create a PDU session, or mark the PDU session as an active state.

In a possible design, the transceiver module 901 is further configured to receive a group update request message #2 from the capability open network element, where the group update request message #2 is used to request to update a group. In this way, the processing module 902 is further configured to update the group according to the group update request message # 2. For example, the update group may include at least one of: deleting group members, re-adding group members to a group, marking group members as active, marking group members as inactive, or adding new group members.

In a possible design, the processing module 902 is further configured to store the group identifier, the group member, and the internal scope in subscription information or policy information of the group. Or, the processing module 902 is further configured to store the group identifier and the internal scope in subscription information or policy information of the group member.

In a possible design, the transceiver module 901 is further configured to send the internal range to the session management network element. Or, the transceiver module 901 is further configured to receive an identifier of a terminal from the session management network element; the processing module 902 is further configured to control the transceiver module 901 to indicate to the session management network element whether the terminal is within an internal range according to the identifier of the terminal.

Optionally, the communication device 900 may further include a storage module (not shown in fig. 9) storing programs or instructions. The processing module 902, when executing the program or instructions, enables the communications device 900 to perform the functions of a UDM network element/PCF network element in the method shown in fig. 4-7, or perform the functions of a core network element in the method shown in fig. 8.

Fig. 10 is a schematic diagram of a second structure of the communication device according to the embodiment of the present application. The communication device may be a terminal, or may be a chip (system) or other part or component that may be provided in the terminal. As shown in fig. 10, the communication device 1000 may include a processor 1001. Optionally, the communication device 1000 may also include a memory 1002 and/or a transceiver 1003. Wherein the processor 1001 is coupled to the memory 1002 and the transceiver 1003, such as by a communication bus.

The following describes each constituent element of the communication apparatus 1000 in detail with reference to fig. 10:

the processor 1001 is a control center of the communication device 1000, and may be one processor or a collective term of a plurality of processing elements. For example, the processor 1001 is one or more central processing units (central processing unit, CPU), but may also be an integrated circuit specific (application specific integrated circuit, ASIC), or one or more integrated circuits configured to implement embodiments of the present application, such as: one or more microprocessors (digital signal processor, DSPs), or one or more field programmable gate arrays (field programmable gate array, FPGAs).

Alternatively, the processor 1001 may perform various functions of the communication apparatus 1000, such as performing the communication methods shown in fig. 4-8 described above, by running or executing a software program stored in the memory 1002 and invoking data stored in the memory 1002.

In a particular implementation, the processor 1001 may include one or more CPUs, such as CPU0 and CPU1 shown in FIG. 10, as an embodiment.

In a specific implementation, as an embodiment, the communication apparatus 1000 may also include a plurality of processors, such as the processor 1001 and the processor 1004 shown in fig. 10. Each of these processors may be a single-core processor (single-CPU) or a multi-core processor (multi-CPU). A processor herein may refer to one or more devices, circuits, and/or processing cores for processing data (e.g., computer program instructions).

The memory 1002 is configured to store a software program for executing the solution of the present application, and the processor 1001 controls the execution of the software program, and the specific implementation may refer to the above method embodiment, which is not described herein again.

Alternatively, memory 1002 may be, but is not limited to, a read-only memory (ROM) or other type of static storage device that may store static information and instructions, a random access memory (random access memory, RAM) or other type of dynamic storage device that may store information and instructions, an electrically erasable programmable read-only memory (electrically erasable programmable read-only memory, EEPROM), a compact disc read-only memory (compact disc read-only memory) or other optical disk storage, optical disk storage (including compact disc, laser disc, optical disc, digital versatile disc, blu-ray disc, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium that can be used to carry or store the desired program code in the form of instructions or data structures and that can be accessed by a computer. The memory 1002 may be integral to the processor 1001 or may exist separately and be coupled to the processor 1001 through an interface circuit (not shown in fig. 10) of the communication device 1000, which is not specifically limited in this embodiment of the present application.

A transceiver 1003 for communication with other communication apparatuses. For example, the communication apparatus 1000 is a terminal, and the transceiver 1003 may be used to communicate with a network device or another terminal device. As another example, the communication apparatus 1000 is a network device, and the transceiver 1003 may be used to communicate with a terminal or another network device.

Alternatively, the transceiver 1003 may include a receiver and a transmitter (not separately shown in fig. 10). The receiver is used for realizing the receiving function, and the transmitter is used for realizing the transmitting function.

Alternatively, the transceiver 1003 may be integral to the processor 1001 or may exist separately and be coupled to the processor 1001 by an interface circuit (not shown in fig. 10) of the communication device 1000, which is not specifically limited in this embodiment of the present application.

It should be noted that the configuration of the communication apparatus 1000 shown in fig. 10 is not limited to the communication apparatus, and an actual communication apparatus may include more or less components than those shown, or may combine some components, or may be different in arrangement of components.

In addition, the technical effects of the communication device 1000 may refer to the technical effects of the communication method described in the above method embodiments, and are not described herein.

The embodiment of the application provides a communication system. The communication system includes: one or more of the NEF network elements shown in fig. 4-7, and one or more of the UDM/PCF network elements shown in fig. 4-7; alternatively, the communication system includes: one or more capability-releasing network elements shown in fig. 8, and one or more core network elements shown in fig. 8.

For example, the capability open network element is configured to receive the group creation request message #1 from the application network element, and send the group creation request message #2 to the core network element according to the group creation request message # 1. A core network element for receiving a group creation request message #2 from the capability open network element, thereby storing the group identification, the group member and the internal range of the group in association. The group creation request message #1 includes a group identifier, a group member included in a group corresponding to the group identifier, and a service range of the group, where the service range is used to indicate the group member to obtain a restricted area of the service provided by the application network element. The group creation request message #2 includes a group identification, a group member, and an internal range for indicating the group member to acquire a restricted area of the service provided by the application network element.

Optionally, the type of group is a temporary group or a dynamic group.

It should be appreciated that the processor in embodiments of the application may be a central processing unit (central processing unit, CPU), which may also be other general purpose processors, digital signal processors (digital signal processor, DSP), application specific integrated circuits (application specific integrated circuit, ASIC), off-the-shelf programmable gate arrays (field programmable gate array, FPGA) or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, or the like. A general purpose processor may be a microprocessor or the processor may be any conventional processor or the like.

It should also be appreciated that the memory in embodiments of the present application may be either volatile memory or nonvolatile memory, or may include both volatile and nonvolatile memory. The nonvolatile memory may be a read-only memory (ROM), a Programmable ROM (PROM), an Erasable PROM (EPROM), an electrically Erasable EPROM (EEPROM), or a flash memory. The volatile memory may be random access memory (random access memory, RAM) which acts as an external cache. By way of example but not limitation, many forms of random access memory (random access memory, RAM) are available, such as Static RAM (SRAM), dynamic Random Access Memory (DRAM), synchronous Dynamic Random Access Memory (SDRAM), double data rate synchronous dynamic random access memory (DDR SDRAM), enhanced Synchronous Dynamic Random Access Memory (ESDRAM), synchronous Link DRAM (SLDRAM), and direct memory bus RAM (DR RAM).

The above embodiments may be implemented in whole or in part by software, hardware (e.g., circuitry), firmware, or any other combination. When implemented in software, the above-described embodiments may be implemented in whole or in part in the form of a computer program product. The computer program product comprises one or more computer instructions or computer programs. When the computer instructions or computer program are loaded or executed on a computer, the processes or functions described in accordance with embodiments of the present application are produced in whole or in part. The computer may be a general purpose computer, a special purpose computer, a computer network, or other programmable apparatus. The computer instructions may be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another computer-readable storage medium, for example, the computer instructions may be transmitted from one website site, computer, server, or data center to another website site, computer, server, or data center by wired (e.g., infrared, wireless, microwave, etc.). The computer readable storage medium may be any available medium that can be accessed by a computer or a data storage device such as a server, data center, etc. that contains one or more sets of available media. The usable medium may be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. The semiconductor medium may be a solid state disk.

It should be understood that the term "and/or" is merely an association relationship describing the associated object, and means that three relationships may exist, for example, a and/or B may mean: there are three cases, a alone, a and B together, and B alone, wherein a, B may be singular or plural. In addition, the character "/" herein generally indicates that the associated object is an "or" relationship, but may also indicate an "and/or" relationship, and may be understood by referring to the context.

In the present application, "at least one" means one or more, and "a plurality" means two or more. "at least one of" or the like means any combination of these items, including any combination of single item(s) or plural items(s). For example, at least one (one) of a, b, or c may represent: a, b, c, a-b, a-c, b-c, or a-b-c, wherein a, b, c may be single or plural.

It should be understood that, in various embodiments of the present application, the sequence numbers of the foregoing processes do not mean the order of execution, and the order of execution of the processes should be determined by the functions and internal logic thereof, and should not constitute any limitation on the implementation process of the embodiments of the present application.

Those of ordinary skill in the art will appreciate that the various illustrative elements and algorithm steps described in connection with the embodiments disclosed herein may be implemented as electronic hardware, or combinations of computer software and electronic hardware. Whether such functionality is implemented as hardware or software depends upon the particular application and design constraints imposed on the solution. Skilled artisans may implement the described functionality in varying ways for each particular application, but such implementation decisions should not be interpreted as causing a departure from the scope of the present application.

It will be clear to those skilled in the art that, for convenience and brevity of description, specific working procedures of the above-described systems, apparatuses and units may refer to corresponding procedures in the foregoing method embodiments, and are not repeated herein.

In the several embodiments provided by the present application, it should be understood that the disclosed systems, devices, and methods may be implemented in other manners. For example, the apparatus embodiments described above are merely illustrative, e.g., the division of the units is merely a logical function division, and there may be additional divisions when actually implemented, e.g., multiple units or components may be combined or integrated into another system, or some features may be omitted or not performed. Alternatively, the coupling or direct coupling or communication connection shown or discussed with each other may be an indirect coupling or communication connection via some interfaces, devices or units, which may be in electrical, mechanical or other form.

The units described as separate units may or may not be physically separate, and units shown as units may or may not be physical units, may be located in one place, or may be distributed on a plurality of network units. Some or all of the units may be selected according to actual needs to achieve the purpose of the solution of this embodiment.

In addition, each functional unit in the embodiments of the present application may be integrated in one processing unit, or each unit may exist alone physically, or two or more units may be integrated in one unit.

The functions, if implemented in the form of software functional units and sold or used as a stand-alone product, may be stored in a computer-readable storage medium. Based on this understanding, the technical solution of the present application may be embodied essentially or in a part contributing to the prior art or in a part of the technical solution, in the form of a software product stored in a storage medium, comprising several instructions for causing a computer device (which may be a personal computer, a server, a network device, etc.) to perform all or part of the steps of the method according to the embodiments of the present application. And the aforementioned storage medium includes: a U-disk, a removable hard disk, a read-only memory (ROM), a random access memory (random access memory, RAM), a magnetic disk, or an optical disk, or other various media capable of storing program codes.

The foregoing is merely illustrative of the present application, and the present application is not limited thereto, and any person skilled in the art will readily recognize that variations or substitutions are within the scope of the present application. Therefore, the protection scope of the present application shall be subject to the protection scope of the claims.

Claims

1. A method of communication, the method comprising:

the capability opening network element receives a group creation request message #1 from the application network element; the group creation request message #1 includes a group identifier, a group member included in a group corresponding to the group identifier, and a service range of the group; the service range is used for indicating the group member to acquire a limited area of the service provided by the application network element;

the capability opening network element sends a group creation request message #2 to a core network element according to the group creation request message #1; the group creation request message #2 includes: the group identity, the group members, and the internal scope of the group; the internal range is used for indicating the group member to acquire a limited area of the service provided by the application network element;

The core network element receives a group creation request message #2 from the capability opening network element;

and the core network element is used for storing the group identification, the group members and the internal range in an associated manner.

2. The method of claim 1, wherein the internal range is the same as the service range or the internal range is mapped by the service range and is a range identifiable by an operator network.

3. A method of communication, the method comprising:

and the capability opening network element triggers the management of the group according to the group creation request message # 1.

4. A method according to any of claims 1-3, characterized in that the service scope is the service scope of the application network element.

5. The method of claim 4, wherein the application network element comprises at least one of: one or more edge application servers EAS, or one or more edge enabling servers EES corresponding to said EAS.

6. A method according to any one of claims 1-3, characterized in that the service scope is characterized by any one or more of the following information: geographic location information or network location information.

7. The method of claim 6, wherein the geographic location information comprises any one or more of: geographic identification information or latitude and longitude information.

8. The method of claim 6, wherein the network location information comprises any one or more of: a data network access identifier DNAI, a track area identity TAI, a TAI list, an area identity list, a cell identity or a cell identity list.

9. The method according to any of claims 3-8, wherein the capability-releasing network element triggers the management of the group according to the group creation request message #1, comprising:

the capability opening network element maps the service range into an internal range which can be identified by an operator network; the internal range is used to characterize the confinement region;

And the capability opening network element sends the group identifier, the group members and the internal range to a core network element.

10. The method according to claim 1, 2 or 9, characterized in that the method further comprises:

the capability opening network element sends a subscription message of position change to a mobility management network element corresponding to the group member; the subscription message carries the internal scope;

the capability opening network element receives a notification message of position change from the mobility management network element; the notification message is used to indicate a relationship of the location of the group member to the internal scope.

11. The method of claim 10, wherein the relationship of the group member's location to the internal range comprises any one or more of:

the group members move into the internal range;

the group member moves out of the internal range;

the group members being within the internal range; or alternatively, the process may be performed,

the group members are outside the interior range.

12. The method according to claim 9, wherein the capability-releasing network element triggers the management of the group according to the group creation request message #1, comprising:

And the capability opening network element sends the group identifier, the group members and the service range to a core network element.

13. The method of claim 1, 2 or 12, wherein the method further comprises:

the capability opening network element sends a subscription message of position change to a mobility management network element corresponding to the group member; the subscription message carries the service range;

the capability opening network element receives a notification message of position change from the mobility management network element; the notification message is used to indicate a relationship of the location of the group member to the service scope.

14. The method of claim 13, wherein the relationship of the group member's location to the service scope comprises any one or more of:

the group members move into the service area;

the group member moves out of the service range;

the group members are within the service range; or alternatively, the process may be performed,

the group members are outside the service range.

15. The method according to claim 10 or 13, characterized in that the method further comprises:

the capability opening network element sends the notification message to the application network element;

The capability opening network element receives a group update request message #1 from the application network element; the group update request message #1 is used for requesting to update the group;

the capability opening network element sends the group update request message #2 to the core network element according to the group update request message #1; the group update request message #2 is used to request update of the group.

16. The method according to claim 10 or 13, characterized in that the method further comprises:

the capability opening network element sends the group update request message #2 to the core network element according to the notification message; the group update request message #2 is used to request update of the group.

17. The method according to claim 10 or 13, characterized in that the method further comprises:

the capability opening network element receives the position change notification indication information from the application network element; the location change notification indication information is used for indicating the capability opening network element to subscribe to the location change condition of the group member.

18. A method of communication, the method comprising:

the core network element receives a group creation request message #2 from the capability opening network element; the group creation request message #2 includes a group identifier, a group member included in a group corresponding to the group identifier, and an internal range of the group; the internal range is used for indicating the group member to acquire a limited area of the service provided by the application network element;

19. The method of any one of claims 1, 2 or 18, further comprising:

and the core network element updates the group according to the relation between the position of the group member and the internal range.

20. The method of claim 19, wherein the core network element updating the group according to the relationship between the location of the group member and the internal range comprises:

if the group member is located outside the internal range or the group member moves outside the internal range, the core network element deletes the group member or marks the group member as a deactivated state; or alternatively, the process may be performed,

if the group member moves within the internal range, the core network element re-adds the group member to the group or marks the group member as active.

21. The method according to any one of claims 19-20, further comprising:

and triggering a session management network element to manage a protocol data unit PDU session corresponding to the group member by the core network element according to the relation between the position of the group member and the internal range.

22. The method according to claim 21, wherein the triggering the session management element to manage the PDU session corresponding to the group member by the core network element according to the relationship between the position of the group member and the internal range comprises:

if the group member is located outside the internal range or the group member moves outside the internal range, the core network element triggers the session management network element to release the PDU session or marks the PDU session as a deactivated state; or alternatively, the process may be performed,

and if the group member is positioned in the internal range or the group member moves to be in the internal range, triggering the session management network element to create the PDU session or marking the PDU session as an active state by the core network element.

23. The method according to any one of claims 19-22, further comprising:

the core network element sends a subscription message of position change to a mobility management network element corresponding to the group member; the subscription message carries the internal scope;

the core network element receives a notification message of the position change from the mobility management network element; the notification message is used to indicate a relationship of the location of the group member to the internal scope.

24. The method according to any of claims 1, 2, 18-23, wherein the core network element storing the group identity, the group member and the internal range in association comprises:

the core network element stores the group identifier, the group members and the internal range into subscription information of the group; or alternatively, the process may be performed,

and the core network element stores the group identifier and the internal range into the subscription information of the group member.

25. The method according to any one of claims 18-20, further comprising:

the core network element sends the internal range to a session management network element; or alternatively, the process may be performed,

the core network element receives the identification of the terminal from the session management network element, and indicates to the session management network element whether the terminal is located within the internal range according to the identification of the terminal.

26. The method according to any of claims 1, 2, 18-25, wherein the core network element is a data storage network element or a policy control network element.

27. A communication device, the device comprising: a module for performing the method of any one of claims 3-26.

28. A communication device, the communication device comprising: a processor and a memory; the memory is configured to store computer instructions that, when executed by the processor, cause the communication device to perform the communication method of any of claims 3-26.

29. A computer-readable storage medium, characterized in that the computer-readable storage medium comprises a computer program or instructions which, when run on a computer, cause the computer to perform the communication method according to any one of claims 3-26.