Method for broadcast wireless communication services - Patents.com

Abstract

The present disclosure relates to a method and device for broadcasting a network service capability announcement message by a network node or function in a wireless communication system. The broadcast announcement message includes a network service identification list. The network service identification list includes the type of network service provided by the network node or function, various service entities that provide the service, and a network resource set associated with the network service. Another network node or function may request one or more of the network services in accordance with the network service capability announcement message.

Description

[Technical field]

[0001] The present disclosure is directed generally to wireless communications, and specifically to transmitting and receiving broadcast information of wireless communication services by radio network nodes. [Background technology]

[0002] Mobile communication technologies have provided the world with improved network connectivity. The rapid technological advances in mobile networks have in turn led to more demand for network capacity and bandwidth. It is important to design an efficient mobile network architecture that interacts with network nodes that are flexibly deployed and scalable in providing various network services. Other aspects such as energy consumption, device cost, spectrum efficiency, and latency are also important considerations when designing mobile networks to meet the needs of various communication applications. Summary of the Invention [Problem to be solved by the invention]

[0003] The present disclosure is directed to methods, systems, and devices related to wireless communication, and more particularly, to transmitting and receiving information broadcast of wireless communication services by a wireless network node or function. [Means for solving the problem]

[0004] In one embodiment, a method of obtaining a network service by a network function is disclosed, the method including receiving a network service announcement message from a first serving network function, the network service announcement message including a service identification list of one or more network services provided by a second serving network function, and selecting a target network service from the one or more network services.

[0005] The above method may further include transmitting a service request for acquiring the selected target network service to the first serving network function based on the network service announcement message.

[0006] In any one of the above methods, the first serving network function is the same network function as the second serving network function. In any one of the above methods, the service identification list may include a service type for each of the one or more network services. In any one of the above methods, the service type includes one of a paging, a multimedia broadcast multicast, a network registration request, a network configuration request, a network attachment request, a network registration response, a network attachment response, an announcement and discovery request, or an announcement and discovery response service type.

[0007] In any one of the above methods, the service identification list further includes a service entity for each of the one or more network services. In any one of the above methods, the service entity includes one of a public land mobile network identification, an authentication management function identifier, a single network slice selection assistance information, or a communication node identification associated with each of the one or more network services.

[0008] In any one of the above methods, the service identification list further includes at least one network resource set for each of the one or more network services. Any one of the above methods may further include transmitting a service request for obtaining the selected target network service to the first serving network function by selecting a network resource from the network resource set corresponding to the selected target network service in the service identification list and transmitting the service request using the selected network resource.

[0009] Various devices are further disclosed, each of which includes a processor and a memory, the processor configured to read computer code from the memory and implement any one of the above methods. In any one of the above methods, the service identification list further includes a resource type indicator for each of the at least one network resource set. In any one of the above methods, the resource type indicator indicates one of a physical channel / signal, spectrum / frame / power, or enterprise operation resource type.

[0010] In any one of the above methods, the network service announcement message is transmitted via one or more system information blocks. Any one of the above methods may further include transmitting a service request to a first serving network function based on the network service announcement message to obtain the selected target network service via a service-based interface between the network functions.

[0011] In another embodiment, a method of announcing a network service by a serving network function is disclosed, which may include: constructing a first network service announcement message including a service identification list of one or more network services provided by the serving network function, broadcasting the first network service announcement message to other network functions, and receiving a service request for a target network service of the one or more network services transmitted by the serving network function after the served network function receives the broadcasted first network service announcement message.

[0012] In the above methods, the service identification list may include a service type for each of the one or more network services. In any one of the above methods, the service type includes one of a paging, a multimedia broadcast multicast, a network registration request, a network configuration request, a network attachment request, a network registration response, a network attachment response, an announcement and discovery request, or an announcement and discovery response service type.

[0013] In any one of the above methods, the service identification list includes a service type for each of the one or more network services. In any one of the above methods, the service type includes one of a paging, a multimedia broadcast multicast, a network registration request, a network configuration request, a network attachment request, a network registration response, a network attachment response, an announcement and discovery request, or an announcement and discovery response service type.

[0014] In any one of the above methods, the service identification list further includes a service entity for each of the one or more network services. In any one of the above methods, the service entity includes one of a public land mobile network identification, an authentication management function identifier, a single network slice selection assistance information, or a communication node identification associated with each of the one or more network services.

[0015] In any one of the above methods, the service identification list further includes at least one network resource set for each of the one or more network services. In any one of the above methods, receiving a service request from the served network function may include receiving a service request for the target network service in a network resource selected by the served network function from the network resource set corresponding to the target network service according to the service identification list. In any of the above methods, the service identification list further includes a resource type indicator for each of the at least one network resource set. In any one of the above methods, the resource type indicator indicates one of a physical channel / signal, spectrum / frame / power, or enterprise operation resource type.

[0016] In any one of the above methods, the first network service announcement message is transmitted by a serving network function via one or more system information blocks. In any one of the above methods, the service request is transmitted via a service-based interface between network functions.

[0017] In any one of the above methods, the serving network function further receives a second network service announcement message from another serving network function prior to constructing the first network service announcement message. In any one of the above methods, the second network service announcement message may include one of a service identification list indicating a type or service identification of one or more network services provided by the other serving network function, a service identification list indicating a type or service identification of one or more network services not provided by the other serving network function, a service identification addition list indicating a type or service identification of one or more network services to be added as network services provided by the other serving network function, or a service identification release list indicating a type or service identification of one or more network services to be removed as network services provided by the other serving network function.

[0018] In any one of the above methods, the content of the first network service announcement message and the second network service announcement message are the same.

[0019] Further disclosed are network devices, each of which includes a processor and a memory with computer instructions stored therein, the processor being configured to implement any one of the methods described above upon execution of the computer instructions from the memory.

[0020] Further disclosed are computer readable media, each of which includes instructions that, when executed by a computer, cause the computer to perform any one of the methods described above.

[0021] These and other aspects and their implementations are described in more detail in the drawings, description, and claims below. The present invention further provides, for example, the following: (Item 1) 1. A method for obtaining a network service through a network function, the method comprising: receiving a network service announcement message from a first serving network function, the network service announcement message including a service identification list of one or more network services provided by a second serving network function; selecting a target network service from the one or more network services; A method comprising: (Item 2) 2. The method of claim 1, further comprising transmitting a service request to the first serving network function to obtain the selected target network service based on the network service announcement message. (Item 3) 2. The method of claim 1, wherein the first serving network function is the same network function as the second serving network function. (Item 4) 2. The method of claim 1, wherein the service identification list includes a service type for each of the one or more network services. (Item 5) 5. The method of claim 4, wherein the service type includes one of the following service types: paging, multimedia broadcast multicast, network registration request, network configuration request, network attachment request, network registration response, network attachment response, announcement and discovery request, or announcement and discovery response. (Item 6) 2. The method of claim 1, wherein the service identification list further includes a service entity for each of the one or more network services. (Item 7) 7. The method of claim 6, wherein the service entity includes one of a public land mobile network identification, an authentication management function identifier, a single network slice selection assistance information, or a communication node identification associated with each of the one or more network services. (Item 8) 2. The method of claim 1, wherein the service identification list further includes at least one network resource set for each of the one or more network services. (Item 9) and transmitting a service request to the first serving network function to obtain the selected target network service, the transmitting comprising: selecting a network resource from the set of network resources that corresponds to the selected target network service in the service identification list; transmitting the service request using the selected network resource; and The method according to item 8, by carrying out the steps. (Item 10) 9. The method of claim 8, wherein the service identification list further includes a resource type indicator for each of the at least one network resource set. (Item 11) Item 11. The method of item 10, wherein the resource type indicator indicates one of a physical channel / signal, spectrum / frame / power, or enterprise-operated resource type. (Item 12) 2. The method according to claim 1, wherein the network service announcement message is transmitted via one or more system information blocks. (Item 13) 2. The method of claim 1, further comprising transmitting a service request for acquiring the selected target network service to the first serving network function based on the network service announcement message via a service-based interface between network functions. (Item 14) 1. A method for announcing a network service by a serving network function, the method comprising: constructing a first network service announcement message including a service identification list of one or more network services provided by the serving network function; broadcasting the first network service announcement message to other network functions; A method comprising: (Item 15) 15. The method of claim 14, further comprising receiving a service request for a target network service among the one or more network services transmitted by the served network function after the served network function receives the broadcasted first network service announcement message. (Item 16) 15. The method of claim 14, wherein the service identification list includes a service type for each of the one or more network services. (Item 17) Item 17. The method of item 16, wherein the service type includes one of the following service types: paging, multimedia broadcast multicast, network registration request, network configuration request, network attachment request, network registration response, network attachment response, announcement and discovery request, or announcement and discovery response. (Item 18) 15. The method of claim 14, wherein the service identification list further includes a service entity for each of the one or more network services. (Item 19) 20. The method of claim 18, wherein the service entity includes one of a public land mobile network identification, an authentication management function identifier, a single network slice selection assistance information, or a communication node identification associated with each of the one or more network services. (Item 20) Item 15. The method of item 14, wherein the service identification list further includes at least one network resource set for each of the one or more network services. (Item 21) The method of claim 20, further comprising receiving a service request for a target network service among the one or more network services, the service request being transmitted by the served network function in a network resource corresponding to the target network service selected by the served network function from the network resource set according to the service identification list after the served network function receives the broadcasted first network service announcement message. (Item 22) 21. The method of claim 20, wherein the service identification list further includes a resource type indicator for each of the at least one network resource set. (Item 23) 23. The method of claim 22, wherein the resource type indicator indicates one of a physical channel / signal, spectrum / frame / power, or enterprise operation resource type. (Item 24) Item 15. The method of item 14, wherein the first network service announcement message is transmitted by the serving network function via one or more system information blocks. (Item 25) 15. The method of claim 14, further comprising receiving a service request for a target network service among the one or more network services transmitted by a served network function after the served network function receives the broadcasted first network service announcement message via a service-based interface between network functions. (Item 26) Item 15. The method of item 14, wherein the serving network function further receives a second network service announcement message from another serving network function prior to constructing the first network service announcement message. (Item 27) The second network service announcement message comprises: a service identification list indicating the type or service identification of one or more network services provided by other serving network functions; a service identification list indicating one or more types or service identifications of network services that are not provided by other serving network functions; a service identification addition list indicating one or more network service types or service identifications to be added as network services provided by other serving network functions; or A service identification release list indicating one or more network service types or service identifications that are to be removed as network services provided by other serving network functions. 27. The method according to claim 26, comprising one of the steps: (Item 28) 27. The method of claim 26, wherein the content of the first network service announcement message and the second network service announcement message are the same. (Item 29) A device comprising a processor and a memory, the processor configured to read computer code from the memory and implement the method according to any one of claims 1-28. (Item 30) A computer readable medium comprising instructions which, when executed by a computer, cause the computer to perform the method of any one of items 1-28. [Brief description of the drawings]

[0022] [Figure 1] FIG. 1 illustrates an example mobile network including a radio access network and a core network.

[0023] [Diagram 2] FIG. 2 illustrates an exemplary radio access network.

[0024] [Diagram 3] FIG. 3 illustrates an exemplary scheme for defining network resources for providing various types of network services.

[0025] [Figure 4] FIG. 4 illustrates another exemplary scheme for defining network resources for providing various types of network services. DETAILED DESCRIPTION OF THE PREFERRED EMBODIMENTS

[0026] Techniques and examples of implementations and / or embodiments in the present disclosure can be used to improve performance in providing various system services in a wireless communication system. The term "exemplary" is used to mean "an example of" and does not imply an ideal or preferred example, implementation, or embodiment unless otherwise stated. Section headings are used in this disclosure to facilitate understanding and do not limit the techniques disclosed in that section to only the corresponding section. The disclosed implementations may be further embodied in a variety of different forms, and thus, it is intended that the scope of the present disclosure or claimed subject matter be construed as not being limited to any of the embodiments set forth below. Various implementations may be embodied as methods, devices, components, systems, or non-transitory computer-readable media. Thus, embodiments of the present disclosure may take the form of, for example, hardware, software, firmware, or any combination thereof.

[0027] The present disclosure is directed to methods, systems, and devices related to wireless communication, and more particularly, to transmitting and receiving broadcast information of wireless communication services by a wireless network node for the purpose of moving toward a modular architecture for requesting and providing network services. Although the present disclosure provides an example implementation in a 5G cellular network system, the underlying principles are applicable to other generations of cellular network systems and other general wireless network systems. (Introduction)

[0028] The services and network functions provided by wireless systems are becoming increasingly complex and diverse to support an increasing number and type of wireless mobile or fixed devices and the growing demand for higher communication bandwidth / throughput and lower latency. These network services and functions have evolved from simply providing an interpersonal communication platform to becoming an integral part of communities and enterprises in various industries.

[0029] Due to their increasing complexity, wireless network nodes and components are becoming more sophisticated, and therefore the software and hardware deployment, operation, and maintenance of these network nodes and components is also becoming increasingly cumbersome and expensive.

[0030] To improve the flexibility / scalability of the wireless network system and reduce its deployment and maintenance complexity, various network services and network functions provided by or through the access network portion of the wireless network may be treated in a modular manner as service entities within each line network node. Various exemplary implementations of such a modular approach to wireless network services and functions are described in more detail in PCT International Application No. PCT / CN2019 / 198040, entitled “Service-Based Access Network Architecture and Communication,” filed on September 26, 2019 by the same applicant as the present application with the China State Intellectual Property Office, the entirety of which is incorporated herein by reference. (Wireless Network Overview)

[0031] An exemplary wireless communication network shown as 100 in FIG. 1 may include user equipment (UE) 110, 111, and 112, a carrier network 102, various service applications 140, and other data networks 150. The carrier network 102 may include, for example, access networks 120 and 121, and a core network 130. The carrier network 110 may be configured to transport voice, data, and other information (collectively referred to as data traffic) between the UEs 110, 111, and 112, between the UEs and the service applications 140, or between the UEs and other data networks 150. The access networks 120 and 121 may be configured as various radio access network nodes (WANNs) for interfacing with the UEs on one side of a communication session and the core network 130 on the other side. The core network 130 may include various network nodes configured to control the communication sessions and perform network access management and traffic routing. The service applications 140 may be hosted by various application servers that are deployed outside of, but connected to, the core network 130. Similarly, other data networks 150 may also be connected to the core network 130.

[0032] In the wireless communication network of 100, UEs may communicate with each other via access networks. For example, UEs 110 and 112 may be connected and communicate via the same access network 120. UEs may communicate with each other via both access networks and core networks. For example, UE 110 may be connected to access network 120 while UE 111 may be connected to access network 121, and thus UE 110 and UE 111 may communicate with each other via access networks 120 and 121 and core network 130. UEs may further communicate with service applications 140 and data network 150 via core network 130. Additionally, UEs may communicate with each other directly via sidelink communication, as indicated by 113.

[0033] FIG. 2 further illustrates an example system diagram of the wireless access network 120 including a wireless access network node (WANN) 202 serving the UEs 110 and 112 via a terrestrial interface 204. Each of the UEs 110 and 112 may include, without limitation, a mobile phone, a smartphone, a tablet, a laptop computer, a vehicle mounted communication device, a roadside communication device, a sensor device, a smart appliance (such as a television, a refrigerator, and an oven), or other device capable of wirelessly communicating via the network. As shown in FIG. 2, each of the UEs, such as the UE 112, may include transceiver circuitry 206 coupled to an antenna 208 to provide wireless communication with the WANN 120 or another UE, such as the UE 110. The transceiver circuitry 206 may also be coupled to a processor 210, which may also be coupled to a memory 212 or other storage device. The memory 212 may store therein computer instructions or code that, when read and executed by the processor 210, cause the processor 210 to implement various of the methods described herein. In particular, the UE may be configured to receive or provide network services.

[0034] Similarly, the WANN 120 may include base stations or other wireless network access points capable of communicating wirelessly with one or more UEs via the terrestrial interface 204 and with a core network. For example, the WANN 120 may be implemented in the form of a 4G LTE base station, a 5G NR base station, a 5G central unit base station, or a 5G distributed unit base station. Each of these types of WANNs may be configured to perform a corresponding set of wireless network functions. The WANN 120 may include transceiver circuitry 214 coupled to an antenna 216, which may include an antenna tower 218 in various forms for providing wireless communication with the UEs 110 and 112. The transceiver circuitry 214 may be coupled to one or more processors 220, which may further be coupled to a memory 222 or other storage device. The memory 222 may store therein instructions or code that, when read and executed by the processor 220, cause the processor 220 to implement various functions of the WANN 120 described herein. In particular, the WANN 120 may be configured to provide or receive network services to or from other network nodes of the wireless network. (Service-based Interface for Network Services and Functions)

[0035] As described in more detail in PCT International Application No. PCT / CN2019 / 198040 (herein incorporated by reference), various network services and functions may be implemented as network service entities in multiple domains, including, but not limited to, a cell group (CG) domain, a radio connection (RC) domain, and a radio session (RS) domain.

[0036] The CG domain may involve services related to cell groups, which may or may not be related to UEs. Examples of CG domain services may include, but are not limited to, a CG enforcement function, a CG control and enforcement proxy function, a CG control function, a CG data plane function, a CG management function, a CG exposure function, and a CG intelligence function.

[0037] An RS domain may involve radio session and bearer connection functions that are not associated with a cell group and may or may not be associated with a UE. Examples of RS domain services include, but are not limited to, an RS Service Data Adaptation Protocol (SDAP) function or a Packet Data Convergence Protocol (PDCP) function, an RS control and enforcement proxy function, an RS domain control function, an RS data plane function, an RS management plane function, an RS exposure function, and an RS intelligence function.

[0038] An RC domain may involve radio connectivity functions that are not related to cell groups and may or may not be related to UEs. Examples of RC domain services include, but are not limited to, RC control functions, RC data plane functions, RC management plane functions, and RC intelligence functions.

[0039] Various control functions in a particular domain may provide service-based interfaces (such as application programming interfaces (APIs) for other control functions (e.g., control functions in a particular domain and other domains)). Thus, the CG, RC, and RS domains may use other services provided to any of the domains via the service-based interfaces. In some implementations, the service-based interfaces may support request and response messages for service requests. For example, the service-based interfaces may support transmission of CG control request messages from the RC control function to the CG control function and corresponding response messages from the CG control function to the RC control function. The CG control request and response messages may include UE-specific information and / or control function-specific information. The control functions of each domain may control the enforcement functions of the domain through a proxy function between the control function and the enforcement function using similar service-based interfaces supporting service request and response messages.

[0040] Service-based interfaces may further be implemented for requests and responses of network services and functions between network nodes of the access network and the core network. For example, interactions between the RC control function and the Authentication Management Function (AFM) of the 5G core network, and between the RS control function and the Session Management Function (SMF) of the 5G core network may be facilitated by the service-based interfaces described above. In a particular example, the AMF may invoke a service-based interface provided by the RC control function for a service request. Similarly, the RC control function may also invoke a corresponding AMF service-based interface to support access, authentication, mobility, NAS messaging, etc. Thus, the service-based interface may be extended beyond the access network and implemented in the core network to request related services.

[0041] Each network service may be associated with various types of network resources required to provide the network service, which may be pre-configured or dynamically allocated.

[0042] A network node may be configured with a service-based interface for providing one or more network services to other network nodes. Such network service functions or capabilities must be known to other network nodes before they can make a service request. As illustrated in various embodiments below, a network node providing one or more network services may be configured to announce its service capabilities and network resource allocations for requesting the services via a broadcast message. Such a broadcast message may contain sufficient information to enable other network nodes to make a service request via the service-based interface.

[0043] The term "node" or "network node" may refer to a physical network unit or a network function. A network function may reside in a single physical network unit. Alternatively, a network function may reside in or be provided by two or more physical network units. A physical network unit may provide or support one or more network functions. In the various implementations described below, the terms "network node" and "network function" are synonymous unless explicitly distinguished.

[0044] The terms "served node", "served network node", or "served network function" are used to refer to a network node or function that requests a network service via a service-based interface, while the terms "serving node", "serving network node", or "serving network function" are used to refer to a network node or function that provides a requested network service. A served node or serving node may include any one of a WANN (e.g., a base station), a UE, or other network nodes. A serving node may additionally include other networks, such as the service application 140 and the data network 150 of FIG. 1. A served node or serving node may be a physical network node. Alternatively, a served node or serving node may be a functional component within a physical network node. In some other implementations, a served node or serving node may be a functional network component that is distributed within multiple physical network nodes. (First embodiment (node ​​provided with service))

[0045] A serving network node may transmit broadcast messages to other network nodes to announce its service features or capabilities. Such broadcast messages may be used to inform other network nodes of various network services provided by the serving network node. Correspondingly, other network nodes acting as served network nodes may receive the announcements and obtain various information regarding the services provided by the serving node.

[0046] By way of example, a network service announcement message broadcast by a serving network node and received by a served node may include at least one of the following:

[0047] (1) a service identification list indicating the service types that a serving node may provide or support;

[0048] (2) a service identification list indicating the service types as well as the service entities that the serving node may provide or support; or

[0049] (3) A resource set for each service identification.

[0050] Furthermore, the service type included in the announcement message for the service may indicate at least one network service category among a plurality of network service categories, which in some implementations may include, but are not limited to, a paging service, a multimedia broadcast multicast service (MBMS), a network registration request service, a network configuration request service, a network attachment request service, a network registration response service, a network configuration response service, a network attachment response service, an announcement and discovery request service, and an announcement and discovery response service.

[0051] The service entity information may be used to indicate the identity of the mobile network and the network node that provides the network service. For example, the service entity information associated with the network service may include at least one of the following: a public land mobile network (PLMN) identity, an AMF identifier, a single network slice selection assistance information (S-NSSAI, which may consist of a slice / service type), and a communication node identity.

[0052] The resource set component of a network service announcement by a serving node may include information related to network resources allocated or allocable for a corresponding network service. Network resources for different network services may include resources at different resource levels or network layers. Thus, resource sets for different network services may be categorized into multiple types of resource sets, labeled, for example, Type 1 resource sets, Type 2 resource sets, Type 3 resource sets, etc. A particular service may be associated with one or more of Type 1, Type 2, and / or Type 3 resource sets.

[0053] A Type 1 resource set may include physical channel / signal resource sets, such as, for example, a synchronization signal (SS) resource set and a physical downlink shared channel (PDSCH) resource set. A Type 2 resource set may include RF service related resource sets, such as radio spectrum, frame structure, and radio power. A Type 3 resource set may include enterprise operated resource sets, such as PLMN identity, AMF identity, and S-NSSAI. The terms "Type 1", "Type 2", and "Type 3" are used only as an indicator to distinguish different types or levels of resource sets.

[0054] A serving network node may provide multiple categories of services, and therefore a network service announcement message may include a list of multiple service identities, where each service identity may be associated with a service entity and one or more resource sets of various types.

[0055] When a network service announcement message from a serving network node is received by a served network node, when the served network node needs a particular network service, it may then select from the resource set for the particular network service according to the received announcement message and request the particular network service from the serving network node. The network service request may be made, for example, via the service-based interface described above.

[0056] The served node may be a UE, a WANN (base station), or another type of network node in a wireless network. The serving node may be, for example, a UE, a WANN, a service application, a data network, or another type of network node in a wireless network. For example, the served network may be a UE. Upon receiving a network service announcement message broadcasted by a serving node, the UE may select from a network resource set according to the announcement message and send a registration request to activate a network registration service to the serving network node via a service-based interface. For another example, the UE may select from a network resource set according to the announcement message and send a configuration request to the serving network node via a service-based interface. Similarly, the UE may select from a network resource set according to the announcement message and send a network connection request to the serving network node via a service-based interface. (Second embodiment (network service resource specification))

[0057] The resource set for each network, announced by the serving network node described above, may be defined either as an actual defined set of network resources or as a resource pool from which network resources may be dynamically selected by the served network node to request a network service.

[0058] As shown in FIG. 3, each service type, such as a paging service 302, an announcement service 304, an MBMS 306, a network registration service 308, a network connectivity service 310, etc., may be associated with one or more types of resource sets, such as a type 1 resource set 320, a type 2 resource set 322, and a type 3 resource set 324. Each type (or level) of resource set may be further associated with various network resources for the network service. For example, the type 1 resource set 320 may be associated with a primary synchronization signal (PSS) resource 330, a physical downlink control channel (PDCCH) resource 332, a secondary synchronization signal (SSS) resource 334. For another example, the type 2 resource set 322 may be associated with a carrier resource 336, a frequency band resource 338, and a power resource 340. For yet another example, the type 3 resource set 324 may be associated with a PLMN identity 342, an AMF identifier 344, and an S-NSSAI 346. Different resource set identifiers for different resource types can identify different resources.

[0059] An exemplary network service announcement message specifying resource sets associated with various services provided by a serving node is shown below.

number

number

[0060] As further shown in the alternative implementation of FIG. 4, each service type, such as the paging service 302, the announcement service 304, the MBMS 306, the network registration service 308, the network connectivity service 310, etc., may be associated with one or more types of resource pools, such as a type 1 resource pool 420, a type 2 resource pool 422, and a type 3 resource pool 424. Each type (or level) of resource pool may be further associated with various network resources for the network service. For example, the type 1 resource pool 420 may be associated with a PSS resource pool 430, a PDCCH resource pool 432, an SSS resource pool 434. For another example, the type 2 resource pool 322 may be associated with a carrier resource pool 436, a frequency band resource pool 438, and a power resource pool 440. For yet another example, the type 3 resource pool 424 may be associated with a PLMN identification 442, an AMF identifier 444, and an S-NSSAI 446.

[0061] An exemplary network service announcement message defining resource pools associated with various services offered by a serving node is shown below.

number

[0062] Multiple serving network nodes may transmit broadcast announcement messages to other network nodes. Such broadcast messages may be used to announce different network services provided by each of the multiple serving network nodes. The multiple serving nodes may provide the same network service. Correspondingly, other network nodes may receive announcement messages from the multiple serving network nodes and obtain different information regarding the services provided by the serving nodes. In particular, a served network node may obtain information regarding the same network service provided by the multiple serving network nodes.

[0063] As an example, each of the network service announcement messages broadcast by the multiple serving network nodes and received by the served nodes may include at least one of the following: (1) a service identification list indicating the service types that the corresponding serving node may provide or support; (2) a service identification list indicating the service types and service entities that the serving node may provide or support; or (3) A resource set for each service identification.

[0064] Further, the service type may indicate at least one network service category among a plurality of network service categories, which in some implementations may include, but are not limited to, a paging service, an MBMS, a network registration request service, a network configuration request service, a network attachment request service, a network registration response service, a network configuration response service, a network attachment response service, an announcement and discovery request service, and an announcement and discovery response service.

[0065] The service entity information may be used to indicate the identity of a network node that provides a mobile network and network service. For example, the service entity information associated with a network service may include at least one of a PLMN identity, an AMF identifier, an S-NSSAI, and a correspondent node identity.

[0066] The resource set component of a network service announcement by a serving node may include information related to network resources allocated (or allocable) for a corresponding network service. Network resources for different network services may include resources at different resource levels. Thus, resource sets for different network services may be categorized into multiple types of resource sets, labeled, for example, Type 1 resource sets, Type 2 resource sets, Type 3 resource sets, etc. A particular service may be associated with one or more of Type 1, Type 2, and / or Type 3 resource sets.

[0067] Type 1 resource sets may include physical channel / signal resource sets, e.g., SS resource sets and PDSCH resource sets. Type 2 resource sets may include RF service related resource sets, such as radio spectrum, frame structure, and radio power. Type 3 resource sets may include enterprise operated resource sets, such as PLMN identity, AMF identity, and S-NSSAI. The terms "Type 1", "Type 2", and "Type 3" are used only as an indicator to distinguish different types or levels of resource sets.

[0068] A serving network node may provide multiple categories of services, and therefore a network service announcement message may include a list of multiple service identities, where each service identity may be associated with a service entity and one or more resource sets of various types.

[0069] Multiple serving network nodes may offer the same particular network service, and the service information is included within their announcements of the particular network service.

[0070] When the network service announcement messages from multiple serving network nodes are received by a served network node, when the served network node needs a particular network service, it may then select a serving network node from the serving network nodes that provides the particular network service according to the announcement message. A resource set for the particular network service as identified in the announcement message of the selected serving network node may be identified and used to request the particular network service from the selected serving network node. The network service request may be made, for example, via the service-based interface described above.

[0071] The served node may be a UE, a WANN (base station), or another type of network node in a wireless network. The serving node may be, for example, a UE, a WANN, a service application, a data network, or another type of network node in a wireless network. (Fourth embodiment (serving node))

[0072] A serving node that provides one or more network services may first construct a broadcast announcement message to announce its service functions or capabilities to other network nodes, and then send the announcement message to other network nodes by broadcasting. The broadcast announcement message may include: (1) a service identification list indicating the service types that the serving node may provide or support; or (2) a service identification list indicating the service types and service entities that the serving node does not provide or is not capable of supporting; or (3) a list of service identities to be added, indicating service types and / or entities of network services that the serving node can provide, and which may be added in addition to any previous announcements by the serving node; or (4) A list of service identities to be released, indicating service types and / or entities of network services that were included in a previous announcement by the serving node but are no longer being provided.

[0073] The service type included in the announcement message for the service may indicate at least one network service category among a plurality of network service categories, which in some implementations may include, but are not limited to, a paging service, an MBMS, a network registration request service, a network configuration request service, a network attachment request service, a network registration response service, a network configuration response service, a network attachment response service, an announcement and discovery request service, and an announcement and discovery response service.

[0074] The service entity information may be used to indicate the identity of a network node that provides a mobile network and network service. For example, the service entity information associated with a network service may include at least one of a PLMN identity, an AMF identifier, an S-NSSAI, and a correspondent node identity.

[0075] The broadcast message from the serving node may further include a resource set associated with each of the service identities. The resource set component of the network service announcement by the serving node may include information related to the network resources allocated (or allocable) for the corresponding network service. The network resources for different network services may include resources at different resource levels. Thus, the resource sets for different network services may be categorized into multiple types of resource sets, labeled, for example, Type 1 resource sets, Type 2 resource sets, Type 3 resource sets, etc. A particular service may be associated with one or more of Type 1, Type 2, and / or Type 3 resource sets.

[0076] Type 1 resource sets may include physical channel / signal resource sets, e.g., SS resource sets and PDSCH resource sets. Type 2 resource sets may include RF service related resource sets, such as radio spectrum, frame structure, and radio power. Type 3 resources may include enterprise operated resource sets, such as PLMN identity, AMF identity, and S-NSSAI. The terms "Type 1", "Type 2", and "Type 3" are used only as an indicator to distinguish different types or levels of resource sets.

[0077] Further, the above broadcast message may be segmented into multiple broadcast messages, each of which includes a segment of the network service announcement by the serving node. Thus, each segmented broadcast message may further include one or more of the following: (1) a message segment that carries a segment of the broadcast announcement message content; (2) a message segment number indicating the segment number of the broadcast message segment contained within this broadcast message (e.g., a segment number of zero corresponds to the first segment, a segment number of one corresponds to the second segment, etc.); or (3) A message segment type indicating whether the contained broadcast message segment is the last segment. (Fifth embodiment (relay of network service broadcast message))

[0078] A serving network node may be configured to relay a network service broadcast announcement message from another serving network node. For example, a network serving node may first receive a first announcement message from another serving network node (which may be broadcast in a unicast state by the other serving network node). The first announcement message may include: (1) a service identification list indicating the service types that other serving nodes may provide or support; or (2) a service identification list indicating service types and service entities that are not offered or supported by other serving nodes; or (3) a list of service identities to be added, indicating service types and / or entities of network services that other serving nodes may provide, and which may be added in addition to previous announcements by the serving nodes; or (4) A list of service identities to be released, indicating service types and / or entities of network services that were included in a previous announcement by another serving node but are no longer being provided.

[0079] The service type included in the announcement message for the service may indicate at least one network service category among a plurality of network service categories, which in some implementations may include, but are not limited to, a paging service, an MBMS, a network registration request service, a network configuration request service, a network attachment request service, a network registration response service, a network configuration response service, a network attachment response service, an announcement and discovery request service, and an announcement and discovery response service.

[0080] The service entity information may be used to indicate the identity of a network node that provides a mobile network and network service. For example, the service entity information associated with a network service may include at least one of a PLMN identity, an AMF identifier, an S-NSSAI, and a correspondent node identity.

[0081] Additionally, the first announcement message may further include a resource set associated with each of the service identities. The resource set component of the network service announcement by the serving node may include information related to network resources allocated (or allocable) for the corresponding network service. Network resources for different network services may include resources at different resource levels. Thus, resource sets for different network services may be categorized into multiple types of resource sets, labeled, for example, Type 1 resource sets, Type 2 resource sets, Type 3 resource sets, etc. A particular service may be associated with one or more of Type 1, Type 2, and / or Type 3 resource sets.

[0082] Type 1 resource sets may include physical channel / signal resource sets, e.g., SS resource sets and PDSCH resource sets. Type 2 resource sets may include RF service related resource sets, such as radio spectrum, frame structure, and radio power. Type 3 resources may include enterprise operated resource sets, such as PLMN identity, AMF identity, and S-NSSAI. The terms "Type 1", "Type 2", and "Type 3" are used only as an indicator to distinguish different types or levels of resource sets.

[0083] Furthermore, the first broadcast announcement message may be segmented into multiple broadcast messages, each of the multiple broadcast messages including a segment of the network service announcement by the serving node. Thus, each segmented broadcast message may further include one or more of the following: (1) a message segment that carries a segment of the broadcast announcement message content; (2) a message segment number indicating the segment number of the broadcast message segment contained within this broadcast message (e.g., a segment number of zero corresponds to the first segment, a segment number of one corresponds to the second segment, etc.); or (3) A message segment type indicating whether the contained broadcast message segment is the last segment.

[0084] When the serving network node receives the first announcement message from the other serving network nodes, the serving node may then send a second announcement message to the other network nodes by broadcasting. The second announcement message may include: (1) a service identification list indicating the service types that the serving node may provide or support; or (2) a service identification list indicating the service types and service entities that the serving node does not provide or is not capable of supporting; or (3) a list of service identities to be added, indicating service types and / or entities of network services that the serving node may provide, and which may be added in addition to any previous announcements by the serving node; or (4) A list of service identities to be released, indicating service types and / or entities of network services that were included in a previous announcement by the serving node but are no longer being provided.

[0085] The service type may indicate at least one network service category among a plurality of network service categories, which in some implementations may include, but are not limited to, a paging service, an MBMS, a network registration request service, a network configuration request service, a network attachment request service, a network registration response service, a network configuration response service, a network attachment response service, an announcement and discovery request service, and an announcement and discovery response service.

[0086] The service entity information may be used to indicate the identity of a network node that provides a mobile network and network service. For example, the service entity information associated with a network service may include at least one of a PLMN identity, an AMF identifier, an S-NSSAI, and a correspondent node identity.

[0087] Additionally, the second announcement message may further include a resource set associated with each of the service identities. The resource set component of the network service announcement by the serving node may include information related to the network resources allocated (or allocable) for the corresponding network service. The network resources for different network services may include resources at different resource levels. Thus, the resource sets for different network services may be categorized into multiple types of resource sets, labeled, for example, Type 1 resource sets, Type 2 resource sets, Type 3 resource sets, etc. A particular service may be associated with one or more of Type 1, Type 2, and / or Type 3 resource sets.

[0088] Type 1 resource sets may include physical channel / signal resource sets, e.g., SS resource sets and PDSCH resource sets. Type 2 resource sets may include RF service related resource sets, such as radio spectrum, frame structure, and radio power. Type 3 resources may include enterprise operated resource sets, such as PLMN identity, AMF identity, and S-NSSAI. The terms "Type 1", "Type 2", and "Type 3" are used only as an indicator to distinguish different types or levels of resource sets.

[0089] Furthermore, the second broadcast announcement message may be segmented into a plurality of broadcast messages, each of which includes a segment of the network service announcement by the serving node. Thus, each segmented broadcast message may further include one of the following: (1) a message segment that carries a segment of the broadcast announcement message content; (2) a message segment number indicating the segment number of the broadcast message segment contained within this broadcast message (e.g., a segment number of zero corresponds to the first segment, a segment number of one corresponds to the second segment, etc.); or (3) A message segment type indicating whether the contained broadcast message segment is the last segment.

[0090] The content of the second announcement message may be the same as or different from the first announcement message, so that the serving node can be used to relay the service capabilities of other serving nodes to other network nodes. (Sixth embodiment (service announcement message as system information element))

[0091] The above service broadcast announcement message may be constructed to include multiple system information elements, where different information elements may carry different system information items.

[0092] For example, the broadcast announcement message may include a first system information element. The first system information element may include: (1) a service identification list indicating the service types that other serving nodes may provide or support; or (2) A service identification list indicating service types and service entities that are not provided or supported by other serving nodes.

[0093] The broadcast announcement message may include a second system information element. The second system information element may include a resource set associated with each service identification. Furthermore, the resource set component of the network service announcement by the serving node may include information related to the network resources allocated (or allocable) for the corresponding network service. The network resources for different network services may include resources at different resource levels. Thus, the resource sets for different network services may be categorized into multiple types of resource sets, labeled, for example, Type 1 resource sets, Type 2 resource sets, Type 3 resource sets, etc. A particular service may be associated with one or more of Type 1, Type 2, and / or Type 3 resource sets.

[0094] Type 1 resource sets may include physical channel / signal resource sets, e.g., SS resource sets and PDSCH resource sets. Type 2 resource sets may include RF service related resource sets, such as radio spectrum, frame structure, and radio power. Type 3 resources may include enterprise operated resource sets, such as PLMN identity, AMF identity, and S-NSSAI. The terms "Type 1", "Type 2", and "Type 3" are used only as an indicator to distinguish different types or levels of resource sets.

[0095] Additionally, the second system information element may further include one or more of the following: (1) a service identification list indicating the service types that other serving nodes may provide or support; or (2) a service identification list indicating service types and service entities that are not offered or supported by other serving nodes; or (3) a list of service identities to be added, indicating service types and / or entities of network services that other serving nodes may provide, and which may be added in addition to previous announcements by the serving nodes; or (4) A list of service identities to be released, indicating service types and / or entities of network services that were included in a previous announcement by another serving node but are no longer being provided.

[0096] In some implementations, the network service announcement message may be broadcast using a system information block (SIB). In some exemplary implementations, the first system information element may be master system information using a master information block (MIB). In some implementations, the second system information element may be type 1 system information. In some exemplary implementations, the first system information element may be system information block 1 (SIB1). In some implementations, the second system information element may be system information block n (SIBn). Other manners in which system information blocks are used for the broadcast announcement message are also contemplated.

[0097] Throughout this specification and the claims, terms may have subtle meanings that are suggested or implied in the context beyond the explicitly stated meaning. Similarly, the phrase "in one embodiment / implementation" as used herein does not necessarily refer to the same embodiment, and the phrase "in another embodiment / implementation" as used herein does not necessarily refer to a different embodiment. For example, it is intended that the claimed subject matter includes combinations of the example embodiments, whether in whole or in part.

[0098] Generally, terminology may be understood, at least in part, from usage in context. For example, terms such as "and," "or," or "and / or" as used herein may include various meanings that may depend, at least in part, on the context in which such terms are used. Typically, when used to relate an enumeration such as A, B, or C, "or" is intended to mean A, B, and C as used herein in an inclusive sense, as well as A, B, or C as used herein in an exclusive sense. In addition, the term "one or more" as used herein may be used to describe any feature, structure, or characteristic in a single sense, or may be used to describe a combination of features, structures, or characteristics in a multiple sense, at least in part, depending on the context. Similarly, terms such as "a," "an," or "the" may be understood to convey a single usage or to convey a multiple usage, at least in part, depending on the context. In addition, the term "based on" may be understood as not necessarily intended to convey an exclusive set of factors, and instead may allow for the existence of additional factors not necessarily explicitly described, again, at least in part, depending on the context.

[0099] References to features, advantages, or similar language throughout this specification do not imply that all of the features and advantages that may be realized using the solution should or are included in any single implementation thereof. Rather, language referring to features and advantages is understood to mean that the specific feature, advantage, or characteristic described in connection with an embodiment is included in at least one embodiment of the solution. Thus, discussions of features and advantages and similar language throughout this specification may, but do not necessarily, refer to the same embodiment.

[0100] Furthermore, the described features, advantages, and characteristics of the solution may be combined in any suitable manner in one or more embodiments. Those skilled in the art will recognize in light of the description herein that the solution may be practiced without one or more of the specific features or advantages of a particular embodiment. In other cases, additional features and advantages may be recognized in an embodiment that may not be present in all embodiments of the solution.

Claims

1. 1. A method for obtaining a network service through a network function, the method comprising: receiving a network service announcement message from a first serving network function, the network service announcement message including a service identification list of one or more network services provided by a second serving network function, the service identification list including at least one network resource set for each of the one or more network services and a resource type indicator for each of the at least one network resource set, from which network resources are dynamically allocated, the resource type indicator indicating one of a physical channel resource type, a synchronization signal resource type, a radio spectrum resource type, a frame resource type, a radio power resource type, or a network identifier resource type; selecting a target network service from the one or more network services; transmitting a service request to the first serving network function for acquiring the selected target network service based on the at least one network resource set and the resource type indicator in the network service announcement message; A method comprising:

2. The method of claim 1 , wherein the first serving network function is the same network function as the second serving network function.

3. 2. The method of claim 1, wherein the service identification list includes a service type for each of the one or more network services, the service type including one of a paging, a multimedia broadcast multicast, a network registration request, a network configuration request, a network attachment request, a network registration response, a network attachment response, an announcement and discovery request, or an announcement and discovery response service type.

4. 2. The method of claim 1, wherein the service identification list further includes a service entity for each of the one or more network services, the service entity including one of a public land mobile network identification, an authentication management function identifier, a single network slice selection auxiliary information, or a communication node identification associated with each of the one or more network services.

5. transmitting a service request to the first serving network function to obtain the selected target network service; selecting a network resource from the set of network resources that corresponds to the selected target network service in the service identification list; transmitting the service request using the selected network resource; and The method of claim 1 , wherein the method is carried out by

6. The method of claim 1 , wherein the network service announcement message is transmitted via one or more system information blocks.

7. 10. The method of claim 1, wherein transmitting the service request to the first serving network function to obtain the selected target network service is performed via a service-based interface between network functions.

8. A device comprising a processor and a memory, The processor, Reading the computer code from the memory receiving a network service announcement message from a first serving network function, the network service announcement message including a service identification list of one or more network services provided by a second serving network function, the service identification list including at least one network resource set for each of the one or more network services and a resource type indicator for each of the at least one network resource set, from which network resources are dynamically allocated, the resource type indicator indicating one of a physical channel resource type, a synchronization signal resource type, a radio spectrum resource type, a frame resource type, a radio power resource type, or a network identifier resource type; selecting a target network service from the one or more network services; transmitting a service request to the first serving network function for acquiring the selected target network service based on the at least one network resource set and the resource type indicator in the network service announcement message; A device that is configured to:

Images