Communication method and apparatus

Abstract

The application provides a communication method and device, belonging to the technical field of communication, to guarantee the service experience of group members. In the method, the service range or internal range of the group can indicate a restricted area for the group members to obtain the service provided by the application network element, that is, the group members can only obtain the service provided by the application network element within the restricted area, otherwise, the group members cannot obtain the service provided by the application network element. In this way, it can be ensured that the group members obtaining the service are located within the restricted area of the service provided by the application network element, thereby guaranteeing the consistent service experience of the group members.

Description

Technical Field

[0001] This application relates to the field of communications, and more particularly to a communication method and apparatus. Background Technology

[0002] 5G local area network (5G LAN), also known as 5G virtual network (5G VN), is typically used in scenarios such as home communication, enterprise offices, factory manufacturing, vehicle-to-everything (V2X) networks, power grid upgrades, and public security agencies. 5G VN is a group service provided by a 5G network. For example, 5G VN can provide private communication between two or more terminals (group members) within a group, based on Internet Protocol (IP) or non-IP protocols (such as Ethernet), meaning communication does not require forwarding through the 5G core network (5G core, 5GC), thus reducing communication latency.

[0003] However, in 5G networks and subsequent evolutionary communication systems, new group communication scenarios have emerged, such as multi-player interactive games and multi-player autonomous vehicle fleets. These scenarios require group members to obtain relevant application data from application functions (AFs) to achieve interactive communication. In this case, the distance between group members and the AF affects their service experience. For example, group members closer to the AF experience lower communication latency and a better service experience. However, group members farther from the AF experience higher communication latency and a worse service experience. Therefore, ensuring a consistent service experience for all group members remains a challenge. Summary of the Invention

[0004] This application provides a communication method and apparatus to ensure that group members can obtain a consistent service experience.

[0005] To achieve the above objectives, this application adopts the following technical solution:

[0006] Firstly, a communication method is provided. This method includes: a capability open network element receiving a group creation request message #1 from an application network element, and sending a group creation request message #2 to a core network element based on the group creation request message #1. The core network element receives the group creation request message #2 from the capability open network element, thereby associating and storing a group identifier, group members, and the internal scope of the group. The group creation request message #1 includes a group identifier, the group members included in the group corresponding to the group identifier, and the service scope of the group, where the service scope indicates the restricted area for group members to access services provided by the application network element. The group creation request message #2 includes a group identifier, group members, and an internal scope, where the internal scope indicates the restricted area for group members to access services provided by the application network element.

[0007] As described in the first aspect, the service range or internal range of a group can indicate the restricted area within which group members can obtain services provided by the application network element. That is, group members can only obtain services provided by the application network element within the restricted area; otherwise, they cannot obtain such services. This ensures that all group members receiving services are located within the restricted area provided by the application network element, thereby guaranteeing a consistent service experience for all group members.

[0008] In one possible design, the internal range is mapped from the service range, and this internal range is a range that the operator network or core network can recognize, thus avoiding group creation failure due to the operator network or core network's inability to recognize the service range. Alternatively, the internal range can be the same as the service range, meaning the service range is already a range that the operator network or core network can recognize. In this case, the capability-opening network element does not need to perform mapping, saving the overhead of the capability-opening network element.

[0009] In one possible design, the service range of the group is the same as the service range of the application network element. That is, the service range of the group can be determined based on the existing service range of the application network element, without the need to configure an additional service range for the application network element, thereby reducing the configuration complexity of the application network element and facilitating flexible deployment.

[0010] Optionally, the application network element includes at least one of the following: one or more Edge Application Servers (EAS), or one or more Edge Enabler Servers (EES) corresponding to EAS. The service scope of the application network element includes at least one of the following: a set of service scopes for one or more EAS, or the service scope of the EES. In this case, multiple EAS can provide services to the group through load balancing, resulting in a better user experience. Furthermore, these EAS can share the service scope of the EES (i.e., the group's service scope is the EES's service scope), thus eliminating the need to configure a separate service scope for each EAS, reducing the configuration complexity of EAS, and facilitating flexible deployment.

[0011] In one possible design, the service range is represented by at least one of the following: geographic location information or network location information. That is, the application network element can select the representation method of the service range based on the capabilities of the capability-opening network element to ensure that the capability-opening network element can identify the service range. For example, if the capability-opening network element supports geographic location, the application network element can use geographic location information to represent the service range. For example, geographic location information includes at least one of the following: geographic identification information or latitude and longitude information. Alternatively, if the capability-opening network element supports network location, the application network element can use network location information to represent the service range. For example, network location information includes at least one of the following: Data Network Access Identifier (DNAI), Track Area Identifier (TAI), TAI list, area identifier, area identifier list, cell identifier, or cell identifier list.

[0012] Optionally, the method described in the first aspect may further include: the capability-opening network element sending a location change subscription message to the mobility management network element corresponding to the group member, and receiving a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range. For example, the relationship between the group member's location and the internal range may include any one or more of the following: the group member moves into the internal range; the group member moves out of the internal range; the group member is within the internal range; or the group member is outside the internal range. In this way, the capability-opening network element can promptly and accurately determine whether a group member is within the internal range, or in other words, determine whether a group member has moved into or out of the internal range.

[0013] Alternatively, the method described in the first aspect may further include: the capability-opening network element sending a location change subscription message to the mobility management network element corresponding to the group member, and receiving a location change notification message from the mobility management network element. The subscription message carries the service range, and the notification message indicates the relationship between the group member's location and the service range. For example, the relationship between the group member's location and the service range includes any one or more of the following: the group member moves into the service range; the group member moves out of the service range; the group member is within the service range; or, the group member is outside the service range. In this way, the capability-opening network element can promptly and accurately determine whether a group member is within the service range, or in other words, whether a group member has moved into or out of the service range.

[0014] Furthermore, the method described in the first aspect may further include: the capability-opening network element sending a location change notification message to the application network element and receiving a group update request message #1 from the application network element, thereby sending a group update request message #2 to the core network element based on the group update request message #1. Here, the group update request message #1 is used to request an update of the group, and the update request message #2 is used to request an update of the group. It can be seen that the capability-opening network element does not directly transmit the group update request message #1, but rather converts it into a message that the core network element can recognize, such as the group update request message #2, to avoid group update failure due to the core network element's inability to recognize the group update request message.

[0015] Optionally, the method described in the first aspect may further include: the capability open network element sending a group update request message #2 to the core network element based on the location change notification message. The group update request message #2 is used to request an update of the group; that is, the capability open network element can directly request the core network element to update the group without going through the application network element, so as to reduce communication latency.

[0016] Optionally, the method described in the first aspect may further include: the capability open network element receiving location change notification indication information from the application network element. The location change notification indication information is used to instruct the capability open network element to subscribe to location changes of group members. Thus, the capability open network element can send a location change subscription message to the mobility management network element corresponding to the group member based on the location change notification indication information, ensuring that the capability open network element can know whether the group member is within the service range. Of course, the capability open network element may also send the location change subscription message to the mobility management network element corresponding to the group member by default; this is not specifically limited.

[0017] In one possible design, the capability-opening network element sends a group creation request message #2 to the core network element based on the group creation request message #1. This includes: the capability-opening network element determining the group type based on the group creation request message #1, and then sending the group creation request message #2 to the core network element according to the group type. In other words, different core network elements can provide services for different types of groups to achieve differentiated services and match the specific needs of each group. For example, temporary or dynamic groups can be provided by the policy control network element. For 5GVN (5G Local Area Network), services can be provided by the data storage network element.

[0018] Optionally, the group creation request message #1 carries group type indication information, which indicates the type of the group so that the capability-opening network element can accurately determine the group type. Of course, the group type can also be indicated in other ways, such as implicitly indicating the group type through the type of the group creation request message #1, without specific limitations.

[0019] Optionally, the group type can be a temporary group or a dynamic group. It should be noted that because temporary or dynamic groups are more random, such as the frequent changes in the location of group members or even the frequent changes in the group members themselves, it is more necessary to limit the service scope to ensure the service quality of temporary groups.

[0020] In one possible design, the method described in the first aspect may further include: the core network element updating the group based on the relationship between the location of the group members and the internal scope, so as to ensure that the group members located in the internal scope can obtain the services provided by the application network element.

[0021] Optionally, the core network element updates the group based on the relationship between the group member's location and the internal range. This includes: if a group member is outside the internal range or 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 services provided by the application network element. Alternatively, if a group member moves into the service range, the core network element re-adds the group member to the group or marks the group member as active to ensure that the group member can regain access to services provided by the application network element.

[0022] In one possible design, the method described in the first aspect may further include: the core network element triggers the session management network element to manage the Protocol Data Unit (PDU) session corresponding to the group member based on the relationship between the group member's location and the internal range. For example, if the group member is outside the internal range or moves out of the internal range, the core network element triggers the session management network element to release the PDU session or mark the PDU session as deactivated, thereby improving the resource utilization of the session management network element and avoiding resource waste caused by maintaining redundant PDU sessions. As another example, if the group member is within the service range or moves into the service range, the core network element triggers the session management network element to create a PDU session or mark the PDU session as active, ensuring that the group member can regain access to the services provided by the application network element through the PDU session.

[0023] Optionally, the method described in the first aspect may further include: a core network element sending a location change subscription message to the mobility management network element corresponding to a group member, and receiving a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range, so that the core network element can promptly ascertain whether the group member is within the internal range.

[0024] In one possible design, the method described in the first aspect may further include: a core network element receiving a group update request message #2 from a capability-opening network element, whereby the group update request message #2 requests an update to the group. Thus, the core network element can update the group according to the group update request message #2. For example, updating the group may include at least one of the following: deleting a group member, re-adding a group member to the group, marking a group member as active, marking a group member as deactivated, or adding a new group member. This enables dynamic management of the group, ensuring that group members within the internal scope can access the services provided by the application network element.

[0025] In one possible design, the core network element associates and stores the group identifier, group members, and internal scope. This includes: the core network element storing the group identifier, group members, and internal scope in the group's subscription information or policy information for centralized storage, facilitating subsequent retrieval. Alternatively, the core network element stores the group identifier and internal scope in the group members' subscription information or policy information for distributed storage, improving storage space utilization.

[0026] It should be noted that the group identifier stored in the core network element storage can be either an external group identifier or an internal group identifier. An internal group identifier can be a group identifier that can be recognized by the operator network or the core network. Similarly, the group member stored in the core network element storage can be either an external identifier (ID) or an internal identifier (ID) of the group member. An internal identifier of the group member can be an identifier that can be recognized by the operator network or the core network.

[0027] In one possible design, the method described in the first aspect may further include: the core network element sending an internal range to the session management network element, which can be used to indicate the restricted area where the session management network element allows the establishment of sessions, to ensure that the session management network element can only establish sessions for terminals within the internal range. Alternatively, the core network element receives an identifier of a terminal from the session management network element and, based on the terminal identifier, indicates to the session management network element whether the terminal is within the internal range, to ensure that the session management network element only allows the terminal to establish a session if the terminal is within the internal range.

[0028] In one possible design, the core network element is either a data storage network element or a policy control network element.

[0029] Secondly, a communication method is provided. This method includes: a capability open network element receiving a group creation request message #1 from an application network element, and triggering group management based on the group creation request message #1. The group creation request message includes a group identifier (#1), the group members included in the group corresponding to the group identifier, and the service scope of the group; the service scope indicates the restricted area where group members can access services provided by the application network element.

[0030] In one possible design, the service range of the group can be the service range of the application network element.

[0031] Optionally, the application network element may include at least one of the following: one or more Edge Application Servers (EAS), or one or more Edge Enabler Servers (EES) corresponding to EAS. The service scope of the application network element may include at least one of the following: a set of service scopes for one or more EAS, or the service scope of an EES.

[0032] In one possible design, the service area can be represented by at least one of the following: geographic location information or network location information. Optionally, the geographic location information may include at least one of the following: geographic identification information or latitude and longitude information. Optionally, the network location information may include at least one of the following: DNAI, TAI, TAI list, area identifier, area identifier list, cell identifier, or cell identifier list.

[0033] In one possible design, the capability open network element triggers group management based on the group creation request message #1, including: the capability open network element maps the service range to an internal range that can be identified by the operator network or core network, and sends the group identifier, group members, and internal range to the core network element. The internal range is used to indicate the restricted area for group members to obtain services provided by the application network element.

[0034] Optionally, the method described in the second aspect may further include: the capability-opening network element sending a location change subscription message to the mobility management network element corresponding to the group member, and receiving a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range.

[0035] Furthermore, the relationship between the position of a group member and the inner range includes any one or more of the following: a group member moves into the inner range; a group member moves out of the inner range; a group member is within the inner range; or, a group member is outside the inner range.

[0036] Alternatively, in another possible design, the open capability network element triggers the management of the group based on the group creation request message #1, including: the open capability network element sending the group identifier, group members, and the service scope of the group to the core network element.

[0037] Optionally, the method described in the second aspect may further include: the capability-opening network element sending a location change subscription message to the mobility management network element corresponding to the group member, and receiving a location change notification message from the mobility management network element. The subscription message carries the service range, and the notification message indicates the relationship between the group member's location and the service range.

[0038] Furthermore, the relationship between the location of a group member and the service area includes any one or more of the following: a group member moves into the service area; a group member moves out of the service area; a group member is within the service area; or, a group member is outside the service area.

[0039] Furthermore, the method described in the second aspect may further include: the capability open network element sending a location change notification message to the application network element, and receiving a group update request message #1 from the application network element, thereby sending 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 to request an update of the group, and the update request message #2 is also used to request an update of the group.

[0040] Optionally, the method described in the second aspect may further include: the capability open network element sending a group update request message #2 to the core network element based on the location change notification message. The group update request message #2 is used to request an update of the group.

[0041] Optionally, the method described in the second aspect may further include: the capability open network element receiving location change notification indication information from the application network element. The location change notification indication information is used to indicate the location changes of members of the capability open network element's subscribed group.

[0042] Furthermore, other technical effects of the communication method described in the second aspect can be referred to the technical effects of the communication method described in the first aspect, and will not be repeated here.

[0043] Thirdly, a communication method is provided. This method includes: a core network element receiving a group creation request message #2 from a capability-opening network element. The group creation request message #2 includes a group identifier, the group members included in the group corresponding to the group identifier, and the internal scope of the group. The internal scope is used to indicate the restricted area where group members can access services provided by application network elements. Thus, the core network element associates and stores the group identifier, group members, and internal scope.

[0044] In one possible design, the method described in the third aspect may further include: the core network element updating the group based on the relationship between the location of the group members and the internal scope.

[0045] Optionally, the core network element updates the group based on the relationship between the group member's location and the internal range, including: if the group member is outside the internal range or moves out of the internal range, the core network element deletes the group member or marks the group member as deactivated. Alternatively, if the group member moves into the service range, the core network element re-adds the group member to the group or marks the group member as active.

[0046] In one possible design, the method described in the third aspect may further include: the core network element triggers the session management network element to manage the PDU session corresponding to the group member based on the relationship between the group member's location and the internal range. Optionally, if the group member is outside the internal range, or 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 deactivated. Optionally, if the group member is within the service range, or moves into the service range, the core network element triggers the session management network element to create a PDU session, or marks the PDU session as active.

[0047] Optionally, the method described in the third aspect may further include: a core network element sending a location change subscription message to the mobility management network element corresponding to a group member, and receiving a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range.

[0048] In one possible design, the method described in the third aspect may further include: a core network element receiving a group update request message #2 from a capability-opening network element, wherein the group update request message #2 is used to request an update of the group. Thus, the core network element can update the group according to the group update request message #2. For example, updating the group may include at least one of the following: deleting a group member, re-adding a group member to the group, marking a group member as active, marking a group member as deactivated, or adding a new group member.

[0049] In one possible design, the core network element associates and stores the group identifier, group members, and internal scope. This includes: the core network element storing the group identifier, group members, and internal scope in the group's subscription information or policy information. Alternatively, the core network element storing the group identifier and internal scope in the group members' subscription information or policy information.

[0050] In one possible design, the method described in the third aspect may further include: the core network element sending the internal range to the session management network element. Alternatively, the core network element receives the identifier of the terminal from the session management network element and, based on the terminal identifier, indicates to the session management network element whether the terminal is within the internal range.

[0051] In one possible design, the core network element is either a data storage network element or a policy control network element.

[0052] Furthermore, other technical effects of the communication method described in the third aspect can be referred to the technical effects of the communication method described in the first aspect, and will not be repeated here.

[0053] Fourthly, a communication system is provided. This system includes: capability-opening network elements and core network elements.

[0054] The capability-opening network element receives group creation request message #1 from the application network element and, based on group creation request message #1, sends group creation request message #2 to the core network element. The core network element receives group creation request message #2 from the capability-opening network element, thereby associating and storing the group identifier, group members, and the group's internal scope. Group creation request message #1 includes the group identifier, the group members included in the group corresponding to the group identifier, and the group's service scope, which indicates the restricted area where group members can access services provided by the application network element. Group creation request message #2 includes the group identifier, group members, and the internal scope, which indicates the restricted area where group members can access services provided by the application network element.

[0055] In one possible design, the internal range can be the same as the service range. Alternatively, the internal range can be mapped from the service range, and this internal range is a range that the operator network or core network can recognize.

[0056] In one possible design, the service range of the group is the same as the service range of the application network element.

[0057] Optionally, the application network element includes at least one of the following: one or more Edge Application Servers (EAS), or one or more Edge Enabler Servers (EES) corresponding to EAS. The service scope of the application network element includes at least one of the following: a set of service scopes for one or more EAS, or the service scope of an EES.

[0058] In one possible design, the service area is characterized by at least one of the following: geographic location information or network location information. Optionally, the geographic location information may include at least one of the following: geographic identifier information or latitude and longitude information. Optionally, the network location information may include at least one of the following: DNAI, TAI, TAI list, area identifier, area identifier list, cell identifier, or cell identifier list.

[0059] Optionally, the capability-opening network element is also used to send a location change subscription message to the mobility management network element corresponding to the group member, and to receive a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range. For example, the relationship between the group member's location and the internal range may include any one or more of the following: the group member moves into the internal range; the group member moves out of the internal range; the group member is within the internal range; or, the group member is outside the internal range.

[0060] Optionally, the capability-opening network element is also used to send a location change subscription message to the mobility management network element corresponding to the group member, and to receive a location change notification message from the mobility management network element. The subscription message carries the service range, and the notification message indicates the relationship between the group member's location and the service range. For example, the relationship between the group member's location and the service range includes any one or more of the following: the group member moves into the service range; the group member moves out of the service range; the group member is within the service range; or, the group member is outside the service range.

[0061] Furthermore, the capability-opening network element is also used to send location change notification messages to application network elements and receive group update request messages #1 from application network elements, thereby sending group update request messages #2 to core network elements based on group update request messages #1. Specifically, group update request message #1 is used to request an update to the group, and update request message #2 is used to request an update to the group.

[0062] Optionally, the capability-opening network element is also used to send a group update request message #2 to the core network element based on the location change notification message. The group update request message #2 is used to request an update to the group.

[0063] Optionally, the capability-opening network element is also configured to receive location change notification indication information from the application network element. The location change notification indication information is used to instruct the capability-opening network element to subscribe to location changes of group members. Thus, the capability-opening network element is also configured to send location change subscription messages to the mobility management network element corresponding to the group member based on the location change notification indication information.

[0064] In one possible design, the capability open network element is also used to determine the type of the group based on the group creation request message #1, and send the group creation request message #2 to the core network element based on the group type.

[0065] Optionally, the group creation request message #1 carries group type indication information, which is used to indicate the type of group.

[0066] Optionally, the group type can be a temporary group or a dynamic group.

[0067] In one possible design, the core network element is also used to update the group based on the relationship between the location of the group members and the internal scope.

[0068] Optionally, if a group member is outside the service area or moves out of the service area, the core network element may also delete the group member or mark the group member as deactivated. Alternatively, if a group member moves into the service area, the core network element may also re-add the group member to the group or mark the group member as active.

[0069] In one possible design, the core network element is also used to trigger the session management network element to manage the PDU sessions corresponding to the group members based on the relationship between the group members' locations and the internal scope. For example, if a group member is outside the internal scope or moves out of the internal scope, the core network element is also used to trigger the session management network element to release the PDU session or mark the PDU session as deactivated. As another example, if a group member is within the service range or moves into the service range, the core network element is also used to trigger the session management network element to create a PDU session or mark the PDU session as active.

[0070] Optionally, the core network element is also used to send a location change subscription message to the mobility management network element corresponding to the group member, and to receive a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range.

[0071] In one possible design, the core network element is further configured to receive a group update request message #2 from a capability-opening network element. Group update request message #2 is used to request an update to the group. Thus, the core network element is also configured to update the group based on the group update request message #2. For example, updating the group may include at least one of the following: deleting a group member, re-adding a group member to the group, marking a group member as active, marking a group member as deactivated, or adding a new group member.

[0072] In one possible design, the core network element is also used to store the group identifier, group members, and internal scope in the group's subscription information or policy information. Alternatively, the core network element is also used to store the group identifier and internal scope in the group members' subscription information or policy information.

[0073] In one possible design, the core network element is also used to send the internal range to the session management network element. Alternatively, the core network element is also used to receive the terminal identifier from the session management network element and, based on the terminal identifier, indicate to the session management network element whether the terminal is within the internal range.

[0074] In one possible design, the core network element is either a data storage network element or a policy control network element.

[0075] Furthermore, the technical effects of the communication system described in the fourth aspect can be referred to the technical effects of the communication method described in the first aspect, and will not be repeated here.

[0076] Fifthly, a communication apparatus is provided. The apparatus includes modules for performing the communication method described in the first aspect, such as a transceiver module and a processing module.

[0077] The transceiver module receives group creation request message #1 from the application network element. The processing module triggers group management based on group creation request message #1. The group creation request message includes a group identifier (#1), the group members included in the group, and the service scope of the group; the service scope indicates the restricted area where group members can access services provided by the application network element.

[0078] In one possible design, the service range of the group can be the service range of the application network element.

[0079] Optionally, the application network element may include at least one of the following: one or more Edge Application Servers (EAS), or one or more Edge Enabler Servers (EES) corresponding to EAS. The service scope of the application network element may include at least one of the following: a set of service scopes for one or more EAS, or the service scope of an EES.

[0080] In one possible design, the service area can be represented by at least one of the following: geographic location information or network location information. Optionally, the geographic location information may include at least one of the following: geographic identification information or latitude and longitude information. Optionally, the network location information may include at least one of the following: DNAI, TAI, TAI list, area identifier, area identifier list, cell identifier, or cell identifier list.

[0081] In one possible design, the processing module is further configured to map the service range to an internal range that can be recognized by the operator network or the core network, and control the transceiver module to send group identifiers, group members, and internal ranges to the core network elements. The internal range is used to instruct group members on the restricted area for obtaining services provided by the application network elements.

[0082] Optionally, the transceiver module is further configured to send a location change subscription message to the mobility management network element corresponding to the group member, and receive a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range.

[0083] Furthermore, the relationship between the position of a group member and the inner range includes any one or more of the following: a group member moves into the inner range; a group member moves out of the inner range; a group member is within the inner range; or, a group member is outside the inner range.

[0084] Alternatively, the processing module can also be used to control the transceiver module to send group identifiers, group members, and the service range of the group to the core network elements.

[0085] Optionally, the transceiver module is also configured to send a location change subscription message to the mobility management network element corresponding to the group member, and receive a location change notification message from the mobility management network element. The subscription message carries the service range, and the notification message indicates the relationship between the group member's location and the service range.

[0086] Furthermore, the relationship between the location of a group member and the service area includes any one or more of the following: a group member moves into the service area; a group member moves out of the service area; a group member is within the service area; or, a group member is outside the service area.

[0087] Furthermore, the transceiver module is also used to send location change notification messages to application network elements and receive group update request messages #1 from application network elements; the processing module is also used to control the transceiver module to send group update request messages #2 to core network elements according to the group update request messages #1. The group update request messages #1 are used to request updates to the group, and the update request messages #2 are also used to request updates to the group.

[0088] Optionally, the processing control is also used to control the transceiver module to send a group update request message #2 to the core network element based on the location change notification message. The group update request message #2 is used to request an update to the group.

[0089] Optionally, the transceiver module is also used to receive location change notification information from the application network element. The location change notification information is used to indicate the location changes of members in the capability open network element subscription group.

[0090] Optionally, the transceiver module may include a sending module and a receiving module. The sending module implements the sending function of the communication device described in the third and fifth aspects, and the receiving module implements the receiving function of the communication device described in the fifth aspect.

[0091] Optionally, the communication device described in the fifth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method described in the second aspect.

[0092] It should be noted that the communication device described in the fifth aspect can be a network device, such as a capability open network element, or a chip (system) or other component or assembly that can be set in a network device, or a device that includes a network device. This application does not limit this.

[0093] Furthermore, the technical effects of the communication device described in the fifth aspect can be referred to the technical effects of the communication method described in the second aspect, and will not be repeated here.

[0094] A sixth aspect provides a communication apparatus. The apparatus includes modules for performing the communication method described in the third aspect, such as a transceiver module and a processing module.

[0095] The transceiver module receives group creation request message #2 from the capability-opening network element. Group creation request message #2 includes a group identifier, the group members included in the group corresponding to the group identifier, and the internal scope of the group. The internal scope indicates the restricted area where group members can access services provided by the application network element. The processing module then associates and stores the group identifier, group members, and internal scope.

[0096] In one possible design, the processing module is also used to update the group based on the relationship between the position of the group members and the internal scope.

[0097] Optionally, if a group member is outside the service area or moves out of the service area, the processing module is also used to delete the group member or mark the group member as inactive. Alternatively, if a group member moves into the service area, the processing module is also used to re-add the group member to the group or mark the group member as active.

[0098] 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 based on the relationship between the group member's location and the internal range. Optionally, if the group member is outside the internal range or 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 deactivated. Optionally, if the group member is within the service range or moves into the service range, the processing module is further configured to trigger the session management network element to create a PDU session or mark the PDU session as active.

[0099] Optionally, the transceiver module is further configured to send a location change subscription message to the mobility management network element corresponding to the group member, and receive a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range.

[0100] In one possible design, the transceiver module is further configured to receive a group update request message #2 from the capability open network element, whereby the group update request message #2 requests an update to the group. Thus, the processing module is further configured to update the group based on the group update request message #2. For example, updating the group may include at least one of the following: deleting a group member, re-adding a group member to the group, marking a group member as active, marking a group member as deactivated, or adding a new group member.

[0101] In one possible design, the processing module is further configured to store the group identifier, group members, and internal scope into the group's contractual information or policy information. Alternatively, the processing module may also be configured to store the group identifier and internal scope into the group members' contractual information or policy information.

[0102] In one possible design, the transceiver module is further configured to send the internal range to the session management network element. Alternatively, the transceiver module is further configured to receive the terminal identifier from the session management network element; the processing module is further configured to control the transceiver module to indicate to the session management network element whether the terminal is within the internal range based on the terminal identifier.

[0103] Optionally, the transceiver module may include a sending module and a receiving module. The sending module implements the sending function of the communication device described in the sixth aspect, and the receiving module implements the receiving function of the communication device described in the sixth aspect.

[0104] Optionally, the communication device described in the sixth aspect may further include a storage module storing programs or instructions. When the processing module executes the program or instructions, the communication device can perform the communication method described in the third aspect.

[0105] It should be noted that the communication device described in the sixth aspect can be a network device, such as a core network element, for example, a data storage network element or a policy control network element, or it can be a chip (system) or other component or assembly that can be set in a network device, or it can be a device that includes a network device. This application does not limit it in this regard.

[0106] Furthermore, the technical effects of the communication device described in the sixth aspect can be referred to the technical effects of the communication method described in the first aspect, and will not be repeated here.

[0107] A seventh aspect provides a communication device. The communication device includes a processor configured to perform the communication method as described in the second or third aspect.

[0108] In one possible design, the communication device described in the seventh aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the seventh aspect and other communication devices.

[0109] In one possible design, the communication device described in the seventh aspect may further include a memory. This memory may be integrated with the processor or disposed separately. The memory may be used to store computer programs and / or data related to the communication method described in the second or third aspect.

[0110] In this application, the communication device described in the seventh aspect may be the network device described in the second or third aspect, or may be a chip (system) or other component or assembly disposed in the terminal, or may be a device containing the terminal.

[0111] Furthermore, the technical effects of the communication device described in the seventh aspect can be referred to the technical effects of the communication method described in the first aspect, and will not be repeated here.

[0112] Eighthly, a communication device is provided. The communication device includes a processor coupled to a memory, the processor executing a computer program stored in the memory to cause the communication device to perform the communication method as described in the second or third aspect.

[0113] In one possible design, the communication device described in the eighth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the eighth aspect and other communication devices.

[0114] In this application, the communication device described in the eighth aspect may be the network device described in the second or third aspect, or a chip (system) or other component or assembly disposed in the network device, or a device containing the network device.

[0115] Furthermore, the technical effects of the communication device described in the eighth aspect can be referred to the technical effects of the communication method described in the first aspect, and will not be repeated here.

[0116] A ninth aspect provides a communication device, comprising: a processor and a memory; the memory being used to store a computer program, which, when executed by the processor, causes the communication device to perform the communication method as described in the second or third aspect.

[0117] In one possible design, the communication device described in the ninth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the ninth aspect and other communication devices.

[0118] In this application, the communication device described in the ninth aspect may be the network device described in the second or third aspect, or may be a chip (system) or other component or assembly disposed in the network device, or may be a device containing the network device.

[0119] Furthermore, the technical effects of the communication device described in the ninth aspect can be referred to the technical effects of the communication method described in the first aspect, and will not be repeated here.

[0120] A tenth aspect provides a communication device comprising: a processor; the processor being coupled to a memory and, after reading a computer program from the memory, executing a communication method as described in the second or third aspect according to the computer program.

[0121] In one possible design, the communication device described in the tenth aspect may further include a transceiver. This transceiver may be a transceiver circuit or an interface circuit. The transceiver can be used for communication between the communication device described in the eighth aspect and other communication devices.

[0122] In this application, the communication device described in the tenth aspect may be the network device described in the second or third aspect, or may be a chip (system) or other component or assembly disposed in the network device, or may be a device containing the network device.

[0123] Furthermore, the technical effects of the communication device described in the tenth aspect can be referred to the technical effects of the communication method described in the second or third aspect, and will not be repeated here.

[0124] Eleventhly, a computer-readable storage medium is provided, comprising: a computer program or instructions; when the computer program or instructions are executed on a computer, the computer causes the computer to perform the communication method described in any one of the first to third aspects.

[0125] In a twelfth aspect, a computer program product is provided, comprising a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method described in any one of the first to third aspects. Attached Figure Description

[0126] Figure 1 This is a schematic diagram of the architecture of a 5G system;

[0127] Figure 2 The intended flow of 5G LAN;

[0128] Figure 3 This is a schematic diagram of the architecture of the communication system provided in the embodiments of this application;

[0129] Figure 4 Flowchart of the communication method provided in the embodiments of this application Figure 1 ;

[0130] Figure 5 Flowchart of the communication method provided in the embodiments of this application Figure 2 ;

[0131] Figure 6 Flowchart of the communication method provided in the embodiments of this application Figure 3 ;

[0132] Figure 7 Flowchart of the communication method provided in the embodiments of this application Figure 4 ;

[0133] Figure 8 Flowchart of the communication method provided in the embodiments of this application Figure 5 ;

[0134] Figure 9 Schematic diagram of the communication device provided in the embodiments of this application Figure 1 ;

[0135] Figure 10 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 . Detailed Implementation

[0136] For ease of understanding, the technical terms involved in the embodiments of this application will be introduced below.

[0137] 1. Fifth generation (5G) mobile communication system (5G system, 5GS):

[0138] Figure 1 This is a schematic diagram of the non-roaming architecture of 5GS. (Example:) Figure 1As shown, 5GS includes: access network (AN) and core network (CN), and may also include: terminals.

[0139] The aforementioned terminal can be a terminal with transceiver capabilities, or a chip or chip system that can be installed on the terminal. This terminal can also be referred to as user equipment (UE), access terminal, user unit, user station, mobile station (MS), mobile station, remote station, remote terminal, mobile device, user terminal, terminal, wireless communication equipment, user agent, or user equipment. The terminals in the embodiments of this application may be mobile phones, cellular phones, smartphones, tablets, wireless data cards, personal digital assistants (PDAs), wireless modems, handsets, laptop computers, machine-type communication (MTC) terminals, computers with wireless transceiver capabilities, virtual reality (VR) terminals, augmented reality (AR) terminals, wireless terminals in industrial control, wireless terminals in self-driving, wireless terminals in remote medical care, wireless terminals in smart grids, wireless terminals in transportation safety, wireless terminals in smart cities, wireless terminals in smart homes, vehicle-mounted terminals, roadside units (RSUs) with terminal functions, etc. The terminal of this application may also be an on-board module, on-board unit, on-board component, on-board chip or on-board unit that is built into a vehicle as one or more components or units.

[0140] The aforementioned AN (Access Network Adapter) is used to implement access-related functions. It can provide network access functionality for authorized users in a specific area and determine transmission links of different quality based on user level and service requirements to transmit user data. The AN forwards control signals and user data between the terminal and the CN (Radio Access Network). The AN may include access network equipment, also known as radio access network (RAN) equipment. The CN is primarily responsible for maintaining the mobile network's subscription data and providing terminals with functions such as session management, mobility management, policy management, and security authentication. The CN mainly includes the following network elements: User Plane Function (UPF) network element, Authentication Server Function (AUSF) network element, Access and Mobility Management Function (AMF) network element, Session Management Function (SMF) network element, Network Slice Selection Function (NSSF) network element, Network Exposure Function (NEF) network element, Network Function Repository Function (NRF) network element, Policy Control Function (PCF) network element, Unified Data Management (UDM) network element, Unified Data Repository (UDR) network element, and Application Function (AF).

[0141] like Figure 1 As shown in (a), the UE accesses the 5G network through the RAN equipment. The UE communicates with the AMF network element through the N1 interface (N1 for short); the RAN network element communicates with the AMF network element through the N2 interface (N2 for short); the RAN network element communicates with the UPF network element through the N3 interface (N3 for short); the SMF communicates with the UPF network element through the N4 interface (N4 for short), and the UPF network element accesses the data network (DN) through the N6 interface (N6 for short). Furthermore, Figure 1The control plane functions of the AUSF, AMF, SMF, NSSF, NEF, NRF, PCF, UDM, UDR, or AF network elements shown in (a) interact using service-oriented interfaces. For example, the service-oriented interface provided by the AUSF network element is Nausf; the service-oriented interface provided by the AMF network element is Namf; the service-oriented interface provided by the SMF network element is Nsmf; the service-oriented interface provided by the NSSF network element is Nnssf; the service-oriented interface provided by the NEF network element is Nnef; the service-oriented interface provided by the NRF network element is Nnrf; the service-oriented interface provided by the PCF network element is Npcf; the service-oriented interface provided by the UDM network element is Nudm; the service-oriented interface provided by the UDR network element is Nudr; and the service-oriented interface provided by the AF is Naf. Furthermore, as... Figure 1 As shown in (b), network elements such as NSSF, AUSF, UDM, UE, RAN, PCF, and SMF can all communicate with AMF network elements. AUSF network elements can also communicate with UDM network elements, which in turn can communicate with SMF network elements. SMF network elements, in addition to communicating with AMF and UDM network elements, can also communicate with UPF and PCF network elements. PCF network elements can also communicate with AF and NEF network elements. NEF network elements can also communicate with AF. UPF network elements can communicate with RAN equipment and DN. Figure 1 As shown in (b), "Nxx" between two network elements indicates the interface between these two network elements. For example, N22 represents the interface between the NSSF network element and the AMF network element, N12 represents the interface between the AUSF network element and the AMF network element, N8 represents the interface between the UDM network element and the AMF network element, and so on.

[0142] RAN equipment can be a device that provides access to terminals. For example, RAN equipment may include: next-generation mobile communication system, such as 6G access network equipment, such as 6G base station, or in next-generation mobile communication system, the network equipment may also have other naming methods, all of which are covered within the protection scope of the embodiments of this application, and this application does not limit them in any way. Alternatively, RAN equipment may also include 5G, such as gNB in ​​a new radio (NR) system, or one or a group of antenna panels (including multiple antenna panels) of a 5G base station, or it may be a network node constituting a gNB, transmission and reception point (TRP or transmission point (TP)) or transmission measurement function (TMF), such as a building base band unit (BBU), or a centralized unit (CU) or distributed unit (DU), an RSU with base station function, or a wired access gateway, or a 5G core network element. Alternatively, RAN equipment may also include access points (APs) in wireless fidelity (WiFi) systems, wireless relay nodes, wireless backhaul nodes, various forms of macro base stations, micro base stations (also known as small stations), relay stations, access points, wearable devices, vehicle-mounted equipment, and so on.

[0143] UPF network elements are primarily responsible for user data processing (forwarding, receiving, billing, etc.). For example, a UPF network element can receive user data from a data network (DN) and forward that data to the terminal through access network equipment. A UPF network element can also receive user data from the terminal through access network equipment and forward that data to the DN. A DN network element refers to the operator's network that provides data transmission services to users. Examples include Internet Protocol (IP), IP Multimedia Service (IMS), and the Internet. A DN can be an external network of the operator or a network controlled by the operator, used to provide services to terminal devices.

[0144] The AUSF network element is mainly used to perform security authentication for terminals.

[0145] AMF network elements are primarily used for mobility management in mobile networks. Examples include user location updates, user network registration, and user handover.

[0146] SMF network elements are primarily used for session management in mobile networks. This includes tasks such as session establishment, modification, and release. Specific functions include assigning Internet Protocol (IP) addresses to users and selecting UPF network elements that provide packet forwarding capabilities.

[0147] The PCF network element primarily supports providing a unified policy framework to control network behavior, providing policy rules to the control layer network functions, and is also responsible for acquiring user subscription information related to policy decisions. The PCF network element can provide policies to the AMF and SMF network elements, such as Quality of Service (QoS) policies and slice selection policies.

[0148] NSSF network elements are mainly used to select network slices for terminals.

[0149] NEF network elements are primarily used to support the opening of capabilities and events.

[0150] UDM network elements are mainly used to store user data, such as subscription data and authentication / authorization data.

[0151] UDR network elements are mainly used to store structured data, including contract data, policy data, externally exposed structured data, and application-related data.

[0152] AF primarily supports interaction with CN to provide services, such as influencing data routing decisions, policy control functions, or providing third-party services to the network side.

[0153] 2. 5G Local Area Network (5G LAN):

[0154] 5G LAN, also known as 5G virtual network (5G VN), is commonly used in scenarios such as home communication, enterprise offices, factory manufacturing, vehicle-to-everything (V2X) networks, power grid upgrades, and public security agencies. 5G VN is a group service provided by a 5G network. For example, 5G VN can provide private communication based on Internet Protocol (IP) or non-IP protocols (such as Ethernet) for two or more terminals (group members) within a group, meaning communication does not need to be forwarded through the 5G core network (5G core, 5GC), thus reducing communication latency. For instance, equipment in a factory can form a group, and group members can send Ethernet data packets to each other. Or, the office equipment (such as mobile phones, computers, or laptops) of all employees in a department of an enterprise can form a group, and group members can send IP data packets to each other, and so on. If two terminals are not in the same group, they cannot communicate with each other.

[0155] To achieve the above functionality, the 3rd Generation Partnership Project (3GPP) technical standard (TS) 23.502 defines a method for statically configuring 5G VN groups. For example, Figure 2 A flowchart illustrating the method for statically configuring a 5G VN group is shown below. Figure 2 As shown, the process of this method includes the following steps.

[0156] S201, the AF sends a NEF parameter configuration creation / update / deletion request (Nnef_ParameterProvision_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.

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

[0158] External group IDs are used to identify 5G VN groups. For example, a 5G VN group can be identified by the data network name (DNN) / single network slice selection assistance information (S-NSSAI), so the DNN / S-NSSAI can be used as the external group ID for this 5G VN group; alternatively, the external group ID can also be assigned by AF or represented by other information elements, without specific limitations.

[0159] 5G VN group member management parameters may include: a list of group member identifiers, which can be identified by a generic public subscription identifier (GPSI) or other identifiers (such as the group member's IP address). Generally, each member in a 5G VN group corresponds to a GPSI identifier.

[0160] 5G VN group data may include at least one of the following: protocol data unit (PDU) session type, application description, or information related to secondary authentication / authorization (denoted as relevant information). The PDU session type is the PDU session type for this 5G VN group. The application description can be used to construct the UE route selection policy (URSP) for 5G VN group members. Relevant information may include at least one of the following: secondary authentication / authorization required by the 5G VN group, or addressing information for data network (DN) authentication, authorization, and accounting (AAA) servers, etc.

[0161] It is understandable that 5G VN group data is typically used in the creation process; that is, the NEF parameter configuration creation request message usually carries 5G VN group data, while the NEF parameter configuration update / deletion request message may not. Furthermore, for the NEF parameter configuration creation request message, the parameters carried are used to create the 5G VN group, meaning the GPSI list includes the identifiers of all members within the 5G VN group. For the NEF parameter configuration update / deletion request message, the parameters carried are used to update / delete members within the 5G VN group, meaning the GPSI list includes the identifiers of members that need to be updated within the 5G VN group, or the identifiers of members that need to be deleted from the 5G VN group.

[0162] After receiving a NEF parameter configuration creation / update / deletion request message from an AF, the NEF network element can determine whether the NEF has granted the AF permission to provide parameters, such as whether it has granted the AF permission to create / update / delete parameters for 5G VN groups. If the NEF network element has granted the AF permission to provide parameters, the NEF network element executes S202. If the NEF network element has not granted the AF permission to provide parameters, it executes S204.

[0163] S202, the NEF network element sends a UDM parameter configuration creation / update / deletion request (Nudm_ParameterProvision_Create / Update / Delete request) message to the UDM network element. Correspondingly, the UDM network element receives the UDM parameter configuration creation / update / deletion request message from the NEF network element.

[0164] The UDM parameter configuration creation / update / deletion request message carries the parameters from the NEF parameter configuration creation / update / deletion request message. After receiving the UDM parameter configuration creation / update / deletion request message from the NEF network element, the UDM network element can determine whether it has granted the AF permission to provide parameters, such as whether it has granted the AF permission to create / update / delete 5G VN groups. If the UDM network element has granted the AF permission to provide parameters, then the UDM network element configures the corresponding parameters. For example, the UDM network element creates a 5G VN group based on the UDM parameter configuration creation request message, i.e., it saves the 5G VN group configuration from the UDM parameter configuration creation request message; or, the UDM network element updates or deletes members in the 5G VN group based on the UDM parameter configuration update / deletion request message. If the UDM network element has not granted the AF permission to provide parameters, then the UDM network element directly executes S203.

[0165] It should be noted that when creating a 5G VN group, the UDM network element can assign an internal group ID to the 5G VN group. This internal group ID corresponds to the external group ID of the 5G VN group, meaning the UDM network element maintains the 5G VN group through the internal group ID. Furthermore, the UDM network element can parse the GPSI in the parameter configuration create / update / delete request message into a subscription permanent identifier (SUPI). This means the UDM network element maintains the members within the 5G VN group through the members' SUPIs, such as creating, updating, or deleting corresponding members.

[0166] S203, the UDM network element sends a UDM parameter configuration creation / update / deletion response message (Nudm_ParameterProvision_Create / Update / Delete response) to the NEF network element. Correspondingly, the NEF network element receives the UDM parameter configuration creation / update / deletion response message from the UDM network element.

[0167] 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 process fails, the reason value in the UDM parameter configuration creation / update / deletion response message indicates the reason for the failure, such as the UDM network element not granting the AF permission to provide parameters.

[0168] S204, the NEF network element sends a NEF parameter configuration creation / update / deletion response (Nudm_ParameterProvision_Create / Update / Delete response) message to the AF. Correspondingly, the AF receives the NEF parameter configuration creation / update / deletion response message from the NEF network element.

[0169] 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 process fails, the reason value in the NEF parameter configuration creation / update / deletion response message indicates the reason for the failure, such as the NEF network element not granting the AF permission to provide parameters.

[0170] After a 5G VN group is successfully created, updated, or deleted, members within the group can communicate directly with other members via the UPF network element (without needing to connect to the external loopback DN through the N6 interface) from any location. This not only reduces communication latency but also ensures data security by preventing data from leaving the core network. However, for some new group scenarios, such as temporarily formed groups (including multiplayer interactive games and multiplayer autonomous vehicle fleets), members need to obtain relevant application data from the AF (Automatic Application Provider), such as from the interactive game server or the autonomous vehicle fleet control center, to enable interaction. In this case, the distance between group members and the AF affects their service experience. For example, group members closer to the AF experience lower communication latency and a better service experience. However, group members farther from the AF experience higher communication latency and a worse service experience. Therefore, ensuring a consistent service experience for all group members remains an issue that needs to be addressed.

[0171] In summary, to address the aforementioned technical problems, this application proposes the following technical solutions to ensure that group members can obtain a consistent service experience. The technical solutions in this application will now be described in conjunction with the accompanying drawings.

[0172] The technical solutions of this application embodiment can be applied to various communication systems, such as wireless fidelity (WiFi) systems, vehicle-to-everything (V2X) communication systems, device-to-device (D2D) communication systems, vehicle-to-everything (V2X) communication systems, 4th generation (4G) mobile communication systems, such as long term evolution (LTE) systems, worldwide interoperability for microwave access (WiMAX) communication systems, 5th generation (5G) mobile communication systems, such as new radio (NR) systems, and future communication systems, such as 6th generation (6G) mobile communication systems, etc.

[0173] This application will present various aspects, embodiments, or features relating to systems that may include multiple devices, components, modules, etc. It should be understood and appreciated that individual systems may include additional devices, components, modules, etc., and / or may not include all the devices, components, modules, etc. discussed in conjunction with the accompanying drawings. Furthermore, combinations of these approaches are also possible.

[0174] Furthermore, in the embodiments of this application, the words "exemplary," "for example," etc., are used to indicate that they are examples, illustrations, or descriptions. Any embodiment or design scheme described as "exemplary" in this application should not be construed as being more preferred or advantageous than other embodiments or design schemes. Specifically, the use of the term "exemplary" is intended to present the concept in a concrete manner.

[0175] In the embodiments of this application, the terms "information," "signal," "message," "channel," and "singaling" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are consistent. Similarly, "of," "corresponding (relevant)," and "corresponding" may sometimes be used interchangeably. It should be noted that, without emphasizing their distinction, their intended meanings are consistent. Furthermore, the " / " mentioned in this application can be used to indicate an "or" relationship.

[0176] The network architecture and business scenarios described in the embodiments of this application are for the purpose of more clearly illustrating the technical solutions of the embodiments of this application, and do not constitute a limitation on the technical solutions provided in the embodiments of this application. As those skilled in the art will know, with the evolution of network architecture and the emergence of new business scenarios, the technical solutions provided in the embodiments of this application are also applicable to similar technical problems.

[0177] 1) Group: A group can be a combination of members with the same attributes. For example, it can be a combination of members that can enjoy the consistent services provided by the application network element, or it can be a combination of all terminal devices located in a specified area. A group can be 5G VN, or other types of groups, such as temporary groups or dynamic groups (groups that require dynamic management of group members), without specific limitations.

[0178] 2) Internal Group ID: An internal group ID is an identifier that can be recognized by network elements within the core network (such as 5GC) or the operator's network (such as SMF, AMF, UDM, PCF, NEF, etc.) and uniquely represents the group. The internal group ID can be a DNN, S-NSSAI, a combination of DNN and S-NSSAI, or represented by other information.

[0179] 3) External Group ID: The external group ID refers to an identifier that is uniquely identified and represents the group outside the core network or operator network, for example, within the AF range. The external group ID can be a string, a random number, or other information. It should be noted that network elements within the core network or operator network may not be able to recognize the external group ID. There can be a mapping relationship between external group IDs and internal group IDs.

[0180] 4) Internal ID of a group member: The internal ID of a group member refers to an identifier that can be recognized by network elements within the core network or operator network and uniquely represents a group member within the group. The internal ID of a group member can be SUPI.

[0181] 5) External ID of a Group Member: The external ID of a group member can be an identifier that can be identified and uniquely represent a group member within the group, outside the core network or operator network, for example, within the AF range. The internal ID of a group member can be an IP address or a GPSI. It should be noted that network elements within the core network or operator network may not be able to recognize the external ID of a group member. There can be a correspondence between the external ID and the internal ID of a group member.

[0182] 6) Service Range of a Group: The service range indicates the restricted area within which group members can access services provided by the AF. In other words, group members (UEs) can only obtain services provided by the AF, such as high-quality application services, when they are within the service range. Otherwise, if group members are outside the service range, they cannot obtain services provided by the AF, or they will only receive low-quality application services. The service range can be represented by geometric (geographical) location information, such as province, city, district, or latitude and longitude range, etc., or it may be represented by topological (network) location information that can be identified by network elements within the core network or operator network, such as data network access identifier (DNAI), track area identifier (TAI), TAI list, area ID, area ID list, cell ID, or cell ID list, etc.

[0183] 7) Internal Range of a Group: The internal range can also be used to indicate the restricted area where group members can access services provided by AF. The internal range and the service range can be the same; for example, both can be represented by the network location information described above. Alternatively, the internal range and the service range can be different; for example, the service range can be represented by the geographic location information described above, but the internal range can be represented by the network location information described above. In this case, the internal range can be a core network element, such as a NEF element, mapped from the service range, that is, geographic location information is converted into network location information. It should be noted that whether the internal range and the service range are the same refers to whether the representation methods are the same. Regardless of whether the representation methods are the same, the internal range and the service range can be used to indicate the same restricted area.

[0184] For ease of description, in the various embodiments of this application, the restricted area corresponding to the group determined by AF can be referred to as the "service range" of the group, and the restricted area involved in the core network element can be referred to as the "internal range" of the group.

[0185] The following is based on Figure 3 The communication system illustrated herein is used as an example to illustrate a communication system applicable to embodiments of this application. For example, Figure 3 This is a schematic diagram of the architecture of a communication system to which the communication method provided in the embodiments of this application is applicable.

[0186] like Figure 3As shown, this communication system is applicable to the aforementioned 5G system and mainly includes: AMF network elements, UDM / PCF network elements, NEF network elements, and AF. Optionally, it may also include: UE and SMF network elements. The relevant functions of the aforementioned network elements can be referred to the relevant descriptions in the aforementioned 5G system, and will not be repeated here. In the communication system of this application embodiment, when creating a group, the AF can provide the service range corresponding to the group through the NEF network element or directly to the UDM / PCF network element. The UDM / PCF network element or the NEF network element can instruct the AMF network element to perform mobility tracking of group members based on the service range, so that the UDM / PCF network element can dynamically update the group members, such as deleting or deactivating group members who have moved out of the service range or are located outside the service range, adding devices that have moved into the service range or are located within the service range to the group, or activating / re-adding group members who have moved into the service range to the group, ensuring that only group members within the service range can obtain the services provided by the AF, and guaranteeing that group members can obtain a consistent service experience.

[0187] For ease of understanding,

[0188] The following is combined with Figures 4-6 The interaction process between various network elements in the above communication system is described in detail through method implementation examples.

[0189] The communication method provided in this application can be applied to the above-described communication system. In different scenarios, different devices / network elements within the communication system can execute different processes of this communication method, which will be described in detail below.

[0190] Scene 1:

[0191] For example, Figure 4 Flowchart of the communication method provided in the embodiments of this application Figure 1 In Scenario 1, when creating a group, the AF can provide the service range of the group to the UDM / PCF network elements through the NEF network element. The UDM / PCF network elements can instruct the AMF network elements to perform mobility tracking of group members according to this service range, so that the UDM / PCF network elements can dynamically update the group members and ensure that only group members within the service range can obtain the services provided by the AF, thereby ensuring that group members can obtain a consistent service experience.

[0192] Specifically, such as Figure 4 As shown, the flow of this communication method is as follows:

[0193] S401, the UE reports its identifier to the AF.

[0194] The UE can access the 5G network and create a PDU session. The UE can access the AF through the created PDU session so that the AF can obtain the UE's identifier, such as the UE's IP address or GPSI. For example, the UE can send service data packets to the AF, with the source address of the data packet being the UE's IP address. That is, the AF obtains the UE's identifier during the service interaction process with the UE. Alternatively, the UE can also specifically report its IP address or GPSI to the AF in the payload portion of the data packet. Optionally, the UE can also send its corresponding service information, such as a service identifier, to the AF. This service information can be used to indicate the UE's service type, allowing the AF to determine the UE's group based on the service type. The specific implementation principle can be found in the relevant description in S402 below, and will not be repeated here.

[0195] An Edge Application Server (AF) is used to provide specific services. An AF can be an Edge Application Server (EAS) or a control network element that manages one or more EASs, such as an Edge Enable Server (EES). Each EAS can provide one or more services. When an AF is an EES, the services it provides are the sum of the services provided by the EASs it manages. Of course, an AF can also be any other possible network element; there are no specific limitations.

[0196] It is understandable that S401 is an optional step. For example, the UE's identifier may be pre-configured in the AF, or the AF may obtain the UE's identifier through other means, such as from the UDM network element, or from a specific portal. In this case, S401 may not be executed.

[0197] S402, AF determines the group to be created and the service scope of that group.

[0198] If one or more UEs access the AF, the AF can create a corresponding group for these one or more UEs.

[0199] One possible implementation is that the AF can group UEs accessing the AF into the same group and assign a group identifier to these UEs. The group identifier can be an external group ID or an internal group ID, without specific limitations. Alternatively, the AF can group UEs accessing the same service into the same group and assign a corresponding group identifier to each group. For example, UE#1, UE#2, ..., and UE#10 all need to access service #1 provided by the AF, while UE#11, UE#12, ..., and UE#20 all need to access service #2 provided by the AF. Thus, the AF groups UE#1-UE#10 into group #1, assigns group identifier #11 to group #1, and groups UE#11-UE#2 into group #2, assigning group identifier #22 to group #2. Another possible implementation is that the AF can subscribe to the location of a UE accessing a service provided by the AF from the 5GC. The AF can then cluster UEs based on their locations to determine which UEs belong to the same type of device. Based on this, the AF can group each type of device into a group and assign or assign a corresponding group identifier to each group. For example, through clustering, the AF identifies UE#1-UE#10 as the same type of device and UE#11-UE#20 as the same type of device. Thus, the AF identifies UE#1-UE#10 as group #1 and assigns group identifier #11 to group #1. Similarly, the AF identifies UE#11-UE#20 as group #2 and assigns group identifier #22 to group #2.

[0200] The service range of a group can be the service range of the AF (Automatic AF), such as a set of service ranges of one or more EAS (Enterprise Application Systems), or it can be the service range of the EES (Enterprise Application System). The service range of an EES can be a set of service ranges of multiple EAS. In this case, different groups can have the same service range, for example, all being the service range of an EES, or different groups can have different service ranges, for example, corresponding to different EAS, without limitation. Alternatively, if the AF subscribes to the location of the UE from the core network, such as 5GC, based on the UE's identifier, the AF can determine the area formed by these locations based on the locations of the UEs within each group; this area is the service range of that group. In this case, the service ranges of different groups may also be different. Alternatively, the AF can also determine the service range of a group using any other possible method based on local policies, without specific limitations.

[0201] It is understandable that S402 is an optional step. For example, if an AF group has already been created and the service scope of the group is configured by default, S402 may not be executed.

[0202] S403, the AF sends a group creation request message to the NEF network element. Correspondingly, the NEF network element receives the group creation request message from the AF.

[0203] For ease of description, in this embodiment, the group creation request sent by the AF to the NEF network element is labeled as Group Creation Request Message #1. Group Creation Request Message #1 can be used to request the creation of one or more groups determined in S402. Group Creation Request Message #1 can be existing signaling, such as the NEF parameter configuration creation request (Nnef_ParameterProvision_Create request) message, i.e., reusing existing signaling to reduce implementation difficulty; or it can be new signaling, which is not specifically limited.

[0204] In one possible scenario, only one group is being created, and the group creation request message #1 can be used solely to request the creation of this single group. For example, the group creation request message #1 includes at least one of the following: the group identifier, the identifier of the corresponding group member (UE) within the group, or the service range of the group. The identifier of the group member can be either an internal ID or an external ID of the group member, without specific limitation. Optionally, the group creation request message #1 can also indicate the type of this group, such as a 5G VN type group, or other types of groups, such as temporary group types or dynamic group types (groups that require dynamic management of group members), without specific limitation. For example, the group creation request message #1 includes a new information element, such as group type indication information, to explicitly indicate the type of the group; or, the type of the group can be implicitly indicated through existing information elements in the group creation request message #1, such as the group identifier. Furthermore, the group type indication information is merely an exemplary name, and it can be replaced with any possible name, such as group indication information, type indication information, etc., without specific limitation.

[0205] In another possible scenario, multiple groups are created. A single group creation request message #1 can be used to request the creation of these multiple groups, thus improving communication efficiency by sending one group creation request message #1. In this case, the group creation request message #1 can include at least one of the following: a group identifier, the identifier of the group members corresponding to each group, or the service scope of each group. Optionally, the group creation request message #1 can also indicate the type of each of these multiple groups; the specific implementation principle can be referred to the relevant description above, and will not be repeated here. Alternatively, multiple groups are created, and there are multiple group creation request messages #1. Each group creation request message #1 can be used to request the creation of a corresponding group, that is, multiple groups can be created by sending multiple group creation request messages #1. Furthermore, the specific implementation principle of each group creation request message #1 can also be referred to the relevant description above, and will not be repeated here.

[0206] In addition, the group creation request message #1 can also include other parameters. The specific implementation principle is similar to the relevant introduction in "2.5GLAN" above, which can be referred to for understanding and will not be repeated here.

[0207] S404, NEF network element verifies AF permissions.

[0208] After receiving the group creation request message #1 from the AF, the NEF network element can determine whether the AF has the authority to request group creation. If the AF has the authority, the NEF network element executes S405. If it is determined that the AF does not have the authority, the NEF network element returns a create group response message to the AF to indicate that the request failed. The create group response message can be existing signaling, such as the Nnef_ParameterProvision_Create response message, thus reusing existing signaling and reducing implementation difficulty; or it can be new signaling, without specific limitations. Optionally, the create group response message #1 can also carry a reason value for the request failure, such as AF not authorized.

[0209] It is understandable that S404 is an optional step. For example, if AF has the default permissions, S404 may not be executed.

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

[0211] For ease of description, in this embodiment, the group creation request sent by the NEF network element to the UDM network element / PCF network element is marked as group creation request message #2. Group creation request message #1 and group creation request message #2 may be the same message or different messages.

[0212] When Group Creation Request Message #1 and Group Creation Request Message #2 are different messages, Group Creation Request Message #2 can be determined based on Group Creation Request Message #1 and is used to request the creation of one or more groups as determined in S402 above. For example, Group Creation Request Message #2 includes at least one of the following: the group identifier, the identifier of the corresponding group member in the group, or the internal scope of the group. The specific implementation principle can be referred to the relevant description above, and will not be repeated here. Group Creation Request Message #2 can be existing signaling, such as the UDM parameter configuration creation request (Nudm_ParameterProvision_Create request) message, that is, reusing existing signaling to reduce the implementation difficulty; or it can be new signaling, which is not specifically limited. In addition, Group Creation Request Message #2 can also include other parameters. The specific implementation principle is similar to the relevant introduction in "2.5G LAN" above, which can be referred to for understanding, and will not be repeated here.

[0213] Optionally, the NEF network element can also determine whether to send Group Creation Request Message #2 to the UDM network element or the PCF network element, depending on the group type. For example, for groups whose members are not easily changed, such as 5G VN, the NEF network element can send Group Creation Request Message #2 to the UDM network element to request the UDM network element to create and maintain the group. For groups whose members are easily changed, such as temporary or dynamic groups, the NEF network element can send 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 can also default to sending Group Creation Request Message #2 only to the UDM network element or the PCF network element, without specific limitations.

[0214] For ease of understanding, the following section will use the example of creating and maintaining a group by a UDM / PCF network element.

[0215] UDM / PCF network elements can obtain the group identifier, the identifiers of the corresponding group members, and the internal scope of the group from the group creation request message #2. Optionally, if the group identifier is an external group ID, the UDM / PCF network element can map the external group ID to an internal group ID. Optionally, if the identifier of a group member is an external ID of the group member, the UDM / PCF network element can also map the external ID of the group member to an internal ID of the group member.

[0216] UDM / PCF network elements can create group subscription information or policy information at the group member level (taking subscription information as an example). For instance, a UDM / PCF network element can save the group identifier (external group ID and / or internal group ID), the group's internal scope, and the group type indication information (optional) into the subscription information of each group member within that group. Alternatively, UDM / PCF network elements can create subscription information or policy information at the group level (taking subscription information as an example). For instance, a UDM / PCF network element can save the group identifier, the identifiers of the corresponding group members within the group (group member's external ID and / or group member's internal ID), the group's internal scope, and the group type indication information (optional) as the group's subscription information, or store it in the group's subscription information.

[0217] Furthermore, the group creation response message #2 can be an existing signaling message, such as the UDM parameter configuration creation response message (Nudm_ParameterProvision_Create response), thus reusing existing signaling to reduce implementation difficulty; alternatively, it can be a new signaling message, without specific limitations. Optionally, the group creation response message #2 can also carry a reason value for request failure, such as AF unauthorized.

[0218] S406, the UDM / PCF network element sends a location change subscription message to the AMF network element. Correspondingly, the AMF network element receives the location change subscription message from the UDM / PCF network element.

[0219] Location change subscription messages (denoted as subscription messages) can be used to notify AMF network elements to perform mobility tracking on group members within a group. Subscription messages can be existing signaling, such as the AMF event exposure subscription (Namf_EventExposure_Subscribe) message, reusing existing signaling to reduce implementation difficulty; or they can be new messages, without specific limitations. Subscription messages may include at least one of the following: the internal scope of the group, or the identifier of the corresponding group member within the group. Group members within a group can be served by one or more AMF network elements. For the case where an AMF network element serves multiple group members, the UDM / PCF network element can carry the identifiers of multiple group members in a single subscription message, or it can send a separate subscription message to the AMF network element for each group member; this application embodiment does not specifically limit this approach. For example, if 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 / PCF network element sends subscription message #1 to AMF network element #1 and subscription message #2 to AMF network element #2. Subscription message #1 includes: {service range, UE#1, UE#2}. Alternatively, the UDM / PCF network element sends two subscription messages #1 to AMF network element #1, each subscription message #1 carrying the service range and the identifier of the corresponding UE from UE#1 to UE#2. Subscription message #2 includes: {service range, UE#3}.

[0220] UDM / PCF network elements can determine the AMF network element serving a group member based on the identifier of that group member. For example, a UDM / PCF network element can determine the AMF network element that the SUPI of each group member points to, i.e., the AMF network element serving that group member, based on the SUPI of that group member. Of course, the method by which UDM / PCF network elements determine the AMF can also refer to existing technologies, and there are no specific limitations on this.

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

[0222] Location change notification messages (denoted as notification messages) can be used to indicate the relationship between the location of a group member and the internal scope. The notification message may carry the identifier of the corresponding group member within the group, as well as the group member's location indication information. This location indication information can be used to indicate the relationship between the group member's location and the internal scope. The relationship between the group member's location and the internal scope may include any of the following: the group member has moved out of the internal scope, the group member has moved into the internal scope, the group member is within the internal scope, or the group member is outside the internal scope. Location indication information is merely an exemplary name and can be replaced with any possible name, such as member location indication information, group member location indication information, etc., without being specifically limited. Furthermore, the notification message may also not carry location indication information, such as implicitly indicating the relationship between the group member's location and the internal scope through the notification message type. Alternatively, the notification message may also carry the group member's location so that the UDM / PCF network element can determine the group member's location and the relationship between the group member's location and the internal scope based on the group member's location.

[0223] In addition, notification message #1 can be an existing signaling message, such as the AMF event exposure notification (Namf_EventExposure_Notify) message, which reuses existing signaling to reduce implementation difficulty, or it can be a new message, without specific limitations.

[0224] Taking an AMF (Active Mobile Filter) network element as an example, the AMF network element can perform mobility tracking on group members indicated by the subscribed message. For example, the AMF network element can determine the location of a group member based on the mobility data of the group member reported by the RAN device (e.g., the location of the group member), or the identifier of the RAN device currently accessed by the group member. The AMF network element can then determine whether the group member is within the internal range based on the location of the group member. If the AMF network element determines that the group member is within the internal range (determined when the mobility tracking of the group member is first performed), no notification message needs to be sent, or a notification message may still be sent; there is no specific limitation on this. If the AMF network element determines that the group member has moved out of the internal range, such as moving from a cell within the service range to a cell outside the service range, a notification message is sent to indicate that the group member has moved out of the internal range. If the AMF network element determines that the group member is outside the internal range (determined when the mobility tracking of the group member is first performed), a notification message is sent to indicate that the group member is outside the internal range. If an AMF network element determines that a group member has moved into the inner range, from a cell outside the group's service range to a cell within the service range, it sends a notification message to instruct the group member to move into the inner range.

[0225] S408, UDM network element / PCF network element maintenance group information.

[0226] Among them, the UDM network element / PCF network element can update the status of group members, or update the group members.

[0227] If a notification message instructs a group member to move out of the inner scope, or if a group member is outside the inner scope, the UDM / PCF network element can mark the group member as deactivated or delete the group member. Deactivation indicates that the group member is currently unavailable; that is, the AF may no longer provide service to the group member, but the group member is still within the group. The UDM / PCF network element can remove the group member's identifier from the group's subscription information, or remove the group's identifier and inner scope from the group member's subscription information. After the UDM / PCF network element deletes the group member, the group member may no longer receive services from the AF.

[0228] If a notification message instructs a group member to move into the internal range, the UDM / PCF network element can mark the group member as active or re-add the group member to the group. An active group member indicates that the member is currently available, meaning the AF currently needs or can provide services to that member. The UDM / PCF network element re-adds the group member's identifier to the group's subscription information, or re-adds the group's identifier and internal range to the member's subscription information. If the group member is re-added to the group, AF services should be provided to that member.

[0229] It's understandable that whether a UDM / PCF network element marks the status of a group member, or deletes or re-adds a group member, depends on whether the group's subscription information or the group member's subscription information maintains the group member's status. If the group member's status is maintained, the UDM / PCF network element can mark the group member's status; otherwise, the UDM / PCF network element can delete or re-add a group member.

[0230] S409, UDM network element / PCF network element triggers SMF network element to adjust PDU session.

[0231] Adjusting a PDU session can include releasing a PDU session, deactivating a PDU session, or activating a PDU session.

[0232] If a UDM / PCF network element marks a group member as deactivated or deletes a group member, the UDM / PCF network element can trigger the SMF network element to adjust the PDU session corresponding to that group member. For example, the UDM / PCF network element sends a request message, such as a UDM subscription data management notification (Nudm_SDM_Notification) message, to the SMF network element to notify it to release or deactivate the PDU session corresponding to the UE, thereby optimizing resources and improving equipment operating efficiency. In this case, the SMF network element can trigger the UPF network element to delete the relevant configuration of the PDU session; or, the SMF network element can retain the relevant configuration of the PDU session but mark it as deactivated, indicating that the PDU session is currently unable to transmit data.

[0233] Alternatively, if the UDM / PCF network element marks a group member as active or re-adds the group member to the group, the UDM / PCF network element can also trigger the SMF network element to adjust the PDU session corresponding to the UE. For example, the UDM / PCF network element can send a request message to the SMF network element to notify it to create or activate the PDU session corresponding to the UE to ensure normal service communication. In this way, the SMF network element can create the relevant configuration for the PDU session; or, if the UDM / PCF network element has pre-stored the relevant configuration for the PDU session, the SMF network element can mark the PDU session as active to activate the user plane path of the PDU session and enable data transmission.

[0234] It is understandable that S409 is an optional step. For example, if the adjustment of the PDU session is triggered by other network elements, S409 will not be executed.

[0235] S410, the AMF / SMF network element rejects requests initiated by UEs located outside its internal range.

[0236] AMF network elements can acquire or be configured with an internal range (see S406). Based on this, if a UE sends a registration request message to an AMF network element, the AMF network element can determine whether the UE is within the internal range. If the UE is within the internal range, the AMF network element allows the UE to register with the core network, such as 5GC. If the UE is outside the internal range, the AMF network element refuses the UE's registration with the core network.

[0237] Alternatively, if the AMF network element allows the UE to register with the core network by default, the SMF network element can determine whether to allow the UE to establish a data connection session, such as a PDU session, based on its internal range. For example, the SMF network element can obtain the internal range in advance from the UDM / PCF network element. Subsequently, if the UE initiates a session establishment request message to the SMF network element, the SMF network element can determine whether the UE is within the internal range. If the UE is within the internal range, the SMF network element allows the UE to establish a data connection session. If the SMF network element determines that the UE is outside the internal range, it refuses to establish a data connection session for the UE. As another example, after receiving a session establishment request message from the UE, the SMF network element can request the UDM / PCF network element to determine whether the UE is within the internal range. Subsequently, if the UDM / PCF network element indicates to the SMF network element that the UE is within the internal range, the SMF network element allows the UE to establish a data connection session. If the UDM / PCF network element indicates to the SMF network element that the UE is within range, the SMF network element will refuse to establish a data connection session for the UE.

[0238] S411, the AF sends a group update request message to the NEF network element. Correspondingly, the NEF network element receives the group update request message from the AF.

[0239] For ease of description, in this embodiment of the application, the group update request message sent by AF to NEF network element is marked as group update request message #1.

[0240] Group update request message #1 can be used to request an update of group members. For example, group update request message #1 can carry the group identifier, the identifiers of the corresponding group members, and update instruction information.

[0241] The update indication information is used to indicate any of the following: deleting a group member, re-adding a group member to the group, marking a group member as active, or marking a group member as inactive. For example, the AF can track the service data packets of a group member to determine if the group member's service data packets have not been received for an extended period (e.g., exceeding a preset time). If the group member's service data packets have not been received for an extended period, the AF sends a group update request message #1 to request the deletion of the group member or to mark the group member as inactive. It is understood that the update indication information is only an exemplary name and can be replaced with any possible name, such as member update indication information, group update indication information, etc., without being specifically limited. In addition, the group update request message #1 may also not carry update indication information, such as using the type of group update request message #1 to replace the indication function of update indication information.

[0242] Optionally, the group update request message #1 may also carry the UE's identifier to request that the UE be added to the group, i.e., to add a new group member. The AF can obtain the UE's identifier in the manner described in S401 and determine which group the UE should belong to in the manner described in S402, which will not be elaborated further here.

[0243] Optionally, the group update request message #1 can also be used to update the service scope of the group. For example, the group update request message #1 carries the new service scope of the group. The specific implementation principle of the new service scope can be found in the relevant introduction to service scope above, and will not be repeated here.

[0244] In addition, the group update request message #1 can be existing signaling, such as the NEF parameter configuration update request (Nnef_Parameter Provision_Update request) message, which reuses existing signaling and reduces the difficulty of implementation; or it can be new signaling, without specific restrictions.

[0245] S412, NEF network element verifies AF's permissions.

[0246] After receiving the group update request message #1 from the AF, the NEF network element can determine whether the AF has the authority to update the group. If the AF has the authority, the NEF network element executes S413. If the AF does not have the authority, the NEF network element returns an update group response message to the AF to indicate that the request failed. The update group response message can be existing signaling, such as the NEF parameter configuration update response message (Nnef_ParameterProvision_Update response), i.e., reusing existing signaling to reduce implementation difficulty; or it can be new signaling, without specific limitations. Optionally, the update group response message can also carry a reason value for the request failure, such as AF not authorized.

[0247] It is understandable that S412 is an optional step. For example, if the default AF has permission or the AF is a trusted AF, S412 may not be executed.

[0248] 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.

[0249] For ease of description, in this embodiment of the application, the group update request message sent by the NEF network element to the UDM network element / PCF network element is marked as group update request message #2.

[0250] Group update request message #2 and group update request message #1 may be the same message or different messages. When group update request message #2 and group update request message #1 are different messages, group update request message #2 can be determined based on group update request message #1. For example, group update request message #2 carries the information in group update request message #1 (see S411) to update group members. In addition, group update request message #2 can be existing signaling, such as a UDM parameter configuration update request (Nudm_ParameterProvision_Update request) message, that is, reusing existing signaling to reduce implementation difficulty; or it can be new signaling, without specific limitations.

[0251] UDM / PCF network elements can update groups based on the information in group update request message #2. For example, a UDM / PCF network element can delete a group member, re-add a group member to the group, mark a group member as active, or mark a group member as inactive. Alternatively, a UDM / PCF network element can determine that a UE is not a member of the group based on its identifier and add the UE to the group. For instance, a UDM / PCF network element can add the UE's identifier to the group's subscription information, or add the group's identifier and internal scope to the UE's subscription information. Furthermore, a UDM / PCF network element can subscribe to the UE's mobility from an AMF network element; the specific implementation principle can be found in the relevant descriptions in S406-S408, and will not be elaborated further.

[0252] It is understood that steps S411-S413 are optional; for example, steps S411-S413 will not be executed if group members are not updated. Furthermore, steps S411-S413 are executed after step S405, and the execution order between steps S411-S413 and steps S406-S410 is not specified.

[0253] Scene 2:

[0254] For example, Figure 5 Flowchart of the communication method provided in the embodiments of this application Figure 2 In Scenario 2, when creating a group, the AF can provide the service range of the group to the UDM / PCF network elements through the NEF network element. The NEF network element can instruct the AMF network element to perform mobility tracking of group members according to this service range, so that the UDM / PCF network elements can dynamically update the group members, ensuring that only group members within the service range can obtain the services provided by the AF, thereby guaranteeing that group members can obtain a consistent service experience.

[0255] Specifically, such as Figure 5As shown, the flow of this communication method is as follows:

[0256] S501, the UE reports its identifier to the AF.

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

[0258] The specific implementation principles of S501-S502 are similar to those of S401-S402 mentioned above, and can be understood by referring to them. They will not be repeated here.

[0259] S503, the AF sends a group creation request message #1 to the NEF network element. Correspondingly, the NEF network element receives the group creation request message #1 from the AF.

[0260] Group creation request message #1 may carry at least one of the following: the identifier of the AF, or location change notification information. The identifier of the AF can be the address of the AF, such as the IP address of the AF, used by the NEF network element to access the AF. The identifier of the AF is an optional element; for example, the NEF network element can pre-configure or pre-obtain the identifier of the AF. The location change notification information can be used to instruct the NEF network element to subscribe to the mobility of group members from the AMF network element. The location change notification information is an optional element; for example, the NEF network element can subscribe to the mobility of group members from the AMF network element by default. Furthermore, the location change notification information is only an exemplary name and can be replaced with any possible name, such as location subscription notification information, location update notification information, etc.

[0261] It is understandable that the group creation request message #1 may also contain other information. For the specific implementation principle, please refer to the relevant introduction in S403 above, which will not be repeated here.

[0262] S504, NEF network element verifies AF permissions.

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

[0264] The specific implementation principles of S504-S505 are similar to those of S404-S405 mentioned above, and can be understood by referring to them. They will not be repeated here.

[0265] S506, the NEF network element sends a subscription message to the AMF network element. Correspondingly, the AMF network element receives a read message from the NEF network element.

[0266] The specific implementation principle of S506 can be found in the relevant description in S406 above, and will not be repeated here. Optionally, the subscription message can also carry the AF identifier, so that the AMF network element can directly send a notification message to the AF based on the AF identifier.

[0267] 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.

[0268] Whether an AMF network element sends a notification message to a NEF network element or to an AF network element depends on whether the AMF network element has obtained the AF's identifier. If the AMF network element has obtained the AF's identifier, it can send a notification message to the AF. If the AMF network element has not obtained the AF's identifier, it can send a notification message to the NEF network element.

[0269] If the NEF receives a notification message (denoted as notification message #1), the NEF network element can send a group update request message #2 to the UDM network element / PCF network element based on notification message #1; alternatively, the NEF network element can also send a notification message (denoted as notification message #2) to the AF based on the AF's identifier. Notification message #1 and notification message #2 can be the same message, meaning the NEF directly forwards notification message #1 to the AF. Alternatively, notification message #1 and notification message #2 can be different messages carrying the same information element; there are no specific limitations on this.

[0270] Furthermore, the specific implementation principle of S507 can be found in the relevant introduction in S407 above, and will not be repeated here.

[0271] S508, the AF sends a group update request message #1 to the NEF network element. Correspondingly, the NEF network element receives the group update request message #1 from the AF.

[0272] S509, NEF network element verifies AF's permissions.

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

[0274] The specific implementation principles of S508-S510 are similar to those of S408, S411-S413 mentioned above, and can be understood by referring to them. They will not be repeated here.

[0275] S511, UDM network element / PCF network element triggers adjustment of PDU session.

[0276] S512, AMF network element / SMF network element rejects requests initiated by UEs located outside the internal range.

[0277] The specific implementation principles of S511-S512 are similar to those of S409-S410 above, and can be understood by reference, so they will not be repeated here.

[0278] Scene 3:

[0279] For example, Figure 6 Flowchart of the communication method provided in the embodiments of this application Figure 3 In Scenario 3, when creating a group, the AF can directly provide the service range of the group to the UDM / PCF network element. The UDM / PCF network element can instruct the AMF network element to perform mobility tracking of group members according to this service range, so that the UDM / PCF network element can dynamically update the group members and ensure that only group members within the service range can obtain the services provided by the AF, thereby ensuring that group members can obtain a consistent service experience.

[0280] S601, the UE reports its identifier to the AF.

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

[0282] The specific implementation principles of S601-S602 are similar to those of S401-S402 mentioned above, and can be understood by referring to them, so they will not be repeated here.

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

[0284] A group creation request message can be used to request the creation of one or more groups as determined in S602. For example, a group creation request message may include at least one of the following: a group identifier, the identifiers of the corresponding group members within the group, or the service scope of the group. The AF may pre-configure the addresses of UDM / PCF network elements to send group creation request messages to the UDM / PCF network elements accordingly.

[0285] Furthermore, the specific implementation principle of S603 is similar to that of S405 mentioned above, and can be understood by referring to it, so it will not be repeated here.

[0286] S604, the UDM / PCF network element sends a subscription message to the AMF network element. Correspondingly, the AMF network element receives the subscription message from the UDM / PCF network element.

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

[0288] S606, UDM network element / PCF network element maintenance group.

[0289] S607, UDM network element / PCF network element triggers adjustment of PDU session.

[0290] S608, AMF / SMF network elements reject requests initiated by UEs located outside their internal range.

[0291] The specific implementation principles of S604-S608 are similar to those of S406-S410 mentioned above, and can be understood by referring to them, so they will not be repeated here.

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

[0293] The group update request message can be used to request updates to group members. For details on the implementation principle, please refer to the relevant introduction in S413 above, which will not be repeated here.

[0294] Scene 4:

[0295] For example, Figure 7 Flowchart of the communication method provided in the embodiments of this application Figure 4 In Scenario 4, when creating a group, the AF can directly provide the service range of the group to the UDM / PCF network element. The AF can also instruct the AMF network element to perform mobility tracking of group members according to this service range, so that the UDM / PCF network element can dynamically update the group members and ensure that only group members within the service range can obtain the services provided by the AF, thereby ensuring that group members can obtain a consistent service experience.

[0296] S701, the UE reports its identifier to the AF.

[0297] S702, AF determines the group to be created and the service scope of that group.

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

[0299] The specific implementation principles of S701-S702 are similar to those of S401-S402 above, and the specific implementation principle of S703 is similar to that of 603 above. They can be understood by reference and will not be repeated here.

[0300] S704, AF sends a subscription message to the AMF network element. Correspondingly, the AMF network element receives the subscription message from the NEF network element.

[0301] The specific implementation principle of S704 can be found in the relevant descriptions of S406 and S506 above, and will not be repeated here.

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

[0303] The specific implementation principle of S705 can be found in the relevant descriptions in S407 and S507 above, and will not be repeated here.

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

[0305] S707, UDM network element / PCF network element triggers adjustment of PDU session.

[0306] S708, AMF / SMF network elements reject requests initiated by UEs located outside their internal range.

[0307] The specific implementation principles of S704-S708 are similar to those of S406-S410 mentioned above, and can be understood by referring to them, so they will not be repeated here.

[0308] The above combination Figures 4-7 The communication method provided in the embodiments of this application is described in detail in various scenarios. The following, in conjunction with... Figure 8 The overall process of this communication method is described.

[0309] For example, Figure 8 Flowchart of the communication method provided in the embodiments of this application Figure 5 This communication method is applicable to the aforementioned communication system and is used to enable communication between application network elements, capability-opening network elements, and core network elements (such as data storage network elements or policy control network elements). The application network element can be the aforementioned AF, the capability-opening network element can be the aforementioned NEF network element, and the core network element can be the aforementioned UDM network element / PCF network element. For example... Figure 8 As shown, the flow of this communication method is as follows:

[0310] S801, the capability open network element receives a group creation request message #1 from the application network element.

[0311] The group creation request message #1 may include a group identifier, the group members included in the group corresponding to the group identifier, and the service scope of the group. The service scope is used to indicate the restricted area where group members can access services provided by application network elements.

[0312] The service scope of a group can be the service scope of the application network element. That is, the service scope of the group can be determined based on the existing service scope of the application network element, eliminating the need for additional service scope configuration for the application network element, thus reducing configuration complexity and facilitating flexible deployment. Optionally, the application network element includes at least one of the following: one or more Edge Application Servers (EAS), or one or more Edge Enabler Servers (EES) corresponding to EAS. The service scope of the application network element includes at least one of the following: a set of service scopes for one or more EAS, or the service scope of the EES. In this case, multiple EAS can provide services to the group through load balancing, resulting in a better user experience. Furthermore, these EAS can also share the service scope of the EES (i.e., the service scope of the group is the service scope of the EES), thus eliminating the need for additional service scope configuration for each EAS, reducing configuration complexity and facilitating flexible deployment.

[0313] The service area can be represented by at least one of the following: geographic location information or network location information. In other words, application network elements can choose the representation method of the service area based on the capabilities of the capability-opening network element to ensure that the capability-opening network element can identify the service area. For example, if the capability-opening network element supports geographic location, the application network element can use geographic location information to represent the service area. For example, geographic location information includes at least one of the following: geographic identification information or latitude and longitude information. Alternatively, if the capability-opening network element supports network location, the application network element can use network location information to represent the service area. For example, network location information includes at least one of the following: DNAI, TAI, TAI list, area identifier, area identifier list, cell identifier, or cell identifier list.

[0314] Furthermore, the specific implementation principle of S801 can be found in the relevant descriptions in S401-S404 above, and will not be repeated here.

[0315] S802, the capability-opening network element sends a group creation request message #2 to the core network element based on the group creation request message #1. Correspondingly, the core network element receives the group creation request message #2 from the capability-opening network element.

[0316] The group creation request message #2 may include a group identifier, the group members included in the group corresponding to the group identifier, and the internal scope of the group. The internal scope is used to indicate the restricted area where group members can access services provided by application network elements.

[0317] In one possible implementation, the internal range is mapped from the service range, and this internal range is a range that the operator network or core network can recognize, thus avoiding group creation failure due to the operator network or core network's inability to recognize the service range. For example, the capability open network element can map the service range to an internal range that the operator network can recognize, and send the group identifier, group members, and internal range to the core network element (such as a data storage network element or a policy control network element). Alternatively, in another possible implementation, the internal range can be the same as the service range, i.e., the service range is already a range that the operator network or core network can recognize. In this case, the capability open network element does not need to perform mapping, thus saving the capability open network element's overhead. That is, the capability open network element can directly send the group identifier, group members, and service range to the core network element (such as a data storage network element or a policy control network element). It can be understood that the capability open network element sends the group creation request message #2 to the core network element based on the group creation request message #1, or it can be considered that the capability open network element triggers group management based on the group creation request message #1.

[0318] Optionally, the capability-opening network element can also determine the group type based on the group creation request message #1, and send a group creation request message #2 to the core network element according to the group type. The group type can be either a temporary group or a dynamic group. It should be noted that because temporary or dynamic groups are highly random—for example, the locations of group members change frequently, and even the group members themselves change frequently—it is necessary to limit the service scope to ensure the service quality of temporary groups. It can be seen that different core network elements can provide services for different types of groups to achieve differentiated services and match the specific needs of each group. For example, temporary or dynamic groups can be provided by policy control network elements. For 5G VN, data storage network elements can provide services.

[0319] Optionally, the group creation request message #1 may carry group type indication information. This information indicates the type of the group, enabling the capability-opening network element to accurately determine its type. Alternatively, the group type can be indicated in other ways, such as implicitly indicating the group type through the type of the group creation request message #1; no specific limitation is made in this regard.

[0320] Furthermore, the specific implementation principle of S802 can be found in the relevant introduction in S405 above, and will not be repeated here.

[0321] S803, core network element associated storage group identifier, group members, and internal scope.

[0322] The core network elements can store the group identifier, group members, and internal scope in the group's subscription information for centralized storage, facilitating subsequent retrieval. Alternatively, the core network elements can store the group identifier and internal scope in the group members' subscription information for distributed storage, improving storage space utilization.

[0323] It should be noted that the group identifier stored in the core network element storage can be either an external group identifier or an internal group identifier. An internal group identifier can be a group identifier that can be recognized by the operator network or the core network. Similarly, the group member stored in the core network element storage can be either an external identifier (ID) or an internal identifier (ID) of the group member. An internal identifier of the group member can be an identifier that can be recognized by the operator network or the core network.

[0324] Furthermore, the specific implementation principle of S803 can be found in the relevant introduction in S405 above, and will not be repeated here.

[0325] In summary, based on the methods described above, the service range or internal scope of a group can indicate the restricted area within which group members can access the services provided by the application network element. That is, group members can only obtain services from the application network element within the restricted area; otherwise, they cannot. This ensures that all group members receiving services are located within the restricted area provided by the application network element, thereby guaranteeing a consistent service experience for all group members.

[0326] Optionally, in one possible design scheme, in the communication method provided in this application embodiment, the capability open network element can send a location change subscription message to the mobility management network element corresponding to the group member, and receive a location change notification message from the mobility management network element. The subscription message carries an internal range / service range, and the notification message indicates the relationship between the group member's location and the internal range / service range. The relationship between the group member's location and the service range / internal range includes any one or more of the following: the group member moves into the service range / internal range; the group member moves out of the service range / internal range; the group member is within the service range / internal range; or, the group member is outside the service range / internal range. In this way, the capability open network element can promptly and accurately determine whether a group member is within the internal range, or in other words, determine the event of a group member moving into or out of the internal range.

[0327] After receiving the notification message, the capability-open network element can also send a location change notification message to the application network element and receive a group update request message #1 from the application network element. Based on group update request message #1, it then sends a group update request message #2 to the core network element. Both group update request message #1 and update request message #2 can be used to request group updates. In other words, the capability-open network element does not directly transmit group update request message #1, but rather converts it into a message that the core network element can recognize, such as group update request message #2, to avoid group updates failing due to the core network element's inability to recognize the group update request message.

[0328] Alternatively, after receiving the notification message, the capability-opening network element can directly send a group update request message #2 to the core network element based on the location change notification message. Group update request message #2 is used to request group updates. That is, the capability-opening network element can directly request the core network element to update the group without going through the application network element, thereby reducing communication latency. In this case, optionally, the capability-opening network element can receive location change notification indication information from the application network element in advance. This location change notification indication information is used to instruct the capability-opening network element to subscribe to the location changes of group members. Thus, the capability-opening network element can send a location change subscription message to the mobility management network element corresponding to the group member according to the indication of the location change notification indication information, ensuring that the capability-opening network element can promptly know whether the group member is within the service range / internal range. Of course, the capability-opening network element can also send the location change subscription message to the mobility management network element corresponding to the group member by default; there is no specific limitation on this.

[0329] Upon receiving group update request message #2, the core network element can update the group according to the message. For example, updating the group may include at least one of the following: deleting a group member, re-adding a group member to the group, marking a group member as active, marking a group member as deactivated, or adding a new group member. This enables dynamic group management, ensuring that group members within the internal scope can access the services provided by the application network element.

[0330] Furthermore, the specific implementation principle of this design scheme can be found in the relevant descriptions in S408, S411-S413, and S506-S510 above, and will not be repeated here.

[0331] Optionally, in one possible design scheme, in the communication method provided in this application embodiment, the core network element can send a location change subscription message to the mobility management network element corresponding to the group member, and receive a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range, so that the core network element can promptly know whether the group member is within the internal range.

[0332] Based on this, core network elements can update the group according to the relationship between the group member's location and the internal range, ensuring that group members within the internal range can receive services provided by the application network elements. For example, if a group member is outside the internal range or moves out of the internal range, the core network element deletes the group member or marks it as deactivated, ensuring that the group member can no longer receive services from the application network elements. Alternatively, if a group member moves into the service range, the core network element re-adds the group member to the group or marks it as active, ensuring that the group member can regain access to services from the application network elements.

[0333] Furthermore, the specific implementation principle of this design scheme can be referred to in the relevant introductions in S406-S408 above, and will not be repeated here.

[0334] Optionally, in one possible design scheme, in the communication method provided in this application embodiment, the core network element triggers the session management network element to manage the Protocol Data Unit (PDU) session corresponding to the group member based on the relationship between the group member's location and the internal range. For example, if the group member is outside the internal range or moves out of the internal range, the core network element triggers the session management network element to release the PDU session or mark the PDU session as deactivated, thereby improving the resource utilization of the session management network element and avoiding resource waste caused by maintaining redundant PDU sessions. As another example, if the group member is within the service range or moves into the service range, the core network element triggers the session management network element to create a PDU session or mark the PDU session as active, ensuring that the group member can regain access to the services provided by the application network element through the PDU session.

[0335] Furthermore, the specific implementation principle of this design scheme can be referred to in the relevant introduction in S409 above, and will not be repeated here.

[0336] Optionally, in one possible design scheme, in the communication method provided in the embodiments of this application, the core network element also reserves the ability to send an internal range to the session management network element. This internal range can be used to indicate the restricted area where the session management network element allows the establishment of sessions, ensuring that the session management network element can only establish sessions for terminals within the internal range. Alternatively, the core network element can also receive the identifier of the terminal from the session management network element, and, based on the identifier of the terminal, indicate to the session management network element whether the terminal is within the internal range, ensuring that the session management network element only allows the terminal to establish a session if the terminal is within the internal range.

[0337] Furthermore, the specific implementation principle of this design scheme can be referred to in the relevant introduction in S410 above, and will not be repeated here.

[0338] It should be noted that the communication processes provided in the above method embodiments are merely examples and are not intended to be limiting. For instance, application network elements may also interact directly with core network elements without going through capability-opening network elements. The specific implementation principles can be found in the relevant descriptions in scenarios 3-4 above, and will not be repeated here.

[0339] The above combination Figures 4-8 The communication method provided in the embodiments of this application is described in detail below. Figures 9-10 This document describes in detail the communication apparatus used to perform the communication method provided in the embodiments of this application.

[0340] For example, Figure 9 This is a schematic diagram of the structure of the communication device provided in the embodiments of this application. Figure 1 .like Figure 9 As shown, the communication device 900 includes a transceiver module 901 and a processing module 902. For ease of explanation, Figure 9 Only the main components of the communication device are shown.

[0341] In some embodiments, the communication device 900 may be adapted to Figure 3 In the communication system shown, the following is performed: Figures 4-5 The method shown describes the function of the NEF network element, or the execution of functions such as... Figure 8 The method shown enables the functionality of open network elements.

[0342] The transceiver module 901 is used to receive group creation request message #1 from the application network element. The processing module 902 is used to trigger group management based on the group creation request message #1. The group creation request message includes a group identifier (#1), the group members included in the group corresponding to the group identifier, and the service scope of the group; the service scope is used to indicate the restricted area where group members can access services provided by the application network element.

[0343] In one possible design, the service range of the group can be the service range of the application network element.

[0344] Optionally, the application network element may include at least one of the following: one or more Edge Application Servers (EAS), or one or more Edge Enabler Servers (EES) corresponding to EAS. The service scope of the application network element may include at least one of the following: a set of service scopes for one or more EAS, or the service scope of an EES.

[0345] In one possible design, the service area can be represented by at least one of the following: geographic location information or network location information. Optionally, the geographic location information may include at least one of the following: geographic identification information or latitude and longitude information. Optionally, the network location information may include at least one of the following: DNAI, TAI, TAI list, area identifier, area identifier list, cell identifier, or cell identifier list.

[0346] In one possible design, the processing module 902 is further configured to map the service range to an internal range that can be recognized by the operator network or the core network, and control the transceiver module 901 to send the group identifier, group members, and internal range to the core network element. The internal range is used to instruct the group members on the restricted area for obtaining services provided by the application network element.

[0347] Optionally, the transceiver module 901 is further configured to send a location change subscription message to the mobility management network element corresponding to the group member, and receive a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range.

[0348] Furthermore, the relationship between the position of a group member and the inner range includes any one or more of the following: a group member moves into the inner range; a group member moves out of the inner range; a group member is within the inner range; or, a group member is outside the inner range.

[0349] Alternatively, the processing module 902 is also used to control the transceiver module 901 to send the group identifier, group members, and service range of the group to the core network elements.

[0350] Optionally, the transceiver module 901 is further configured to send a location change subscription message to the mobility management network element corresponding to the group member, and receive a location change notification message from the mobility management network element. The subscription message carries the service range, and the notification message indicates the relationship between the group member's location and the service range.

[0351] Furthermore, the relationship between the location of a group member and the service area includes any one or more of the following: a group member moves into the service area; a group member moves out of the service area; a group member is within the service area; or, a group member is outside the service area.

[0352] Furthermore, the transceiver module 901 is also used to send a location change notification message to the application network element and receive a group update request message #1 from the application network element; the processing module 902 is also used 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. The group update request message #1 is used to request an update of the group, and the update request message #2 is also used to request an update of the group.

[0353] Optionally, the processing module 902 is also configured to control the transceiver module 901 to send a group update request message #2 to the core network element based on the location change notification message. The group update request message #2 is used to request an update of the group.

[0354] Optionally, the transceiver module 901 is also configured to receive location change notification information from the application network element. The location change notification information is used to indicate the location changes of members in the capability open network element subscription group.

[0355] Optionally, the transceiver module 901 may include a transmitting module ( Figure 9 (not shown in the image) and receiving module ( Figure 9 (Not shown in the diagram). The transmitting module implements the transmitting function of the communication device 900, and the receiving module implements the receiving function of the communication device 900.

[0356] Optionally, the communication device 900 may also include a storage module. Figure 9 (Not shown in the image), the storage module stores programs or instructions. When the processing module 902 executes the program or instructions, the communication device 900 can perform actions such as... Figures 4-5 The method shown describes the function of the NEF network element, or the execution of functions such as... Figure 8 The method shown enables the functionality of open network elements.

[0357] It should be noted that the communication device 900 may be a network device, a chip (system) or other component or assembly that can be set in a network device, or a device that includes a network device. This application does not limit this.

[0358] In addition, the technical effects of the communication device 900 can be referenced. Figures 4-8 The technical effects of the communication method shown will not be elaborated here.

[0359] In other embodiments, the communication device 900 may be adapted to Figure 3In the communication system shown, the following is performed: Figures 4-7 The method shown describes the functions of the UDM / PCF network element, or the execution of functions such as... Figure 8 The method shown illustrates the functions of the core network elements.

[0360] The transceiver module 901 receives a group creation request message #2 from the capability-opening network element. The group creation request message #2 includes a group identifier, the group members included in the group corresponding to the group identifier, and the internal scope of the group. The internal scope indicates the restricted area where group members can access services provided by the application network element. The processing module 902 then associates and stores the group identifier, group members, and internal scope.

[0361] In one possible design, the processing module 902 is also used to update the group based on the relationship between the position of the group members and the internal scope.

[0362] Optionally, if a group member is outside the inner scope or moves out of the inner scope, the processing module 902 is further configured to delete the group member or mark the group member as deactivated. Alternatively, if a group member moves into the service scope, the processing module 902 is further configured to re-add the group member to the group or mark the group member as active.

[0363] In one possible design, processing module 902 is further configured to trigger the session management network element to manage the PDU session corresponding to the group member based on the relationship between the group member's location and the internal range. Optionally, if the group member is outside the internal range or moves out of the internal range, processing module 902 is further configured to trigger the session management network element to release the PDU session or mark the PDU session as deactivated. Optionally, if the group member is within the service range or moves into the service range, processing module 902 is further configured to trigger the session management network element to create a PDU session or mark the PDU session as active.

[0364] Optionally, the transceiver module 901 is further configured to send a location change subscription message to the mobility management network element corresponding to the group member, and receive a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range.

[0365] In one possible design, the transceiver module 901 is further configured to receive a group update request message #2 from the capability open network element, whereby the group update request message #2 requests an update to the group. Thus, the processing module 902 is further configured to update the group based on the group update request message #2. For example, updating the group may include at least one of the following: deleting a group member, re-adding a group member to the group, marking a group member as active, marking a group member as deactivated, or adding a new group member.

[0366] In one possible design, processing module 902 is further configured to store the group identifier, group members, and internal scope into the group's contract information or policy information. Alternatively, processing module 902 is further configured to store the group identifier and internal scope into the group members' contract information or policy information.

[0367] In one possible design, the transceiver module 901 is further configured to send the internal range to the session management network element. Alternatively, the transceiver module 901 is further configured to receive the terminal identifier 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 the internal range based on the terminal identifier.

[0368] Optionally, the transceiver module 901 may include a transmitting module ( Figure 9 (not shown in the image) and receiving module ( Figure 9 (Not shown in the diagram). The transmitting module implements the transmitting function of the communication device 900, and the receiving module implements the receiving function of the communication device 900.

[0369] Optionally, the communication device 900 may also include a storage module. Figure 9 (Not shown in the image), the storage module stores programs or instructions. When the processing module 902 executes the program or instructions, the communication device 900 can perform actions such as... Figures 4-7 The method shown describes the functions of the UDM / PCF network element, or the execution of functions such as... Figure 8 The method shown illustrates the functions of the core network elements.

[0370] It should be noted that the communication device 900 may be a network device, a chip (system) or other component or assembly that can be set in a network device, or a device that includes a network device. This application does not limit this.

[0371] In addition, the technical effects of the communication device 900 can be referenced. Figures 4-8 The technical effects of the communication method shown will not be elaborated here.

[0372] For example, Figure 10 Schematic diagram of the communication device provided in the embodiments of this application Figure 2 The communication device can be a terminal, or a chip (system) or other component or assembly that can be set in the terminal. For example... Figure 10 As shown, 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. The processor 1001 is coupled to the memory 1002 and the transceiver 1003, for example, they may be connected via a communication bus.

[0373] The following is combined with Figure 10 A detailed description of each component of the communication device 1000 is provided below:

[0374] The processor 1001 is the control center of the communication device 1000. It can be a single processor or a collective term for multiple processing elements. For example, the processor 1001 can be one or more central processing units (CPUs), application-specific integrated circuits (ASICs), or one or more integrated circuits configured to implement the embodiments of this application, such as one or more digital signal processors (DSPs), or one or more field-programmable gate arrays (FPGAs).

[0375] Optionally, the processor 1001 can perform various functions of the communication device 1000, such as the functions described above, by running or executing software programs stored in the memory 1002 and calling data stored in the memory 1002. Figures 4-8 The communication method shown.

[0376] In a specific implementation, as one example, the processor 1001 may include one or more CPUs, for example... Figure 10 CPU0 and CPU1 are shown in the diagram.

[0377] In a specific implementation, as one example, the communication device 1000 may also include multiple processors, for example... Figure 10 The processors 1001 and 1004 are shown. Each of these processors can be a single-core processor or a multi-core processor. Here, "processor" can refer to one or more devices, circuits, and / or processing cores used to process data (e.g., computer program instructions).

[0378] The memory 1002 is used to store the software program that executes the solution of this application, and is controlled by the processor 1001 to execute it. The specific implementation method can be referred to the above method embodiment, and will not be repeated here.

[0379] Optionally, the memory 1002 may be a read-only memory (ROM) or other type of static storage device capable of storing static information and instructions, random access memory (RAM) or other type of dynamic storage device capable of storing information and instructions, or electrically erasable programmable read-only memory (EEPROM), compact disc read-only memory (CD-ROM) or other optical disc storage, optical disc storage (including compressed optical discs, laser discs, optical discs, digital universal optical discs, Blu-ray discs, etc.), magnetic disk storage media or other magnetic storage devices, or any other medium capable of carrying or storing desired program code in the form of instructions or data structures and accessible by a computer, but not limited thereto. The memory 1002 may be integrated with the processor 1001 or exist independently, and may be connected via the interface circuit of the communication device 1000. Figure 10 (Not shown in the image) is coupled to the processor 1001, and this embodiment does not specifically limit this.

[0380] Transceiver 1003 is used for communication with other communication devices. For example, if communication device 1000 is a terminal, transceiver 1003 can be used to communicate with a network device or with another terminal device. As another example, if communication device 1000 is a network device, transceiver 1003 can be used to communicate with a terminal or with another network device.

[0381] Optionally, transceiver 1003 may include a receiver and a transmitter. Figure 10 (Not shown separately). The receiver is used to implement the receiving function, and the transmitter is used to implement the sending function.

[0382] Optionally, the transceiver 1003 can be integrated with the processor 1001, or it can exist independently and be connected via the interface circuit of the communication device 1000. Figure 10 (Not shown in the image) is coupled to the processor 1001, and this embodiment does not specifically limit this.

[0383] It should be noted that, Figure 10The structure of the communication device 1000 shown does not constitute a limitation on the communication device. Actual communication devices may include more or fewer components than shown, or combine certain components, or have different component arrangements.

[0384] Furthermore, the technical effects of the communication device 1000 can be referred to the technical effects of the communication method described in the above method embodiments, and will not be repeated here.

[0385] This application provides a communication system. The communication system includes: Figures 4-7 One or more NEF network elements are shown, and Figures 4-7 One or more UDM network elements / PCF network elements are shown; or, the communication system includes: Figure 8 One or more open network elements with the capabilities shown, and Figure 8 One or more core network elements are shown.

[0386] For example, an open capability network element receives a group creation request message #1 from an application network element and, based on group creation request message #1, sends a group creation request message #2 to a core network element. The core network element receives group creation request message #2 from the open capability network element, thereby associating and storing the group identifier, group members, and the group's internal scope. Group creation request message #1 includes the group identifier, the group members included in the group corresponding to the group identifier, and the group's service scope, which indicates the restricted area where group members can access services provided by the application network element. Group creation request message #2 includes the group identifier, group members, and the internal scope, which indicates the restricted area where group members can access services provided by the application network element.

[0387] In one possible design, the internal range can be the same as the service range. Alternatively, the internal range can be mapped from the service range, and this internal range is a range that the operator network or core network can recognize.

[0388] In one possible design, the service range of the group is the same as the service range of the application network element.

[0389] Optionally, the application network element includes at least one of the following: one or more Edge Application Servers (EAS), or one or more Edge Enabler Servers (EES) corresponding to EAS. The service scope of the application network element includes at least one of the following: a set of service scopes for one or more EAS, or the service scope of an EES.

[0390] In one possible design, the service area is characterized by at least one of the following: geographic location information or network location information. Optionally, the geographic location information may include at least one of the following: geographic identifier information or latitude and longitude information. Optionally, the network location information may include at least one of the following: DNAI, TAI, TAI list, area identifier, area identifier list, cell identifier, or cell identifier list.

[0391] Optionally, the capability-opening network element is also used to send a location change subscription message to the mobility management network element corresponding to the group member, and to receive a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range. For example, the relationship between the group member's location and the internal range may include any one or more of the following: the group member moves into the internal range; the group member moves out of the internal range; the group member is within the internal range; or, the group member is outside the internal range.

[0392] Optionally, the capability-opening network element is also used to send a location change subscription message to the mobility management network element corresponding to the group member, and to receive a location change notification message from the mobility management network element. The subscription message carries the service range, and the notification message indicates the relationship between the group member's location and the service range. For example, the relationship between the group member's location and the service range includes any one or more of the following: the group member moves into the service range; the group member moves out of the service range; the group member is within the service range; or, the group member is outside the service range.

[0393] Furthermore, the capability-opening network element is also used to send location change notification messages to application network elements and receive group update request messages #1 from application network elements, thereby sending group update request messages #2 to core network elements based on group update request messages #1. Specifically, group update request message #1 is used to request an update to the group, and update request message #2 is used to request an update to the group.

[0394] Optionally, the capability-opening network element is also used to send a group update request message #2 to the core network element based on the location change notification message. The group update request message #2 is used to request an update to the group.

[0395] Optionally, the capability-opening network element is also configured to receive location change notification indication information from the application network element. The location change notification indication information is used to instruct the capability-opening network element to subscribe to location changes of group members. Thus, the capability-opening network element is also configured to send location change subscription messages to the mobility management network element corresponding to the group member based on the location change notification indication information.

[0396] In one possible design, the capability open network element is also used to determine the type of the group based on the group creation request message #1, and send the group creation request message #2 to the core network element based on the group type.

[0397] Optionally, the group creation request message #1 carries group type indication information, which is used to indicate the type of group.

[0398] Optionally, the group type can be a temporary group or a dynamic group.

[0399] In one possible design, the core network element is also used to update the group based on the relationship between the location of the group members and the internal scope.

[0400] Optionally, if a group member is outside the service area or moves out of the service area, the core network element may also delete the group member or mark the group member as deactivated. Alternatively, if a group member moves into the service area, the core network element may also re-add the group member to the group or mark the group member as active.

[0401] In one possible design, the core network element is also used to trigger the session management network element to manage the PDU sessions corresponding to the group members based on the relationship between the group members' locations and the internal scope. For example, if a group member is outside the internal scope or moves out of the internal scope, the core network element is also used to trigger the session management network element to release the PDU session or mark the PDU session as deactivated. As another example, if a group member is within the service range or moves into the service range, the core network element is also used to trigger the session management network element to create a PDU session or mark the PDU session as active.

[0402] Optionally, the core network element is also used to send a location change subscription message to the mobility management network element corresponding to the group member, and to receive a location change notification message from the mobility management network element. The subscription message carries an internal range, and the notification message indicates the relationship between the group member's location and the internal range.

[0403] In one possible design, the core network element is further configured to receive a group update request message #2 from a capability-opening network element. Group update request message #2 is used to request an update to the group. Thus, the core network element is also configured to update the group based on the group update request message #2. For example, updating the group may include at least one of the following: deleting a group member, re-adding a group member to the group, marking a group member as active, marking a group member as deactivated, or adding a new group member.

[0404] In one possible design, the core network element is also used to store the group identifier, group members, and internal scope in the group's subscription information or policy information. Alternatively, the core network element is also used to store the group identifier and internal scope in the group members' subscription information or policy information.

[0405] In one possible design, the core network element is also used to send the internal range to the session management network element. Alternatively, the core network element is also used to receive the terminal identifier from the session management network element and, based on the terminal identifier, indicate to the session management network element whether the terminal is within the internal range.

[0406] In one possible design, the core network element is either a data storage network element or a policy control network element.

[0407] It should be understood that the processor in the embodiments of this application can be a central processing unit (CPU), or it can be other general-purpose processors, digital signal processors (DSPs), application-specific integrated circuits (ASICs), field-programmable gate arrays (FPGAs), or other programmable logic devices, discrete gate or transistor logic devices, discrete hardware components, etc. The general-purpose processor can be a microprocessor or any conventional processor.

[0408] It should also be understood that the memory in the embodiments of this application can be volatile memory or non-volatile memory, or may include both volatile and non-volatile memory. The non-volatile memory can be read-only memory (ROM), programmable read-only memory (PROM), erasable programmable read-only memory (EPROM), electrically erasable programmable read-only memory (EEPROM), or flash memory. The volatile memory can be random access memory (RAM), which is used as an external cache. By way of example, but not limitation, many forms of random access memory (RAM) are available, such as static RAM (SRAM), dynamic RAM (DRAM), synchronous DRAM (SDRAM), double data rate synchronous DRAM (DDR SDRAM), enhanced synchronous DRAM (ESDRAM), synchronous linked DRAM (SLDRAM), and direct rambus RAM (DR RAM).

[0409] The above embodiments can be implemented, in whole or in part, by software, hardware (such as circuits), firmware, or any other combination thereof. When implemented using software, the above embodiments can be implemented, in whole or in part, in the form of a computer program product. The computer program product includes one or more computer instructions or computer programs. When the computer instructions or computer programs are loaded or executed on a computer, all or part of the processes or functions described in the embodiments of this application are generated. The computer can be a general-purpose computer, a special-purpose computer, a computer network, or other programmable device. The computer instructions can be stored in a computer-readable storage medium or transmitted from one computer-readable storage medium to another. For example, the computer instructions can be transmitted from one website, computer, server, or data center to another website, computer, server, or data center via wired (e.g., infrared, wireless, microwave, etc.) means. The computer-readable storage medium can be any available medium that a computer can access or a data storage device such as a server or data center that includes one or more sets of available media. The available medium can be a magnetic medium (e.g., floppy disk, hard disk, magnetic tape), an optical medium (e.g., DVD), or a semiconductor medium. A semiconductor medium can be a solid-state drive.

[0410] It should be understood that the term "and / or" in this article is merely a description of the relationship between related objects, indicating that three relationships can exist. For example, A and / or B can represent: A existing alone, A and B existing simultaneously, or B existing alone. A and B can be singular or plural. Additionally, the character " / " in this article generally indicates an "or" relationship between the preceding and following related objects, but it can also represent an "and / or" relationship. Please refer to the context for a more accurate understanding.

[0411] In this application, "at least one" means one or more, and "more than one" means two or more. "At least one of the following" or similar expressions refer to any combination of these items, including any combination of single or multiple items. For example, at least one of a, b, or c can mean: a, b, c, ab, ac, bc, or abc, where a, b, and c can be single or multiple.

[0412] It should be understood that in the various embodiments of this application, the order of the above-mentioned processes does not imply the order of execution. The execution order of each process should be determined by its function and internal logic, and should not constitute any limitation on the implementation process of the embodiments of this application.

[0413] Those skilled in the art will recognize that the units and algorithm steps of the various examples described in conjunction with the embodiments disclosed herein can be implemented in electronic hardware, or a combination of computer software and electronic hardware. Whether these functions are implemented in hardware or software depends on the specific application and design constraints of the technical solution. Those skilled in the art can use different methods to implement the described functions for each specific application, but such implementation should not be considered beyond the scope of this application.

[0414] Those skilled in the art will understand that, for the sake of convenience and brevity, the specific working processes of the systems, devices, and units described above can be referred to the corresponding processes in the foregoing method embodiments, and will not be repeated here.

[0415] In the several embodiments provided in this application, it should be understood that the disclosed systems, apparatuses, and methods can be implemented in other ways. For example, the apparatus embodiments described above are merely illustrative; for instance, the division of units is only a logical functional division, and in actual implementation, there may be other division methods. For example, multiple units or components may be combined or integrated into another system, or some features may be ignored or not executed. Furthermore, the coupling or direct coupling or communication connection shown or discussed may be through some interfaces; the indirect coupling or communication connection between apparatuses or units may be electrical, mechanical, or other forms.

[0416] The units described as separate components may or may not be physically separate. The components shown as units may or may not be physical units; that is, they may be located in one place or distributed across multiple network units. Some or all of the units can be selected to achieve the purpose of this embodiment according to actual needs.

[0417] In addition, the functional units in the various embodiments of this application can be integrated into one processing unit, or each unit can exist physically separately, or two or more units can be integrated into one unit.

[0418] If the aforementioned functions are implemented as software functional units and sold or used as independent products, they can be stored in a computer-readable storage medium. Based on this understanding, the technical solution of this application, in essence, or the part that contributes to the prior art, or a portion of the technical solution, can be embodied in the form of a software product. This computer software product is stored in a storage medium and includes several instructions to cause a computer device (which may be a personal computer, server, or network device, etc.) to execute all or part of the steps of the methods described in the various embodiments of this application. The aforementioned storage medium includes various media capable of storing program code, such as USB flash drives, portable hard drives, read-only memory (ROM), random access memory (RAM), magnetic disks, or optical disks.

[0419] The above description is merely a specific embodiment of this application, but the scope of protection of this application is not limited thereto. Any variations or substitutions that can be easily conceived by those skilled in the art within the scope of the technology disclosed in this application should be included within the scope of protection of this application. Therefore, the scope of protection of this application should be determined by the scope of the claims.

Claims

1. A communication method, characterized in that, The method includes: The capability open network element receives a group creation request message #1 from the application network element; the group creation request message #1 includes a group identifier, the group members included in the group corresponding to the group identifier, and the service scope of the group; the service scope is used to indicate the restricted area for the group members to obtain the services provided by the application network element; 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; the group creation request message #2 includes: the group identifier, the group members, and the internal scope of the group; the internal scope is used to indicate the restricted area for the group members to obtain the services provided by the application network element. The core network element receives a group creation request message #2 from the capability open network element; The core network element is associated with and stores the group identifier, the group members, and the internal scope.

2. The method according to claim 1, characterized in that, The internal range is the same as the service range, or the internal range is mapped from the service range, and the internal range is a range that the operator network can recognize.

3. A communication method, characterized in that, The method includes: The capability open network element receives a group creation request message #1 from the application network element; the group creation request message #1 includes a group identifier, the group members included in the group corresponding to the group identifier, and the service scope of the group; the service scope is used to indicate the restricted area for the group members to obtain the services provided by the application network element; The capability open network element triggers the management of the group based on the service scope of the group carried in the group creation request message #1.

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

5. The method according to claim 4, characterized in that, The application network element includes at least one of the following: one or more Edge Application Servers (EAS), or one or more Edge Enable Servers (EES) corresponding to the EAS.

6. The 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 according to claim 6, characterized in that, The geographic location information includes any one or more of the following: geographic identification information or latitude and longitude information.

8. The method according to claim 6, characterized in that, The network location information includes any one or more of the following: Data Network Access Identifier (DNAI), Trajectory Area Identifier (TAI), TAI list, Area Identifier, Area Identifier list, Cell Identifier, or Cell Identifier list.

9. The method according to any one of claims 3, 5, 7-8, characterized in that, The capability-opening network element triggers management of the group based on the service scope of the group carried in the group creation request message #1, including: The capability-opening network element maps the service range to an internal range that the operator network can recognize; the internal range is used to characterize the restricted area. The capability-opening network element sends the group identifier, the group members, and the internal scope to the core network element.

10. The method according to claim 9, characterized in that, The method further includes: The capability-opening network element sends a location change subscription message to the mobility management network element corresponding to the group member; the subscription message carries the internal range; The capability open network element receives a location change notification message from the mobility management network element; the notification message is used to indicate the relationship between the location of the group member and the internal range.

11. The method according to claim 10, characterized in that, The relationship between the location of the group member and the internal scope includes any one or more of the following: The group member moves into the inner area; The group member moves out of the inner area; The group members are within the stated internal scope; or... The group members are outside the said internal scope.

12. The method according to claim 9, characterized in that, The capability-opening network element triggers management of the group based on the service scope of the group carried in the group creation request message #1, including: The capability-opening network element sends the group identifier, the group members, and the service range to the core network element.

13. The method according to claim 12, characterized in that, The method further includes: The capability-opening network element sends a location change subscription message to the mobility management network element corresponding to the group member; the subscription message carries the service range; The capability open network element receives a location change notification message from the mobility management network element; the notification message is used to indicate the relationship between the location of the group member and the service range.

14. The method according to claim 13, characterized in that, The relationship between the location of the group members and the service area includes any one or more of the following: The group members move into the service area; The group member moves out of the service area; The group members are within the service area; or... The group members are outside the scope of the service.

15. The method according to claim 10 or 13, characterized in that, The method further includes: The capability-opening network element sends the notification message to the application network element; The capability open network element receives a group update request message #1 from the application network element; the group update request message #1 is used to request an update to the group; The capability open 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 an update to the group.

16. The method according to claim 10 or 13, characterized in that, The method further includes: The capability open 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 an update to the group.

17. The method according to claim 10 or 13, characterized in that, The method further includes: The capability open network element receives location change notification information from the application network element; the location change notification information is used to instruct the capability open network element to subscribe to the location change information of the group members.

18. A communication method, characterized in that, The method includes: The core network element receives a group creation request message #2 from a capability open network element; the group creation request message #2 includes a group identifier, the group members included in the group corresponding to the group identifier, and the internal scope of the group; the internal scope is used to indicate the restricted area for the group members to obtain services provided by the application network element; the internal scope is determined based on the service scope provided by the application network element; The core network element is associated with and stores the group identifier, the group members, and the internal scope.

19. The method according to any one of claims 1, 2, or 18, characterized in that, The method further includes: The core network element updates the group based on the relationship between the location of the group members and the internal scope.

20. The method according to claim 19, characterized in that, The core network element updates the group based on the relationship between the location of the group members and the internal scope, including: If the group member is located outside the internal scope, or if the group member moves outside the internal scope, the core network element deletes the group member or marks the group member as inactive; or... If a group member moves into the internal range, the core network element will either re-add the group member to the group or mark the group member as active.

21. The method according to claim 19, characterized in that, The method further includes: The core network element triggers the session management network element to manage the protocol data unit (PDU) session corresponding to the group member based on the relationship between the location of the group member and the internal scope.

22. The method according to claim 21, characterized in that, The core network element triggers the session management network element to manage the PDU sessions corresponding to the group members based on the relationship between the location of the group members and the internal scope, including: If a group member is located outside the internal scope, or if a group member moves outside the internal scope, the core network element triggers the session management element to release the PDU session, or marks the PDU session as inactive; or, If the group member is located within the internal range, or if the group member moves into the internal range, the core network element triggers the session management element to create the PDU session, or marks the PDU session as active.

23. The method according to any one of claims 20-22, characterized in that, The method further includes: The core network element sends a location change subscription message to the mobility management network element corresponding to the group member; the subscription message carries the internal range. The core network element receives a location change notification message from the mobility management network element; the notification message is used to indicate the relationship between the location of the group member and the internal range.

24. The method according to any one of claims 1, 2, 18, 20-22, characterized in that, The core network element is associated with and stores the group identifier, the group members, and the internal scope, including: The core network element stores the group identifier, the group members, and the internal scope in the group's subscription information; or, The core network element stores the group identifier and the internal scope in the group member's subscription information.

25. The method according to claim 18 or 20, characterized in that, The method further includes: The core network element sends the internal range to the session management network element; or... The core network element receives the identifier of the terminal from the session management network element, and, based on the identifier of the terminal, indicates to the session management network element whether the terminal is within the internal range.

26. The method according to any one of claims 1, 2, 18, 20-22, characterized in that, The core network element is either a data storage network element or a policy control network element.

27. A communication device, characterized in that, The communication device includes a processor and a memory; the memory is used to store computer instructions, which, when executed by the processor, cause the communication device to perform the communication method as described in any one of claims 3-26.

28. A computer-readable storage medium, characterized in that, The computer-readable storage medium includes a computer program or instructions that, when executed on a computer, cause the computer to perform the communication method as described in any one of claims 3-26.

Images